Unlike the statistics produced via a topic, there is no discovery of the attributes available in object STATUS queries.

Unlike the statistics produced via a topic, there is no discovery of the attributes available in object STATUS queries.

Return a standardised value.

Unlike the statistics produced via a topic, there is no discovery of the attributes available in object STATUS queries.

Return a standardised value.

DiscoverAndSubscribe does the work of finding the different resources available from a queue manager and issuing the MQSUB calls to collect the data */.

EndConnection tidies up by closing the queues and disconnecting.

Patterns are very simple, following normal MQ lines except that they can be prefixed with "!" to exclude them.

This function is exported so it can be called during the build/test process for automatic generation of some of the mHeur map elements.

Return the current command level */.

This will be the preferred interface in future to get at the values, at which point it will change to not use the global public variables.

Return the current platform - the MQPL_* definition value.

Return the nominated MQCA*/MQIA* attribute from the object's attributes stored in the map.

Return the nominated MQCA* attribute from the object's attributes stored in the map.

InitConnection connects to the queue manager, and then opens both the command queue and a dynamic reply queue to be used for all responses including the publications */.

If we need to list the channels that match a pattern.

If we need to list the channels that match a pattern.

If we need to list the queues that match a pattern.

If we need to list the topics that match a pattern.

Normalise converts the value returned from MQ into the correct units such as converting MB to bytes.

ProcessPublications has to read all of the messages since the last scrape and update the values for every relevant gauge.

Unlike the statistics produced via a topic, there is no discovery of the attributes available in object STATUS queries.

Unlike the statistics produced via a topic, there is no discovery of the attributes available in object STATUS queries.

Return a standardised value.

Return a standardised value.

ReadPatterns is called during the initial configuration step to read a file containing object name patterns if they are not explicitly given on the command line.

* A collector can set the locale (eg "Fr_FR") before doing the discovery * process to get access to the MQ-translated strings */.

Unlike the statistics produced via a topic, there is no discovery of the attributes available in object STATUS queries.

Return a standardised value.

Unlike the statistics produced via a topic, there is no discovery of the attributes available in object STATUS queries.

Return a combination of the topic name and the status query type so we get unique keys in the map.

Return a standardised value.

Return a standardised value.

* Check any important parameters - this must be called after DiscoverAndSubscribe * to maintain compatibility of the package's APIs.

Most of the ATTR_ fields can be inherited from the channel.go module.

"repos" or "normal" = "full" or "partial".

clussdr status.

yes/no.

The next attributes are given the same name as the published statistics from the amqsrua-style values.

This is the Highest Depth returned over an interval via the RESET QSTATS command.

Uncommitted messages - on Distributed platforms, this is any integer; but on z/OS it only indicates 0/1 (MQQSUM_NO/YES).

Some of the log-related metrics are effectively duplicated between QMSTATUS and published resources eg LOGUTIL.

To provide a non-empty value for certain fields.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

These object types are the same where possible as the MQI MQOT definitions but there are some unique types here so that correspondence is not completely identical.

QMgrMapKey can never be a real object name and is therefore useful in maps that may contain only this single entry.

This are used externally so we need to maintain them as public exports until there's a major version change.

This are used externally so we need to maintain them as public exports until there's a major version change.

This are used externally so we need to maintain them as public exports until there's a major version change.

This are used externally so we need to maintain them as public exports until there's a major version change.

This are used externally so we need to maintain them as public exports until there's a major version change.

This are used externally so we need to maintain them as public exports until there's a major version change.

This are used externally so we need to maintain them as public exports until there's a major version change.

This are used externally so we need to maintain them as public exports until there's a major version change.

This are used externally so we need to maintain them as public exports until there's a major version change.

This are used externally so we need to maintain them as public exports until there's a major version change.

May move to a config option at some point.

The AllMetrics structure is the top of the tree, holding the set of classes.

For now, only queues are subscribable through this interface but there are now Application resources that might be relevant at some time.

Setup for the 7 levels of logging that logrus allows, even if we don't intend to use all of them for now.

MonClass described the "classes" of data generated by MQ, such as DISK and CPU.

MonElement describes the real metric element generated by MQ.

MonType describes the "types" of data generated by MQ.

This structure contains additional info about any object type that may need to be held.

All we care about for attributes are ints and strings.