-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
chore(promtail): Use minimal init config in rpm/deb packaging. #11511
Conversation
Related issue: #11398 This minimal config scrape only single file thus not overloading the systems as described in the issue Signed-off-by: Kaviraj <[email protected]>
Signed-off-by: Kaviraj <[email protected]>
Trivy scan found the following vulnerabilities:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we move the file into tools/packaging/
as it is intended for packaging purposes only.
Signed-off-by: Kaviraj <[email protected]>
Co-authored-by: Christian Haudum <[email protected]>
Co-authored-by: Christian Haudum <[email protected]>
@kavirajk, seems the package testing for deb is failing and doesn´t continue with rpm package testing :-) |
@chaudum, maybe you can help ? |
any update @chaudum / @kavirajk / @MichelHollands ? |
Apologies for the delay. Got distracted with PTO and other works. I will take a look ASAP. |
filename: /tmp/positions.yaml | ||
|
||
clients: | ||
- url: http://localhost:3100/loki/api/v1/push |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should use consistent list indentation (compare with scrape_configs
).
- localhost | ||
labels: | ||
job: varlogs | ||
__path__: /var/log/messages |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a comment that this section should be changed by the user after installation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a hint :-) - there is now more failing in the build-pipeline - https://drone.grafana.net/grafana/loki/32891/25/8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Release stage" on drone pipeline seems flaky.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think found the issue. The packaging test pipeline generate test log and writes to /var/log/test.log
and checks if its scraped fine, By using minimal config we scrape only /var/log/messages
and doesn't include /var/log/test.log
.
I changed the filename from /var/log/test.log
-> /var/log/messages
instead in the scripts so test logs are properly scraped.
I think that should fix it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It did.
Co-authored-by: Christian Haudum <[email protected]>
Signed-off-by: Kaviraj <[email protected]>
Previously we are writing logs to /var/log/test.log. But with minimal config we scrape only /var/log/messages. So write to /var/log/messages instead Signed-off-by: Kaviraj <[email protected]>
Signed-off-by: Kaviraj <[email protected]>
@chaudum addressed your comments. Also CI passes. |
Hello @chaudum!
Please, if the current pull request addresses a bug fix, label it with the |
…ackaging. (#11676) Backport 86f2001 from #11511 --- **What this PR does / why we need it**: Related issue: #11398 This minimal config scrape only single file thus not overloading the systems as described in the issue **Which issue(s) this PR fixes**: Fixes #<issue number> **Special notes for your reviewer**: **Checklist** - [x] Reviewed the [`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md) guide (**required**) - [x] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] If the change is worth mentioning in the release notes, add `add-to-release-notes` label - [ ] 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](d10549e) - [ ] 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](0d4416a) Co-authored-by: Kaviraj Kanagaraj <[email protected]> Co-authored-by: Poyzan <[email protected]>
@poyzannur / @kavirajk - there is still no new version 2.9.4 released ? |
…na#11511) Related issue: grafana#11398 This minimal config scrape only single file thus not overloading the systems as described in the issue
What this PR does / why we need it:
Related issue: #11398
This minimal config scrape only single file thus not overloading the systems as described in the issue
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist
CONTRIBUTING.md
guide (required)CHANGELOG.md
updatedadd-to-release-notes
labeldocs/sources/setup/upgrade/_index.md
production/helm/loki/Chart.yaml
and updateproduction/helm/loki/CHANGELOG.md
andproduction/helm/loki/README.md
. Example PRdeprecated-config.yaml
anddeleted-config.yaml
files respectively in thetools/deprecated-config-checker
directory. Example PR