MongoDB Extended Discovery

Overview

The 10genMongoDB_DBDetails pattern performs a deep discovery of the MongoDB database server configuration, models Databases and creates the respective relationships between them and the MongoDB Software Instance.

Trigger

The 10genMongoDB_DBDetails pattern triggers off the creation or confirmation of a MongoDB Server, MongoDB Config Server or MongoDB Shard Server software instances.

Listening ports

The port is inherited from the triggering SoftwareInstance.

Modeling Databases

Databases are modeled as 'Database' nodes of the parent SoftwareInstance.

The pattern retrieves the list of databases using the following methods:

  • MondoDB API provider
  • Active command using 'mongo' shell
  • Using directory listing (if <db_path> is set for parent SI)
  • Using '_mdb_catalog.wt' file
  • Using 'WiredTiger.wt' file


The following table describes the attributes returned:

Modeled attributeDescription
type"MongoDB Database"
name"MongoDB Database <Database name>"
short_nameDatabase name
instanceDatabase name
logical_database_type"MongoDB Database"

Modeling Local Queues

Local queues are modeled as Detail nodes of the either IBM WebSphere MQ Series Queue Manager SoftwareInstance (for normal local queues or queue aliases) or the Channel Detail node of the IBM WebSphere MQ Series Queue Manager SoftwareInstance (for local queues of the transmission type).

The IBM_WebSphereMQExtendedDiscovery pattern retrieves the list of local queues from the runmqsc.exe application located in the bin folder of the install root using the following commands:

  • On Windows:
    • echo end|echo dis ql(*) all| "%install_root%\\bin\\runmqsc.exe" <MQ_INSTANCE>
    • echo end|echo dis qa(*) all| "%install_root%\\bin\\runmqsc.exe" <MQ_INSTANCE>
  • On UNIX:
    • echo 'end'|echo 'dis ql(*) all'| %install_root%/bin/runmqsc <MQ_INSTANCE>
    • echo 'end'|echo 'dis qa(*) all'| %install_root%/bin/runmqsc <MQ_INSTANCE>


The following table describes the attributes returned by the command and the regular expressions that are used to retrieve their values:

Modeled attributeRegular Expression
name

^([^\)]+)

cluster relation

CLUSTER\(([^\)]+)\)

type*

USAGE\(([^\)]+)\)

transmission queue

XMITQ\(([^\)]+)\)

remote QM name

RQMNAME\(([^\)]+)\)

max message lengthMAXMSGL\(([^\) ]+)\)
max message depthMAXDEPTH\(([^\) ]+)\)

The type is identified for all Local Queues except Queue Aliases by looking for either "normal" or "transmission" substring in the resulting string.

Note

Modeling System Queues and Channels can be enabled in the configuration section of the pattern. It is disabled by default.

Modeling Remote Queues

Remote queues are modeled as Detail nodes of the Channel node that has them registered.

The IBM_WebSphereMQExtendedDiscovery pattern retrieves the list of remote queues from the runmqsc.exe application located in the bin folder of the install root using the following commands:

  • On Windows:
    • echo end|echo dis qr(*) all| "%install_root%\\bin\\runmqsc.exe" <MQ_INSTANCE>
  • On UNIX:
    • echo 'end'|echo 'dis qr(*) all'| %install_root%/bin/runmqsc <MQ_INSTANCE>


The following table describes the attributes returned by the command and the regular expressions that are used to retrieve their values:

Modeled attributeDescriptionValue examples                         Regular Expression
nameQueue nameREM.INVENTQ

QUEUE\(([^\)]+)\)

name of the queue on remote QMName of the queue on remote QMLOCAL.INVENTORY 

RNAME\(([^\)]+)\)

remote QM nameRemote QM name

LONDON

RQMNAME\(([^\)]+)\)

transmission queue nameRelated transmission queuePUNEQ

XMITQ\(([^\)]+)\)

Relationship Creation

The pattern creates a containment relationship with parent MongoDB Software Instance for every database.


Was this page helpful? Yes No Submitting... Thank you

Comments