# How to capture jolokia output on to APM Server

**URL:** <https://discuss.elastic.co/t/how-to-capture-jolokia-output-on-to-apm-server/238763>\
**Category:** APM\
**Tags:** java\
**Created:** [June 26, 2020, 12:00am UTC](https://discuss.elastic.co/t/how-to-capture-jolokia-output-on-to-apm-server/238763 "2020-06-26T00:00:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anjana1](https://avatars.discourse-cdn.com/v4/letter/a/22d042/32.png) [@anjana1](https://discuss.elastic.co/u/anjana1)\
**Post date:** [June 26, 2020, 12:00am UTC](https://discuss.elastic.co/t/how-to-capture-jolokia-output-on-to-apm-server/238763/1 "2020-06-26T00:00:07Z")

</div>

**Kibana version** : 7.8

**Elasticsearch version** : 7.8

**APM Server version** : 7.8

**APM Agent language and version** :Java apm agent 1.17.0

**Fresh install or upgraded from other version?** fresh install

**Is there anything special in your setup?** For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc. :-----No

I am exposing some Mbeans in my application using Jolokia agent. I would like to access these Mbeans attributes in my elastic search. I have found JMX configuration options using APM agent , but we can only capture "numbers" using capture\_jmx\_metrics. My Mbeans have many String Attributes which I would like to move over to elastic search. Is that achievable ? I also cannot use Metric beats or logstash as its a lot of overload and do not want to have beats running on each and every systems ..

below image shows the String type Mbean attributes which I would like to access in Elastic

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/5/65fdb542bc95b365398ac46e311a48dc1f1dc1a9.png)

---

<div class="post-metadata">

**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\
**Post date:** [June 26, 2020, 8:00am UTC](https://discuss.elastic.co/t/how-to-capture-jolokia-output-on-to-apm-server/238763/2 "2020-06-26T08:00:10Z")

</div>

Hi 👋

Currently, APM Server only supports numbers as metric values, that's why `cpature_jmx_metrics` also doesn't support to capture string attributes of MBeans.

See also

> <https://github.com/elastic/apm-server/blob/6ba318f5ed3326bc7ade33b94bcaa8cdb07e636a/docs/spec/metricsets/sample.json#L7>

Could you give an example of a string attribute you want to monitor, how you plan to visualize and what insight you get from it?

---

<div class="post-metadata">

**Author:** ![anjana1](https://avatars.discourse-cdn.com/v4/letter/a/22d042/32.png) [@anjana1](https://discuss.elastic.co/u/anjana1)\
**Post date:** [June 26, 2020, 7:02pm UTC](https://discuss.elastic.co/t/how-to-capture-jolokia-output-on-to-apm-server/238763/3 "2020-06-26T19:02:42Z")

</div>

We have Mbeans that provides service statuses ,service names, long out put for errors for services status which all have string formats. So it is more of an application status monitoring than performance monitoring

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 17, 2020, 3:02pm UTC](https://discuss.elastic.co/t/how-to-capture-jolokia-output-on-to-apm-server/238763/4 "2020-07-17T15:02:43Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.