Instana monitoring: Configuring agents

Mount the keystore to the IBM® Instana® agents, then configure monitoring for a specific queue manager.

Mounting the keystore to the IBM Instana agents

1. Create a secret from your JKS keystore in the IBM Instana agent namespace.
   Run the following command, replacing keystore_secret_name with the name you want to use. Perform this replacement in all subsequent steps.

   oc create secret generic keystore_secret_name --from-file=./application.jks -n instana-agent

2. In the instana-agent namespace, use the oc edit daemonset instana-agent command to edit the instana-agent daemonset to include the following additional volumeMount and volume:

   volumeMounts:
   - name: mq-key-jks-name
      subPath: application.jks
      mountPath: /opt/instana/agent/etc/application.jks 
   volumes:
   - name: mq-key-jks-name
      secret:
         secretName: keystore_secret_name

Configuring monitoring for a specific queue manager

3. In the instana-agent namespace, use the oc edit configmap instana-agent command to edit the instana-agent configmap.
4. Add the following section under configuration.yaml: |. If you have already defined this section, then just add the new queue manager to the list.

       com.instana.plugin.ibmmq:
         enabled: true
         poll_rate: 60
         queueManagers:
            QUEUE_MANAGER_NAME:
               channel: 'INSTANA.A.SVRCONN'
               keystorePassword: 'your_password'
               keystore: '/opt/instana/agent/etc/application.jks'
               cipherSuite: 'TLS_RSA_WITH_AES_256_CBC_SHA256'

   where

   • your_password is the password to your JKS keystore
   • QUEUE_MANAGER_NAME is the name of the underlying IBM MQ queue manager to deploy, rather than the name of the Queue Manager Operand.

   Note: If QUEUE_MANAGER_NAME is not set to the underlying queue manager name, and is instead set to the Operand, monitoring will not work. The underlying name is defined in spec.queuemanager.name for the Queue Manager Operand.
5. Delete the instana-agent pods in the instana-agent namespace. This causes them to restart, and to begin monitoring with the new settings.