-
Notifications
You must be signed in to change notification settings - Fork 38
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
Instrumentation infrastructure for plugins #27
Comments
👍 for generic, but skewing Prometheus-friendly. |
Any new thoughts on this? |
I don't understand what this means. |
I think the idea is to codify and expose an API for calculating timings, as we do internally, such that a middleware can do the same to instrument itself, without having to reimplement anything... if that makes sense. |
Ah ok, that is how I took it at first too but not sure how that relates to prometheus? We are just talking about the timing and size atoms, like those that already exist? |
/ping @deadtrickster |
Should we consider Open Telemetry for this? I wouldn't mind working on it, but:
|
Add API so plugins can instrument themselves, just like main Elli does. Something generic, or just use Prometheus/Prometheus data model?
The text was updated successfully, but these errors were encountered: