Skip to content

Upgrade to Prometheus 3.x #2306

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.

Sign up for GitHub

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

Jump to bottom
Open
ptodev opened this issue Dec 20, 2024 · 2 comments · May be fixed by #3454
Open

Upgrade to Prometheus 3.x #2306

ptodev opened this issue Dec 20, 2024 · 2 comments · May be fixed by #3454
Assignees
@dehaansa

Comments

@ptodev
Copy link
Collaborator

ptodev commented Dec 20, 2024

Prometheus 3.0 was released in November 2024. Given that Alloy includes native Prometheus pipelines, it would be good to upgrade it sooner rather than later.

  • There are breaking changes in the v3 release. If we want to upgrade without making an Alloy v2 release, we should find a way to not incorporate breaking changes.
  • I believe there have been changes to the remote write specification. We need to take special care that the prometheus.remote_write component works in a backwards compatible way.
  • We need to incorporate new config arguments. For example an Alloy user noted that match_first_network in docker_sd_config would be useful.
@github-actions GitHub Actions
Copy link
Contributor

This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!

@mateuszdrab
Copy link

The improvements made in prometheus/prometheus#10490 should change how containers with service network mode are handled.
Currently, promtail does not discover containers that are configured with network_mode: "service:xyz" which prevents those containers from having their logs processed.
I believe the changes have already propagated to promtail in Loki v3.2.0

@ptodev ptodev self-assigned this Feb 24, 2025
@thampiotr thampiotr changed the title Upgrade to Prometheus 3.0 Upgrade to Prometheus 3.x Mar 11, 2025
@ptodev ptodev assigned dehaansa and unassigned ptodev Apr 14, 2025
@dehaansa dehaansa linked a pull request Apr 25, 2025 that will close this issue
Draft
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dehaansa dehaansa

Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@dehaansa @ptodev @mateuszdrab