You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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.
@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.
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
The text was updated successfully, but these errors were encountered: