builtin:ibmmq.queue-managers)
Dynatrace needs to know the IBM MQ definition of your alias queues, remote queues, and cluster queues for the end-to-end tracing. Without this information, Dynatrace can still trace all requests but producer and consumer services would not be stitched together.
builtin:ibmmq.queue-managers
group:mainframe
environment
GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:ibmmq.queue-managers |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:ibmmq.queue-managers | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:ibmmq.queue-managers |
To execute this request, you need an access token with Read settings (settings.read
) scope. To learn how to obtain and use it, see Tokens and authentication.
name
clusters
Name of the cluster(s) this queue manager is part of
AliasQueue
objectaliasQueue
baseQueue
clusterVisibility
Name of the cluster(s) this alias should be visible in
RemoteQueue
objectlocalQueue
remoteQueue
remoteQueueManager
clusterVisibility
Name of the cluster(s) this local definition of the remote queue should be visible in
ClusterQueue
objectlocalQueue
clusterVisibility
Name of the cluster(s) this local queue should be visible in