Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Update Get-Started Labels #13188

Merged
merged 1 commit into from
Jun 11, 2024
Merged

Conversation

adamsthws
Copy link
Contributor

docs: Update Get-Started Labels

Description

The current section on "Getting Started with Labels" provides several YAML configuration examples. For newcomers, it is not immediately clear that these examples pertain to configurations for log collectors like Promtail/Alloy, rather than Loki itself. This can lead to confusion about where and how to apply these configurations. Clarifying this in the documentation will enhance its accessibility and usability, particularly for those new to Loki and its ecosystem.

Proposed Change

Add a brief note at the beginning of the section clarifying that these examples are meant for log collector configurations, such as Promtail/Alloy.

Issue(s) this PR fixes

Fixes: #13187

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • Title matches the required conventional commits format, see here
    • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
  • Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
  • For Helm chart changes bump the Helm chart version in production/helm/loki/Chart.yaml and update production/helm/loki/CHANGELOG.md and production/helm/loki/README.md. Example PR
  • If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

docs: Update Get-Started Labels

Description
The current section on "Getting Started with Labels" provides several YAML configuration examples. For newcomers, it is not immediately clear that these examples pertain to configurations for log collectors like Promtail/Alloy, rather than Loki itself. This can lead to confusion about where and how to apply these configurations. Clarifying this in the documentation will enhance its accessibility and usability, particularly for those new to Loki and its ecosystem.

Proposed Change
Add a brief note at the beginning of the section stating these examples are meant for log collector configurations, such as Promtail/Alloy.
@adamsthws adamsthws requested a review from a team as a code owner June 10, 2024 20:19
@CLAassistant
Copy link

CLAassistant commented Jun 10, 2024

CLA assistant check
All committers have signed the CLA.

@github-actions github-actions bot added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Jun 10, 2024
Copy link
Contributor

@JStickler JStickler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Docs team] LGTM, thanks for taking the time to improve the docs.

@grafanabot
Copy link
Collaborator

This PR must be merged before a backport PR will be created.

1 similar comment
@grafanabot
Copy link
Collaborator

This PR must be merged before a backport PR will be created.

@JStickler JStickler merged commit a08ee68 into grafana:main Jun 11, 2024
62 of 63 checks passed
grafanabot pushed a commit that referenced this pull request Jun 11, 2024
grafanabot pushed a commit that referenced this pull request Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release-2.9.x backport release-3.0.x size/XS type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Docs feedback: /docs/sources/get-started/labels/_index.md
4 participants