Display Event Repository Configuration Information

Display Event Repository configuration information.

Before you begin

This procedure assumes that you have set up the Event Repository and are logged on to a machine where the MATRIXX Engine software is installed. To run Event Repository administration scripts on a machine where the MATRIXX Engine software is not installed, see the discussion about setup for Event Repository administration scripts.

Procedure

  1. To view the configuration information of the Event Repository, run the check_event_repository_configuration.py command with the --host option.
    check_event_repository_configuration.py --host serverNameIp

    where serverNameIp is the host name or IP address of a machine on which one of the mongod servers in your replica set is running. Connecting to a host on which your primary mongod server is running is recommended.

  2. If prompted, enter your username and password for connecting to the MongoDB server.

    The following is example output for running the check_event_repository_configuration.py command. This example output is for a sharded MongoDB deployment:

    check_event_repository_configuration.py --user MtxAdmin
    =======================================================================
    check_event_repository_configuration.py started on 2016-03-17 16:41:22
    =======================================================================
    The config server replica set is named 'MtxConfigReplSet':
     - mongod server on 192.168.1.1:27019 is PRIMARY
     - mongod server on 192.168.1.2:27019 is SECONDARY
     - mongod server on 192.168.1.3:27019 is SECONDARY
    
    This database has 3 shards.
    
    Shard 1 replica set is named 'MtxEventReplSet_1':
     - mongod server on 192.168.1.11:27018 is PRIMARY
     - mongod server on 192.168.1.12:27018 is SECONDARY
     - mongod server on 192.168.1.13:27018 is SECONDARY
    
    Shard 2 replica set is named 'MtxEventReplSet_2':
     - mongod server on 192.168.1.21:27018 is PRIMARY
     - mongod server on 192.168.1.22:27018 is SECONDARY
     - mongod server on 192.168.1.23:27018 is SECONDARY
    
    Shard 3 replica set is named 'MtxEventReplSet_3':
     - mongod server on 192.168.1.31:27018 is PRIMARY
     - mongod server on 192.168.1.32:27018 is SECONDARY
     - mongod server on 192.168.1.33:27018 is SECONDARY
    
    Partitioning method: 2
    
    Indexes:
    Found index configuration:  MtxWalletOwnerId_1_EventTime_1 OrderedDict([(u'WalletOwnerId', 1), (u'EventTime', 1)])
    Found index configuration:  MtxEventTime_1 OrderedDict([(u'EventTime', 1)])
    
    Sharding is enabled for database 'MtxEventDatabase'.
    Sharded collections are:
        'MtxEventDatabase.EventCollection20160316', key=OrderedDict([(u'WalletOwnerId', u'hashed')])
        'MtxEventDatabase.EventCollection20160331', key=OrderedDict([(u'WalletOwnerId', u'hashed')])