Skip to content

fix: expose db event metrics via prometheus #1434

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 2 commits into from
Jun 25, 2025

Conversation

filipecabaco
Copy link
Member

What kind of change does this PR introduce?

currently we're not exposing db_event metrics via prometheus endpoint

currently we're not exposing db_event metrics via prometheus endpoint
Copy link

vercel bot commented Jun 24, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
realtime-demo ⬜️ Ignored (Inspect) Visit Preview Jun 25, 2025 10:13am

@coveralls
Copy link

coveralls commented Jun 24, 2025

Coverage Status

coverage: 84.622% (+0.09%) from 84.533%
when pulling 50fc853 on fix/expose-db-events-in-victoria-metrics
into fded2b6 on main.

Copy link
Member

@edgurgel edgurgel left a comment

Choose a reason for hiding this comment

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

Added a comment but other than that LGTM

@filipecabaco filipecabaco merged commit 3e1ce1c into main Jun 25, 2025
7 checks passed
@filipecabaco filipecabaco deleted the fix/expose-db-events-in-victoria-metrics branch June 25, 2025 10:30
@kiwicopple
Copy link
Member

🎉 This PR is included in version 2.37.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants