Skip to content
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

Agent 3.0 PREVIEW.4 In Process Agent - Custom JMX Metrics with Boolean Values Not Collected #1235

Closed
zoomingrocket opened this issue May 13, 2020 · 3 comments
Milestone

Comments

@zoomingrocket
Copy link

Using PREVIEW.4 in process java agent with custom jmx metrics configured in json for collection. JMX Metric will show in Metrics list until first time a value is set either to true or false and it will stop showing up in Application Insights

Request to either provide a mechanism to define type of jmx attribute so that a translation of boolean to numeric can be done or auto parse

@zoomingrocket zoomingrocket changed the title PREVIEW.4 In Process Agent - Custom JMX Metrics with Boolean Values Not Collected Agent 3.0 PREVIEW.4 In Process Agent - Custom JMX Metrics with Boolean Values Not Collected May 13, 2020
@trask
Copy link
Member

trask commented Jun 10, 2020

Hi @zoomingrocket do you have a single jmx metric that sometimes reports true/false and sometimes reports a numeric value? Curious what is the specific metric? Trying to think how best to capture that.

@zoomingrocket
Copy link
Author

@trask - No i have multiple boolean JMX Metrics that report true/false values, never numeric. Generally used for state indicators whether certain component in JVM is up or down. We are noticing that upon server startup the attribute is not having a value set so attribute shows up in Metric list and when a value is set to either false or true it drops off the Metric list from App Insight. So i was wondering if we can specify the type of attribute in ApplicationInsights.json so that true/false can interpreted as 1/0 numeric values in metric palette and alerts can be setup on same.

@trask trask added this to the future milestone Jun 10, 2020
@trask trask modified the milestones: future, 3.0.0 Sep 13, 2020
@trask
Copy link
Member

trask commented Sep 25, 2020

This is supported now in Preview.7

@trask trask closed this as completed Sep 25, 2020
trask pushed a commit that referenced this issue Oct 17, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jul 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants