Balkar Singh Kang

Dashboard for Probe of Things - A Custom Probe That Does Things

Blog Post created by Balkar Singh Kang Employee on Sep 29, 2017

Purpose

This purpose of this document is to record the step by step configuration details for the “ "Probe of Things - A Custom Probe That Does Things probe deployment and dashboards” required at the customer location. These dashboards are designed based on field developed probe named probe_of_things. Refer to the attachment for the screenshots and dashboards.

Probe Information

The function of this probe will be to provide a UIM administrator with small callback utilities to make the management of the UIM infrastructure a little easier. In CUSTOMER environment, the Probe_of_things probe is deployed in development environment. CUSTOMER has requirement of providing a flexible tool to their customers to view and compare probe configurations on their servers.

 

https://communities.ca.com/community/ca-infrastructure-management/unified-infrastructure-management/blog/2016/07/22/probe-of-things-a-custom-probe-that-does-things

 

Probe Deployment & Configuration

Download the latest version of the probe from communities.ca.com portal.

Deploy the probe of the destination server. (Note: This server is in the same network/datacenter of UMP server)

This probe is confirmation from raw configuration. In CUSTOMER environment, profiles are created for the following probes.

                    Cdm

                    Ntservices

                    Ntevl

                    Sqlserver

                    Processes

 

Each profile has the following three (3) keys

Probe

                    Name of the probe

Sections

                    Comma separated list of sections from the probe cfg file.

Keys

                    Comma separated list of thresholds from various sections of the probe cfg file

 

 

Figure 1: Probe Configuration

Database Index Creation

Probe_of_things probe uses h2 database as back and is hosted locally. The following indexes are created in CUSTOMER environment to enhance the query performance.

 

CREATE INDEX IDX_THR_CUR_01 ON THRESHOLD_CURRENT(ROBOT);

CREATE INDEX IDX_THR_CUR_02 ON THRESHOLD_CURRENT(ROBOT,PROBE);

CREATE INDEX IDX_THR_CUR_03 ON THRESHOLD_CURRENT(ROBOT,PROBE,SECTION);

CREATE INDEX IDX_THR_CUR_04 ON THRESHOLD_CURRENT(PROBE,SECTION,KEY);

 

Please refer to Appendix A for the instructions to access the database console

UMP Configuration

  UMP Dashboard will require a new database connection. Use the following steps configure HTML5 Dashboard connectivity.

                Open UMP Dashboard designer

                                    Click on “Data Sources” -> Enable Advanced Data Sources -> SQL

                                                      Click + to add new data source from h2 database

Figure 2: UMP – Adding Data Source Steps

Figure 3: UMP Connection Add Screen

CUSTOMER development environment is already configured with required h2 database connection as H2DatabaseConnection

Note: The above configuration requires wasp to restart.

Dashboards

   Dashboard 1: “Probe Config by Server”

   Requirements

                          Users should be able to see probe configuration thresholds for selected probe on a selected server.

   Screenshot

Figure 4: Dashboard Screen Shot

   Queries

List Servers

                                                                        select distinct robot from threshold_current

                                                      List Probes

                                                                        select distinct probe from threshold_current where robot = '${robot}'                                                             List Probe Sections

select distinct case when charindex('/',section,2) = 0 then substring(section,2,length(section)) else substring(section, 2,charindex('/',section,2)-2) end as Section from threshold_current where robot= '${robot}' and probe = '${probe}'

                                                      Server Configuration

select * from threshold_current where robot= '${robot}' and probe = '${probe}' and section like '%${probe_section}%'

 

   Dashboard 2: “Probe Config Compare for 2 Servers”

    Requirements

Users should be able to compare the configuration of selected probe on two selected servers.   

 

Screenshot      

Figure 5: Dashboard Screen Shot

Queries

                                                      List Servers

                                                                        select distinct robot from threshold_current

                                                      List Probes

                                                                        select distinct probe from threshold_current where robot = '${robot}'

                                                      List Probe Sections

                                                                        select distinct

case when charindex('/',section,2) = 0 then substring(section,2,length(section)) else substring(section, 2,charindex('/',section,2)-2) end as Section

from threshold_current where robot= '${robot}' and probe = '${probe}'

List Compare to Servers

select distinct robot from threshold_current where probe = '${probe}' and section like '%${probe_section}%'

 

                                                      Server Configuration Comparison

select one.hub as Hub1, one.robot as Server1, two.hub as Hub2, two.robot as Server2, one.section, one.key, one.value as Server1_Values , two.value as Server2_Values, case when one.value=two.value then 'No' else 'Yes' end as Diff

from threshold_current one

join threshold_current two 

on two.probe = one.probe and two.section=one.section and two.key=one.key where one.robot = '${robot}' and two.robot = '${comparerobot}' and one.probe = '${probe}' and one.section like '%${probe_section}%'

 

Dashboard Access

   Site POTS

                                    A site “POTS” is created for end user access.

 

Figure 6: Site POTS

Appendix

                 

Database Client Setup

                                    While installation enable H2 support

Figure 7: SQL Installation

 

                                    And copy the driver in the lib directory.

                 

  • Run the .bat program from the installation directory

 

  • Add Alias to Configure the connection string per the screenshot below.

                                                      Database: <name of the server where probe of things” installed>

                                                      Username:uim

                                                      Password:uim

Figure 8: h2 db connection settings

Outcomes