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

Update docs/telemetry.md with new Event-Based metrics #4837

Closed
stevend-uber opened this issue Jan 26, 2024 · 0 comments · Fixed by #5189
Closed

Update docs/telemetry.md with new Event-Based metrics #4837

stevend-uber opened this issue Jan 26, 2024 · 0 comments · Fixed by #5189
Labels
help wanted Issues with this label are ready to start work but are in need of someone to do it priority/backlog Issue is approved and in the backlog

Comments

@stevend-uber
Copy link
Contributor

With Event-Based cache hydration in experimental and hopefully more widely adopted, we should add the currently supported metrics to the docs/telemetry.md file for easy searchability.

@rturner3 rturner3 added help wanted Issues with this label are ready to start work but are in need of someone to do it priority/backlog Issue is approved and in the backlog labels Feb 1, 2024
@edwbuck edwbuck mentioned this issue Jun 4, 2024
3 tasks
edwbuck added a commit to edwbuck/spire that referenced this issue Jun 4, 2024
Closes spiffe#4837

This covers the database interactions for both
registration entry events (list, prune, fetch)
and node events (list, prune, fetch)

Signed-off-by: Edwin Buck <edwbuck@gmail.com>
MarcosDY pushed a commit that referenced this issue Jun 4, 2024
* Update Telemetry documentation for SPIRE DB Events

Closes #4837

This covers the database interactions for both
registration entry events (list, prune, fetch)
and node events (list, prune, fetch)

Signed-off-by: Edwin Buck <edwbuck@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issues with this label are ready to start work but are in need of someone to do it priority/backlog Issue is approved and in the backlog
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants