Lamaxu models the data it collect and separates it into the following object categories.
Category | Description | Log file | Use Case |
---|---|---|---|
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 |
|
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 |
|
STATUS | Point in time info received from objects. | statusData.log |
|
CONFIG_EVENT | Events that can be generated about object modifications and changes if configured. | eventData.log |
|
STATS_MESSAGE | Message statistics information from either a RESETQSTATS or via the SYSTEM.ADMIN.STATISTICS.QUEUE | statsData.log |
|
TRACE | Activity trace messages | traceData.log | Capture message ativity trace inf |