IBM MQ fields
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
ibmmq Module
IBM MQ error logs
ibmmq.errorlog.installation-
This is the installation name which can be given at installation time. Each installation of IBM MQ on UNIX, Linux, and Windows, has a unique identifier known as an installation name. The installation name is used to associate things such as queue managers and configuration files with an installation.
type: keyword
ibmmq.errorlog.qmgr-
Name of the queue manager. Queue managers provide queuing services to applications, and manage the queues that belong to them.
type: keyword
ibmmq.errorlog.arithinsert-
Changing content based on error.id
type: keyword
ibmmq.errorlog.commentinsert-
Changing content based on error.id
type: keyword
ibmmq.errorlog.errordescription-
Please add description
type: text
example: Please add example
ibmmq.errorlog.explanation-
Explains the error in more detail
type: keyword
ibmmq.errorlog.action-
Defines what to do when the error occurs
type: keyword
ibmmq.errorlog.code-
Error code.
type: keyword