JMX APM only displays MBean attribute for 'int' data type

We've had great success when developers expose MBeans as numeric data types. The problem is we'd like to fetch 'boolean', 'string' and/or composite data types.

---

Example Use Case:

Did file get sent to destionation (return: true/false)

---

Is this supported (ie are we doing something wrong), or would it be a feature request in a future version of APM?

Find more posts tagged with

mbean

string

jmx

boolean

Accepted answers

tomb

**I have a service that pushes data to an API. As part of this process, the application reports one of the following: "PushNotAttempted" , "PushSucceeded", or "PushFailed". I would like to to warn on "PushNotAttempted" and alert on "PushSucceeded".

This is an ideal candidate for using enum, which can be exposed as numeric attribute, i.e.:

PushSucceeded = 0

PushNotAttempted = 1 <= set component Statistic Warning Threshold, equal to 1

PushFailed = 2 <= set component Statistic Critical Threshold, equal to 2

**Is there a white paper or doc that outlines to developers what types of JMX objects can be read? I'd like to build a best practice document as we drive for greater utilization of Orion/JMX.

Some information is in Administrator Guide, but to be more specific you can monitor:

simple Java types: byte, short, int, long, float, double, java.lang.Byte, java.lang.Short, java.lang.Integer, java.lang.Long, java.lang.Float, java.lang.Double
sub-items of composite types (CompositeData, HashMap), which are any of mentioned simple types

Attributes, that can be monitored by APM are shown with checkbox in JMX wizard.

All comments

uncleakamai

...more specifically the CompositeData object for Java 6 JMX...

tomb

Hi uncleakamai,

I understand your use case for boolean, but currently this not supported type in APM. As a workaround, couldn't your MBean developers expose the boolean type as a numeric attribute returning 0 / 1 instead?

I can't think of any use case for string types though. Can you give some examples?

Now to your next question - composite attributes are supported by APM. There is just minor limitation - their subitems must be simple types. You can use JMX wizard to browse them.

uncleakamai

**yes they can...thats a valid workaround but I was hoping to not have to change anything. will implement

I can't think of any use case for string types though. Can you give some examples?

**I have a service that pushes data to an API. As part of this process, the application reports one of the following: "PushNotAttempted" , "PushSucceeded", or "PushFailed". I would like to to warn on "PushNotAttempted" and alert on "PushSucceeded".

Now to your next question - composite attributes are supported by APM. There is just minor limitation - their subitems must be simple types. You can use JMX wizard to browse them.

**Is there a white paper or doc that outlines to developers what types of JMX objects can be read? I'd like to build a best practice document as we drive for greater utilization of Orion/JMX.

tomb

**I have a service that pushes data to an API. As part of this process, the application reports one of the following: "PushNotAttempted" , "PushSucceeded", or "PushFailed". I would like to to warn on "PushNotAttempted" and alert on "PushSucceeded".

This is an ideal candidate for using enum, which can be exposed as numeric attribute, i.e.:

PushSucceeded = 0

PushNotAttempted = 1 <= set component Statistic Warning Threshold, equal to 1

PushFailed = 2 <= set component Statistic Critical Threshold, equal to 2

**Is there a white paper or doc that outlines to developers what types of JMX objects can be read? I'd like to build a best practice document as we drive for greater utilization of Orion/JMX.

Some information is in Administrator Guide, but to be more specific you can monitor:

simple Java types: byte, short, int, long, float, double, java.lang.Byte, java.lang.Short, java.lang.Integer, java.lang.Long, java.lang.Float, java.lang.Double
sub-items of composite types (CompositeData, HashMap), which are any of mentioned simple types

Attributes, that can be monitored by APM are shown with checkbox in JMX wizard.

aLTeReGo

The latest JMX component monitor in the SAM 5.2 beta includes support for Boolean values. If you're an existing APM/SAM customer under active maintenance you can sign-up here to participate in the beta. We'd love to get your feedback on this feature.

To learn more about what's new in the SAM 5.2 beta please read my blog postings below.

SAM 5.2 Beta 2 - Soup's On

SAM 5.2 Beta is Now Available

omavel

Composite Data is still not supported by SAM?

omavel

Well ok, selfanswer:

Should add Key parameter