rbtnguyen
diff --git a/‎content/en/integrations/faq/i-have-a-matching-bean-for-my-jmx-integration-but-nothing-on-collect.md
Lines changed: 39 additions & 4 deletions b/‎content/en/integrations/faq/i-have-a-matching-bean-for-my-jmx-integration-but-nothing-on-collect.md
Lines changed: 39 additions & 4 deletions
diff --git a/‎static/images/integrations/faq/jmx_conf.png
-77.3 KB b/‎static/images/integrations/faq/jmx_conf.png
-77.3 KB
diff --git a/‎static/images/integrations/faq/jmx_metric_type.png
-77.7 KB b/‎static/images/integrations/faq/jmx_metric_type.png
-77.7 KB
@@ -33,13 +33,48 @@ This means that your `Hadoop:service=HBase,name=Master,sub=Server - tag.isActive
 
 Check your `jmx.yaml` file, the following excerpt should show something similar:
 
-{{< img src="integrations/faq/jmx_conf.png" alt="jmx_conf"  >}}
+```yaml
+init_config:
+instances:
+  - name: hbase_master
+    host: localhost
+    port: xxx
+    tags:
+      application: hbase
+      service: master
+    conf:
+      - include:
+          bean: "Hadoop:service=HBase,name=Master,sub=Server"
+          [...]
+            tag.isActiveMaster:
+              alias: jmx.hadoop.hbase.master.server.tag.isActiveMaster
+              metric_type: java.lang.String
+```
 
 The `java.lang.String` metric_type confirms the issue you were seeing in the logs.
 
-To resolve this issue, change the associated metric_type, and ensure that your `jmx.yaml` file has the following configuration:
-
-{{< img src="integrations/faq/jmx_metric_type.png" alt="jmx_metric_type"  >}}
+To resolve this issue, change the associated metric_type, and ensure that your `jmx.yaml` file has the following configuration (note the changes in the last four lines):
+
+```yaml
+init_config:
+instances:
+  - name: hbase_master
+    host: localhost
+    port: xxx
+    tags:
+      application: hbase
+      service: master
+    conf:
+      - include:
+          bean: "Hadoop:service=HBase,name=Master,sub=Server"
+          [...]
+            tag.isActiveMaster:
+              alias: jmx.hadoop.hbase.master.server.tag.isActiveMaster
+              metric_type: gauge
+              values:
+                "true": 1
+                "false": 0
+```
 
 Jmxfetch then knows it's a string and uses this rule to transform that into a numeric metric.