-
Notifications
You must be signed in to change notification settings - Fork 5
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
Custom Metrics #3
Comments
To understand the use case better, what kind of metrics do you want to report to Dynatrace? Custom metrics is on our roadmap for the SDK. In the meantime, you can either call the REST API or have a look at custom request attributes to see if this could fit your use case. roadmap: https://answers.dynatrace.com/spaces/483/dynatrace-product-ideas/idea/198106/planned-features-for-oneagent-sdk.html |
We have plenty of usecases and many teams are requesting for JMX like features in dynatrace. Currently they have to implement rest calls, as mentioned by you. This can be dangerous for the cluster, since it can be easily overwhelmed by these calls. So some usecases are:
|
thanks for the details and sorry for the late answer, I have missed the notification. The use case you describe is totally in sync with what we want to achieve. As mentioned earlier this is on the roadmap (you can follow it there: https://answers.dynatrace.com/spaces/483/dynatrace-product-ideas/idea/198106/planned-features-for-oneagent-sdk.html) but not available at the moment. |
Is there an ETA for the tracing of custom services? Could someone point me to the right API endpoint which could be used to trace custom metrics. |
Hi @moeriki - are you interested in custom metrics or custom services? and what is your use case? Note that you are commenting on closed issue, please consider creating a new issue for your questions. |
What is the best way to provide custom metrics from within a nodejs application.
Providing a function within the sdk would reduce the need for rest calls and reduce complexity of deployments. Are there any other possibilities?
The text was updated successfully, but these errors were encountered: