-
Notifications
You must be signed in to change notification settings - Fork 209
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
Allow access to MetricSet and improve memory allocation on MetricSample #1236
Conversation
❕ Build Aborted
Expand to view the summary
Build stats
Trends 🧪Steps errorsExpand to view the steps failures
|
If this is ok to merge I would like to start with |
@russcam can we merge this? |
@glucaci let me try to give an overview on what we had in mind. We'd like to have something similar across the Elastic APM Agents. One metrics library we wanted to have support for across agents is Prometheus: #1127 - at the moment we don't actively work on that in .NET. The current metrics API was internal on purpose: we were not sure we'd like to have it public in its current form. If we make anything public, likely we'd prefer to have an internal sync with other Elastic APM agent devs to make sure that if we make this public then the API is somewhat similar across agents and we don't end up breaking it later. So what I want to say with this: we may need to think about this a bit longer. |
Thanks and I understand your point of view. I thought that this #322 (comment) was the final decision. On the other hand is like a buggy API on In my opinion this will be a fix for anyone how wants to use custom metrics with |
@glucaci thank you for your interest in improving the agent regarding metric collection! The |
Hi @russcam, I'm not sure that The main point of this PR is to make |
For users to send custom metrics, must have access to
MetricSet
as in #322 mentioned.In the same time I did an optimization on
MetricSample
.I'm working o a prototype to integrate
IPayloadSender.QueueMetrics
withMetrics.NET
library