-
Notifications
You must be signed in to change notification settings - Fork 390
chore(deps): update prom/prometheus docker tag to v3.4.1 #4038
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
File renamed without changes.
File renamed without changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
The code appears to be correct and optimized for updating Prometheus from version v3.4.0 to v3.4.1. Here's a brief analysis of the changes:
Changes & Observations:
prom/prometheus:v3.4.0toprom/prometheus:v3.4.1. This ensures that you are fetching the latest stable version of Prometheus, which includes any bug fixes or features present in this release.Potential Issues:
/etc/prometheus/) remain intact when upgrading images.Recommendations:
Validation Testing: After applying these changes, run thorough validation tests on the new Prometheus setup to ensure all alerts are working correctly and there are no data ingestion bottlenecks.
Monitoring: Consider setting up monitoring to log service health metrics like CPU usage, memory consumption, and disk utilization during the upgrade process to detect any performance issues early.
Documentation Review: If the deployment involves multiple services, review the documentation to confirm that the new parameters (
--config.file,--storage.tsdb.path) do not conflict with other configuration options set outside this block.Summary:
The updates should work as intended given they only involve an image replacement. Verify functionality through testing before going live.