Skip navigation

Sentry Software

5 Posts authored by: Razeem Mohamed Moderator
Share:|

Why Monitoring Studio KM?

As there are no out of the box solutions to monitor the Hitachi Content Platform and pull the data into TrueSight Operations Mgmt , we took up the challenge to cover the monitoring gap using the versatile Monitoring Studio KM from Sentry Software.

 

How we achieved it?

The Hitachi Content Platform provides its health, capacity and performance data through SNMP. We all know that all the Monitoring Studio KM needs is a source of data and a mode to access it. The built-in SNMP polling feature made it simple.

 

Then, we used the Dynamic Object Builder, string search, numeric value extraction and value mapping to complete the monitoring template.

 

What we achieved?

To know more about the list of components and parameters monitored, please refer to Monitoring Hitachi Content Platform

 

Want to know more?

Drop your questions in the comment section and we will be more than happy to respond.

Razeem Mohamed

IronPort Monitoring

Posted by Razeem Mohamed Moderator Sep 25, 2017
Share:|

A new version of the IronPort Monitoring template for Monitoring Studio KM is now available for download from Monitoring IronPort Systems| Sentry Software

Razeem Mohamed

F5 - BigIP Systems

Posted by Razeem Mohamed Moderator Jul 28, 2017
Share:|

The latest of the Monitoring Studio template custom built to monitor the F5-BigIP System is now available for download!!!

 

Monitoring F5 BIG-IP Systems | Sentry Software

 

Any feedback would be appreciated.

 

Thanks

Razeem

Share:|

Often we end up with no solution when it comes down to monitoring in house applications, complex applications, websites, database or any appliance or device for which there is no out of the box monitoring solutions to be into TrueSight Operations Mgmt.

 

If the object(application, service, API, device etc.) to be monitored has any source of data through API, SNMP, WBEM, Command line, Windows service/process/performance counters etc you can very well build a monitoring solution in minutes.

 

When you have something to be monitored,

  • List down the parameters and attributes that you would like to monitor.
  • Identify the best suited protocol to pull the information from the source object to be monitored.
  • Use any external tool like SNMP browser, CIM Navigator or DB analyzer if required. This will help you understand the structure of the data and confirm the availability of the data.
  • Identify the object groups and the parameters that are available for each one of them.
  • Determine the data type of each parameter or attribute.
  • Then start creating the "monitors" (Configuring Groups, Hosts and Monitors) using the built in monitor functions of the Monitoring Studio KM and process the extracted output (4. Processing a Monitor Result Output) if required.
  • Once the data collection is successful, you can configure thresholds (Configuring Thresholds)based on your requirements and configure alert actions (Specifying Alert Actions).
  • You can then export the configuration to be used as a template and deployed on another agents (Deploying your Configuration)

 

At the time of writing this article, I recommend you to use the Monitoring Studio KM v9.4. To create a template, you must use the PATROL Classic Console or the PATROL Central Operator Console.

The data collected by the PATROL Agent can be then integrated into the TrueSight Operations Management.

 

You can refer to the pre-built configuration templates available at Monitoring Studio | Sentry Software  for example.

Share:|

To monitor the EMC disk arrays you will need to configure the EMC SMI-S provider and make sure that the arrays are being discovered by the SMI-S provider to be able to monitor them. The arrays are discovered automatically when they are locally attached to the SMI-S provider. To make sure that the EMC SMI-S provider has discovered the arrays that need to be, you can use the TestSmiProvider tool.

 

This article explains the steps to perform this check.

 

Steps

  • - Logon to the server where the EMC SMI-S provider is installed
  • - Run the TestSmiProvider.exe which can generally be found under “C:\Program Files\EMC\ECIM\ECOM\bin”

 

C:\Program Files\EMC\ECIM\ECOM\bin>TestSmiProvider.exe

Connection Type (ssl,no_ssl) [no_ssl]:

Host [localhost]:

Port [5988]:

Username [admin]:

Password [#1Password]:

Log output to console [y|n (default y)]:y

Log output to file [y|n (default y)]:

Logfile path [Testsmiprovider.log]:

Connecting to localhost:5988

Using user account 'admin' with password '#1Password'

 

########################################################################

## ##

## EMC SMI Provider Tester ##

##   This program is intended for use by EMC Support personnel only.  ##

##   At any time and without warning this program may be revised      ##

##   without regard to backwards compatibility or be ##

##   removed entirely from the kit. ##

########################################################################

  slp    - slp urls slpv    - slp attributes

  cn     - Connect dc      - Disconnect

  disco  - EMC Discover rc      - RepeatCount

  addsys - EMC AddSystem remsys  - EMC RemoveSystem

  refsys - EMC RefreshSystem

 

  ec     - EnumerateClasses ecn     - EnumerateClassNames

  ei     - EnumerateInstances ein     - EnumerateInstanceNames

  ens    - EnumerateNamespaces mine    - Mine classes

 

  a      - Associators an      - AssociatorNames

  r      - References rn      - ReferenceNames

 

  gi     - GetInstance gc      - GetClass

 

  ci     - CreateInstance di      - DeleteInstance

  mi     - ModifyInstance eq      - ExecQuery

  gp     - GetProperty sp      - SetProperty

 

  tms    - TotalManagedSpace tp      - Test pools

  ecap   - Extent Capacity pd      - Profile Discovery

 

  im     - InvokeMethod active  - ActiveControls

  ind    - Indications menu tv      - Test views

 

  st     - Set timeout value lc      - Log control

  sl     - Start listener dv      - Display version info

  ns     - NameSpace vtl     - VTL menu

 

 

  q      - Quit h       - Help

########################################################################

Namespace: root/emc

repeat count: 1

 

 

- Run the command eq at the prompt

(localhost:5988) ? eq

Query Language[DMTF:CQL]:

- Run the below query

Query []: SELECT EMC_ArrayChassis.SerialNumber FROM EMC_ArrayChassis

 

A working provider will return the following for each disk system attached to this provider:

++++ Testing ExecQuery:  ++++

Instance 0:

ObjectPath : //10.0.10.54/root/emc:Clar_ArrayChassis.CreationClassName="Clar_ArrayChassis",Tag="CLARiiON+CKM00083900053"

<INSTANCE  CLASSNAME="Clar_ArrayChassis" >

<PROPERTY NAME="CreationClassName" TYPE="string">

<VALUE>Clar_ArrayChassis</VALUE>

</PROPERTY>

<PROPERTY NAME="Tag" TYPE="string">

<VALUE>CLARiiON+CKM00083900053</VALUE>

</PROPERTY>

<PROPERTY NAME="SerialNumber"  TYPE="string">

<VALUE>CKM00083900053</VALUE>

</PROPERTY>

</INSTANCE>

 

 

Number of instance qualifiers: 0

Number of instance properties: 3

Property: CreationClassName Number of qualifiers: 0

Property: Tag Number of qualifiers: 0

Property: SerialNumber Number of qualifiers: 0

 

ExceQuery 1 instances; repeat count 1;return data in 0.000000 seconds

 

Retrieve and Display data - 1 Iteration(s) In 0.062400 Seconds

 

A failing provider will return the following:

++++ Testing ExecQuery:  ++++

Error: Connection closed by CIM Server.

 

Retrieve and Display data - 1 Iteration(s) In 0.053000 Seconds

 

Please

press enter key to continue...

Filter Blog

By date:
By tag: