-
Notifications
You must be signed in to change notification settings - Fork 4
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
Exportable service metrics #134
Comments
Why this is coming up now: I learned that the Resource Health building block in EOEPCA will possibly in the future be able to receive OpenTelemetry traces from other building blocks, to ease debugging. VEDA Backend has set up a centralized usage metrics overview (dashboard), which would also be highly relevant as a feature for eoapi-k8s. |
I think we have about 75% of this already done in
That said we use ETOL on the fire atlas stuff and without writing custom metrics I haven't seen a lot of good data coming out of it that we can't get from other metrics APIs already. So something to think about |
Great to hear the infrastructure is basically already there and we just need to add some custom metrics. Let us see once our services are up, which metrics that could be. What is ETOL? 🙏 |
The Encyclopedia of Trotskyism Online 😉 I mean OTeL |
@j08lue: It also occurred to me this means we'd have to build our own custom runtimes to add OTeL stuff 😞 I really, truly feel like this is yet another example of something that should be plumbed through and turned on in all the upstream libraries 😬 |
Scope out what it would take to gather service health / usage metrics and make them accessible to any harvester of such metrics, e.g. to feed into a Grafana dashboard or OpenSearch.
Similar to what veda-backend has been doing, e.g.
Perhaps related to
Acceptance criteria
The text was updated successfully, but these errors were encountered: