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

No support for type: java.util.map #125

Closed
KParzival opened this issue Feb 23, 2017 · 5 comments
Closed

No support for type: java.util.map #125

KParzival opened this issue Feb 23, 2017 · 5 comments
Milestone

Comments

@KParzival
Copy link

KParzival commented Feb 23, 2017

Migrating a bunch of hosts from current monitoring solution to Datadog, discovered that this JMX type was not supported by Datadog.

Example output from JTerm:

#mbean = sme:name=ActiveCampaignStats:
CampaignCount = {
  Europe = 4563;
  Asia = 1128;
  All = 82134;
 };
$>

Which in JConsole might look something like:

AttributeName:        AttributeValue:
=======================================
CampaignCount         {Europe=4563,Asia=1128,All=82134}
@yannmh
Copy link
Member

yannmh commented Feb 23, 2017

Hey @KParzival,

Maps are actually supported: use the syntax $variable.$key in the list of attributes to grab the desired parameter. Here is an example: https://github.com/DataDog/jmxfetch/blob/master/src/main/resources/jmx-2.yaml

Please let me know if that helps.

@KParzival
Copy link
Author

KParzival commented Feb 23, 2017

Hi @yannmh thanks for the reply, unfortunately, I tried that exact syntax, it doesn't work.
I then worked directly with a DD Support person.
When running:
/etc/init.d/datadog-agent jmx list_everything
the MBeans that have only java.util.map types don't even show up as being grabbed by JMXFetch, and java.util.map is not in the list of supported types listed here: https://github.com/DataDog/jmxfetch/blob/master/src/main/java/org/datadog/jmxfetch/Instance.java#L23-L28

@yannmh
Copy link
Member

yannmh commented Feb 23, 2017

Thanks for the details @KParzival,

Could you send us a flare please? It's likely a small code change and this would be very helpful.

@KParzival
Copy link
Author

Hi @yannmh,
Already sent a flare today when working on a case with Alex/Grant.

Case# 82354

@yannmh yannmh added this to the 0.13.0 milestone Mar 2, 2017
@yannmh
Copy link
Member

yannmh commented Mar 2, 2017

Thanks @KParzival. We found the issue and are working on a fix for the upcoming agent release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants