Page History

OBJECT_CONFIG

This is configuration attributes for various objects (e.g. Queue managers, queues, topics, etc.) deployed within the MQ landscape. This could conceivably be generated into MQSC or other commands most-readily, but is currently provided in JSON or XML format with all the attribute details.

Object configuration is collected through a polling mechanism and as such is not an event-driven approach, and the data will contain identical attribute configuration if the object has not changed since the last poll.

objectData.log

queueData.log

• Potentially generate MQSC from data.
• Identify issues with deployed configurations.
• Document and audit deployed configurations.

EVENT_MESSAGE

This is event data that can be retrieved in a delta-style approach. Once activated, the statistical data will be pushed to a queue from which LAMAXU reads.  When appropriately configured, it should only have information relative to the last publish.

eventData.log

• Generate alerts from statistic data
• Join data sets to fulfil fulfill monitoring gaps such as dynamic queues associated with topics.

STATUS

Point in time info received from objects.

statusData.log

• Status information to be consumed by enterprise monitoring solutions.

CONFIG_EVENT

Events that can be generated about object modifications and changes if configured.

eventData.log

• Potentially utilize information to synchronize with version control and version all configuration.
• Potentially utilize for version controlled configurations.

• Send config change events into SIEM monitoring.

STATS_MESSAGE

Message statistics information from either a RESETQSTATS or via the SYSTEM.ADMIN.STATISTICS.QUEUE

statsData.log

• Potentially utilize information to synchronize with version control and version all configurationCapture message volume statistics information for use with operational capacity planning activities.