Skip to content

[raft][metrics] Timestamp the context - #1795

Merged
mickmis merged 1 commit into
interuss:masterfrom
Orbitalize:fix_metrics_panic
Oct 19, 2026
Merged

mickmis merged 1 commit into
interuss:masterfrom
Orbitalize:fix_metrics_panic

Conversation

@MariemBaccari

Copy link
Copy Markdown
Contributor

This PR aims to fix #1794 by timestamping the context of the metric collection fetcher since those requests do not go through the timestamp middleware.

@MariemBaccari
MariemBaccari marked this pull request as ready for review October 19, 2026 08:05

@mickmis mickmis left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM to avoid the panic.

But that makes me wonder whether we actually want to dispatch a read proposal to get those metrics. For a potential future optimization, what would you think of reading this from the memstore instead? (we'd need to see how to deal with the interfaces though) Because in the end I do not think we really care about this read being super up-to-date.

@mickmis
mickmis merged commit 3046298 into interuss:master Oct 19, 2026
20 checks passed
@mickmis
mickmis deleted the fix_metrics_panic branch October 19, 2026 13:14
@MariemBaccari

Copy link
Copy Markdown
Contributor Author

@mickmis I agree. I think this will be part of the design for #1774.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[raft] Scraping /metrics crashes the core-service with timestamp not found in context

2 participants