I am trying to add Tomcat-JMX Integration to the Datadog Agent, in order to
achieve Remote Monitoring .
I am following the docs
https://docs.datadoghq.com/containers/guide/autodiscovery-with-jmx/?tab=helm#autodiscovery-annotations
[https://datadog-docs.imgix.net/images/dd-docs-meta-image.png]<https://docs.datadoghq.com/containers/guide/autodiscovery-with-jmx/?tab=helm#autodiscovery-annotations>
Autodiscovery with
JMX<https://docs.datadoghq.com/containers/guide/autodiscovery-with-jmx/?tab=helm#autodiscovery-annotations>
Datadog, the leading service for cloud-scale monitoring.
docs.datadoghq.com
This is the Environment I am using in my case.
I am trying to integrate JMX in one my Deployment, in AKS environment and I am
using Helm to upgrade my environment.
as suggested in the documentation., I am adding the annotations in my
deployment file in helm structure.
My agent is JMX enabled, and i can see in deployment logs.
I have configured a service for this deployment and its reflecting.
Issue I am facing :
I am trying to add my annotations, in the deployment file, after deployment,
it should be able make the remote connection , but its showing these logs in
the agent.
while i check the Java process., even its not reflecting this JMX process , it
seems JMX process is not at all created, in my case.,
error i am facing after deployment"
========
JMXFetch
========
Information
==================
runtime_version : 11.0.18
version : 0.47.8
Initialized checks
==================
tomcat
instance_name : tomcat-10.75.12.143-1099
message : Unable to instantiate or initialize instance 10.75.12.143:1099.
Is the target JMX Server or JVM running? Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: 10.75.12.143; nested
exception is:
java.net.ConnectException: Connection refused (Connection refused)]
metric_count : 0
service_check_count : 0
status : ERROR
instance_name : tomcat-10.75.12.143-1099
message : Unable to instantiate or initialize instance 10.75.12.143:1099.
Is the target JMX Server or JVM running? Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: 10.75.12.143; nested
exception is:
java.net.ConnectException: Connection refused (Connection refused)]
metric_count : 0
service_check_count : 0
status : ERROR
Failed checks
=============
no checks
These are the annotations i have tried to implement JMX in my case:
ad.datadoghq.com/{{ .Values.configmap.app.name }}-container.checks: >-
{
"tomcat": {
"init_config": {
"is_jmx": true,
"collect_default_metrics": true
},
"instances": [{
"host": "%%host%%",
"port": "1099"
}]
}
}
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
- name: JAVA_OPTS
value: >-
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.port=1099
-Dcom.sun.management.jmxremote.rmi.port=1099
-Djava.rmi.server.hostname=$(POD_IP)
-Djava.net.preferIPv4Stack=true
-Dcom.sun.management.jmxremote.host=$(POD_IP)
Even i tried by altering some of the unwanted annotations, I am not getting the
expected result., ie., remote JMX connection.,
I would requet your help in this.,
Thanks in advance!
Thanks & Regards,
--
SAI VAMSI .B
Senior DevOps Engineer
________________________________
From: Christopher Schultz <ch...@christopherschultz.net>
Sent: Tuesday, November 28, 2023 19:41
To: users@tomcat.apache.org <users@tomcat.apache.org>
Subject: [EXT] Re: Datadog _ JMX Integration facing connection issues.
External Email: Use caution with links and attachments.
Sai Vamsi,
On 11/28/23 04:29, Bodavula, Sai Vamsi Mohan Krishna (TR Technology) wrote:
> Hello team,
> I am trying to add Tomcat-JMX Integration to the Datadog Agent, in order
> to achieve Remote Monitoring .
> I am following the docs
> https://urldefense.com/v3/__https://docs.datadoghq.com/containers/guide/autodiscovery-with-jmx/?tab=helm*autodiscovery-annotations__;Iw!!GFN0sa3rsbfR8OLyAw!flrd6o4JKEdfTeHqFXZnxrdwVlDfgIQWa0LA1ItCAwqquaEQHF1TQrWhTdEdCz8b0U5R2hKiyy7adAu09KNW3__LBlrGJg7Il1X4ugDoVeSJPw$
>
> <https://urldefense.com/v3/__https://docs.datadoghq.com/containers/guide/autodiscovery-with-jmx/?tab=helm*autodiscovery-annotations__;Iw!!GFN0sa3rsbfR8OLyAw!flrd6o4JKEdfTeHqFXZnxrdwVlDfgIQWa0LA1ItCAwqquaEQHF1TQrWhTdEdCz8b0U5R2hKiyy7adAu09KNW3__LBlrGJg7Il1X4ugDoVeSJPw$
> >
>
> *_This is the Environment I am using in my case._*
> I am trying to integrate JMX in one my Deployment, in AKS environment
> and I am using Helm to upgrade my environment.
> as suggested in the documentation., I am adding the annotations in my
> deployment file in helm structure.
> My agent is JMX enabled, and i can see in deployment logs.
> I have configured a service for this deployment and its reflecting.
>
>
> *_Issue I am facing :_*
> I am trying to add my annotations, in the deployment file, after
> deployment, it should be able make the remote connection , but its
> showing these logs in the agent.
> while i check the Java process., even its not reflecting this JMX
> process , it seems JMX process is not at all created, in my case.,
> *
> *
> *_Following are the annotations i am using in my case
>
> _*
> Even i tried by altering some of the unwanted annotations, I am not
> getting the expected result., ie., remote JMX connection.,
I'm sorry, but this list does not allow attached or embedded images. Can
you copy/paste your logs into the text and try again?
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
