For telegraf agent to collect metrics for some of the application services, you must make modifications in the end point VMs. After you make these modifications, the agent starts collecting metrics. You must SSH to the virtual machine where you have deployed the agent and modify the configuration files.

Apache HTTPD

For the agent to collect metrics, modify the conf file available in /etc/httpd/conf.modules.d/status.conf and enable the mod_status for the HTTPD plugin.

<IfModule mod_status.c>

<Location /server-status>

    SetHandler server-status


ExtendedStatus On


If the conf file is not available, you must create one. Restart the HTTPD service after modifying the conf file with the following command:

systemctl restart httpd

Java Application

Support for Java application monitoring is currently limited to applications that support jolokia based JMX monitoring. Currently, as part of Java plugin activation, both the jolokia.jar and jolokia.war files are placed in the "Installed Path". If the Java application to be monitored is a servlet container, then the jolokia.war file is automatically deployed to the "Installed Path" that you provided when you configured the Java application in vRealize Operations Cloud. If auto deployment is not supported or not enabled, restart the application after activating the plugin or refer to the application's product documentation for the deployment of manual .war.

For all other java applications, first activate the plugin then include the path to the jolokia.jar file in the "-javaagent:" JVM flag as a command line parameter. For example, "-javaagent:/<path_to_jolokia>/jolokia.jar", <path_to_jolokia> is the "Installed Path" which was provided during application configuration. Restart the application.

Note: For monitoring a customized third-party java application, ensure that:
  • The jolokia based JMX monitoring is supported.
  • In case auto deploy is turned off, manual .war deployment is supported for servlet container application.
  • "-javaagent:" JVM flag is added as part of the command line parameter (JVM_OPTS)


Add the following lines to the conf file available in /etc/nginx/nginx.conf:

http {
    server {
        location /status {
            stub_status on;
   access_log off;
   allow all;

Restart the Nginx service with the following command:

systemctl restart nginx


In the configuration file available in the /var/lib/pgsql/data/pg_hba.conf, change the value of local all postgres peer to local all postgres md5 and restart the service with the following command:

sudo service postgresql restart


To monitor the Cassandra database application, the Jolokia jar must be included as a JVM input to the Cassandra database application. Complete the following steps:

  1. Modify /etc/default/cassandra.

    echo "export JVM_EXTRA_OPTS=\"-javaagent:/usr/share/java/jolokia-jvm-1.6.0-agent.jar=port=8778,host=localhost\"" | sudo tee -a /etc/default/cassandra

    You can download the latest version of the Jolokia agent from For a .JAR file deployment, you have to restart the application service after including the full file path of the JAR in the JMX argument of the JAVA process which you are monitoring.

  2. Alternatively, you can enable the agent by modifying Include the following line at the end of the

    JVM_OPTS="$JVM_OPTS -javaagent:/usr/share/java/jolokia-jvm-1.6.0-agent.jar=port=8778,host=localhost"

    After you see the JVM inputs, restart the Cassandra service.

Oracle Database

To monitor the Oracle database, complete these steps:

  1. Download the instant client library from:

    You must download the Oracle instant library and included it in the PATH.

  2. Create a User.

    CREATE USER <UserName> IDENTIFIED BY <yourpassword>;
     GRANT select_catalog_role TO <UserName>;
  3. Install Python 3.6 or later.

    python3 -m pip install cx_Oracle --upgrade
  4. Set the PATH of TNS_ADMIN.

    For example, the path for TNS_ADMIN will be similar to c:\app\product\<version>\dbhome_1\NETWORK\ADMIN”.


Oracle database cannot be activated on Linux platforms.

Active MQ 5.16 and Later Versions

To activate Active MQ 5.16 and later versions, complete the following steps:

  • Navigate to /opt/activemq/apache-activemq-5.16.0/webapps/api/WEB-INF/classes/jolokia-access.xml

  • Remove or comment out the following lines:

  • Restart the Active MQ service.

Microsoft SQL Server

The user account must have the following permissions to monitor the Microsoft SQL Server application service with Telegraf.

USE master;
CREATE LOGIN [telegraf] WITH PASSWORD = N'mystrongpassword';
Note: If you want to monitor named instances of the Microsoft SQL Server application service, then the plugin activation input should not have the Port field configured. Use Port only when there is no instance in the server (default 1433).