Configuring IBM MQ monitoring in Docker
Configure the IBM MQ sensor based on the deployment of the Instana agent and the queue manger in your environment.
Deployment-based configuration
The following table displays the configurations for different agent-queue manager deployment scenarios:
| Agent-queue manager deployment | Monitoring method | Configuration |
|---|---|---|
| Both in Docker in the same host | Local monitoring with client binding mode | Configure connection parameters, excluding host and port, in the agent configuration.yaml file |
| In different environments (VM, Docker, or Kubernetes) | Remote monitoring with client binding mode | Configure connection parameters, including host and port, in the agent configuration.yaml file. |
Configuring local monitoring with client binding mode
When the Instana host agent and IBM MQ run in different Docker containers in the same machine, only local monitoring with the client binding mode is supported because the Instana host agent and IBM MQ run in different Docker operating systems.
In such scenario, you need to configure IBM MQ connection parameters in the agent configuration file. Because IBM MQ sensor discovers IBM MQ queue manager instances automatically, you don't need to set the host and port in the agent configuration file.
The configuration steps are the same as in the Local monitoring with client binding mode section.
Configuring remote monitoring with client binding mode
The configuration steps are the same as in the Remote monitoring with client binding mode section. By using the client binding mode in the remote monitoring, you need to configure the host and port because IBM MQ sensor can't discover them in remote monitoring.