mgetinfo examples


This section contains examples of mgetinfo.

mgetinfo config example

mgetinfo -n aspen config

This command produces output similar to the following:

cellName=aspen
HomeDir=C:/mcell/server
KBDir=C:/mcell/server/etc/aspen/kb/
ConfigFile=C:/mcell/server/etc/mcell.conf
TraceConfigFile=C:/mcell/server/etc/mcell.trace
TraceDefaultFile=C:/mcell/server/tmp/aspen/trace
ServerDirectoryFile=C:/mcell/server/etc/mcell.dir
PropagateConfigFile=C:/mcell/server/etc/mcell.propagate
ModifyConfigFile=C:/mcell/server/etc/mcell.modify

mgetinfo metrics example

mgetinfo metrics

This command produces output similar to the following:

ReceivedEvents
Number of received event messages
60
0
0
300
1
0
3616974
12534
0
ErrorEvents
Number of events containing errors
60
0
0
300
0
0
3616974
94
0
DroppedEvents
Number of events dropped by rules
60
0
0
300
1
0
3616974
5700
0
StoredEvents
Number of events entered in the DB
60
0
0
300
0
0
3616974
6834
0
RemovedEvents
Number of events removed by DB cleanup
60
0
0
300
0
0
3616974
27451
0
DeletedEvents
Number of events deleted by clients
60
0
0
300
0
0
3616974
0
0
PropagatedEvents
Number of propagated events
60
0
0
300
0
0
3616974
102
0
ConnectedSources
Number of connected sources
60
0
0
300
0
0
3616974
0
0

The output for mgetinfo metrics consists of the metric name, a metric description and short term, medium term, and long term metrics, each consisting of

  • Period of time for which the metric is counted (in seconds) 
  • Total count of metric items during the period 
  • Average occurrence of the metric item over the time period (in items per second)

For example, in the first line of the sample output,

  • The metric name is ReceivedEvents. 
  • The description for ReceivedEvents is Number of received event messages. 
  • The short term metric is 60 seconds, during which 0 events were received, resulting in an average occurrence of 0 events received per second. 
  • The medium term metric ran for 300 seconds, during which 1 event was received, resulting in an average of 0 events received per second. 
  • The long term metric ran for 3616974 seconds, during which 12534 events were received, resulting in an average of 0 events received per second.

mgetinfo param example

The following figure shows an example of mgetinfo param.

Example of mgetinfo param

mgetinfo -n aspen param

This command produces output similar to the example shown in the following figure.

mgetinfo param command output

Trace=Yes
TraceSrc=No
TraceRuleLevel=1
TraceConfigFileName=mcell.trace
TraceDefaultFileName=%T/trace
LicenseServer=
CellOperationLevel=Consolidation
CellOperationRelax=No
.
.
.

mgetinfo services example

The following figure shows an example of mgetinfo services.

Example of mgetinfo services

mgetinfo services

This command produces output similar to the example shown in the following figure.

mgetinfo services command output

MC_SM_COMPONENT            Number of MC SM Component            87
CONNECTIVITY               Number of Connectivity               11
IT_COMPONENT               Number of IT Component               22
LOGICAL_COMPONENT          Number of Logical Component          47
SERVICE_LEVEL_AGREEMENT    Number of Service Level Agreement     7
MC_SM_RELATIONSHIP         Number of MC SM Relationship        126
IMPACT_RELATIONSHIP        Number of Impact Relationship       126
NULL_RELATIONSHIP          Number of Null Relationship          0"

mgetinfo connect example

The following figure shows an example of mgetinfo connect.

Example of mgetinfo connect

mgetinfo connect

This command produces output similar to the example shown in the following figure.

Output of mgetinfo connect

IN browser ImpactExplorer 10.0.10.17:1545  10.0.10.28:1828  Admin  0  2028 2071

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC ProactiveNet 9.6