https://www.puppet.com/community logo
Join Slack
Powered by
This message was deleted.
# puppet
s
This message was deleted.
c
Anything that gets instrumented via the Dropwizard Metrics library automatically gets an MBean registered with JMX and the 
/metrics/v2
API allows you to query those MBeans via HTTPs instead of using the JMX protocol (more config, something like 3 extra ports to route through firewalls, one of which might be randomly assigned during startup... head desk ) In contrast, the 
/status
API only returns info the developers added to the various status callback functions. So, if someone slaps some instrumentation in, but doesn't go the extra mile to add a summary of that to 
/status
, then you need to talk to 
/metrics/v2
.
n
Ah okay, good to know. Thanks.
I'm looking into scraping metrics with telegraf and the jolokia2_agent input: ā€¢ https://github.com/influxdata/telegraf/tree/master/plugins/inputs/jolokia2_agent
/metrics/v2
would be the appropriate endpoint for that, correct?
c
Yup. That route leads right to a Jolokia servelet.
Although, I think it has a cert auth gate these days --- so you'll want to give the Telegraf agent access to a Puppet SSL keypair.
n
Yeah, I had to go through the whole auth.conf dance first before I could even start testing it.
Which... I expected I had to, but couldn't find any docs that explicitly state "you must allow access to 
/metrics/v2
in auth.conf to use this" šŸ˜•
Open in Slack
PreviousNext
Powered by