Showing metric value in BSM Service Health KPI's and SHA

4,991 views
4,860 views

Published on

Published in: Technology, Business

Showing metric value in BSM Service Health KPI's and SHA

  1. 1. custom metric values in BSM Service Health KPI and SHA
  2. 2. Part I- Custom Metrics in BSM Introduction There are cases where we want to show status and value on the KPI level, for example KPI that is affected by metrics like temperature, humidity, number of connections, and so on. Most of the out-of-the-box KPIs show status only and the value is on the health indicator level. In this use-case scenario we are going to create and show the metric value directly on the KPI and the dashboard. We will create 2 custom His and KPIs – Temperature and Humidity. The metrics will be taken from a weather website with SiteScope URL content monitor.
  3. 3. BSM Configuration Create new Health Indicators – Temperature and Humidity Navigate to AdminService HealthRepositoriesIndicators • Name – Temperature • States – add the possible state for the indicator. You can customize the Display name, for example Normal status can be Cold, Minor can be Warm, and so on. • Default Rule – Generic Sample Rule; Selection – returnNumOfDigitAfterPoint • If the Hi will be part of SLA, you can choose HI availability as the default SLM rule ** Repeat the same steps for the second health indicator – Humidity
  4. 4. BSM Configuration Create new Health Indicators – Temperature and Humidity
  5. 5. BSM Configuration Create new KPIs – Temperature and Humidity Navigate to AdminService HealthRepositoriesKPIs • Name – Temperature; Domain – System • Selected Rules – Worst, Best, and Percentage Rules. These are the most common business rules. You can add additional business rules according to your needs. • Advanced Settings:
  6. 6. BSM Configuration Create new KPIs – Temperature and Humidity • Presentation Settings: Value: NODE.DIM.RESULT.Value Status: NODE.DIM.RESULT.Status Formatting Method: Selection (leave empty) Value Postfix: °C. This is an optional field that will show the measurement unit. For Humidity KPI use %
  7. 7. BSM Configuration Create new KPIs – Temperature and Humidity • Presentation type: Values or Status
  8. 8. BSM Configuration Assign the KPI to the CIT Node Navigate to AdminService HealthAssignmentsKPI Assignments • Create new assignment under CIT Node and give it a name • Condition – Monitored by SiteScope • KPI Configuration – add the Temperature and Humidity KPI with their His respectively No need to create HI assignment, since the KPI Enrichment Service (KES) rule for SiteScope will automatically create the Temperature and Humidity His when a new sample value will be received
  9. 9. BSM Configuration Assign the KPI to the CIT Node
  10. 10. BSM Configuration Mapping a SiteScope Metric to the custom HIs Like we mentioned before, the metric will be fed from SIS URL Content monitor, and thus we will update this monitor type. • Navigate to AdminSystem Availability ManagementMetrics and Indicators • Select URL Content from the monitor list • Navigate to Node CIT, and select Temperature health indicator. In the Metric Pattern enter /Temperature/
  11. 11. BSM Configuration Mapping a SiteScope Metric to the custom His
  12. 12. BSM Configuration Mapping a SiteScope Metric to the custom His • Add another Metric pattern called /Humidity/ and map it to Humidity HI • Publish the changes
  13. 13. SiteScope configuration URL Content monitor settings In this example, we will monitor the temperature and humidity from 3 different locations – Tel-Aviv, Tokyo, and Toronto. The information is taken from http://www.timeanddate.com/weather website. I’ve created 3 dummy Cis named Tel-Aviv, Tokyo, and Toronto in order to map the metrics to them. URL Content monitor settings: • URL - http://www.timeanddate.com/weather/israel/tel-aviv Match content for Temperature - /Temperature:</td><td>(-?d+)&nbsp;°C/ For Humidity - /<td>Humidity:</td><td>(-?d+)%</td>/ ** The regex should catch any number – negative and positive from the relevant html code <td>Temperature:</td><td>28&nbsp;°C</td> • Match content labels – Temperature/Humidity respectively
  14. 14. SiteScope configuration URL Content monitor settings HP Integration Settings – in this section we “tell” the system to which CI and HI to map the metrics • CI Type – Windows (in this example); Server: tel-aviv • Indicator Settings – Metric Pattern=/Temperature/, Indicator=Temperature • Configure thresholds accordingly. Use ‘Temperature’ and ‘Humidity’ condition Repeat these steps for Humidity metric as well
  15. 15. SiteScope configuration URL Content monitor settings • BSM Service Health affected by: Metrics
  16. 16. BSM Service Health • We can see our customized metrics showed as value and status according to the thresholds:
  17. 17. BSM Service Health • We can also see a metric-based graph for Temperature or Humidity in these locations:
  18. 18. Part II - SHA Add Custom metrics for SHA Baselining • Navigate to DPS: <HPBSM>:confanalyticsmetadatadefault • Edit the relevant XML file, in this case SiS.xml • Add new Group and the relevant metrics in the following format: <match value="metric_name"/>
  19. 19. Part II - SHA Add Custom metrics for SHA Baselining • After the changes, restart analytics_loader process on the gateway • Add the Cis to the SHA monitored Cis from BSM UI
  20. 20. Part II - SHA Validate SHA collects metrics for Temperature and Humidity metrics • http://<DPS>:29925/mbean?objectname=Topaz%3Aservice%3DSHA+Engine • Invoke fetchMetricsByDimension. Use uCMDB ID as the value • Look for the Temperature and Humidity metrics, it should look something like that:
  21. 21. Part II - SHA Build a custom graph for the metric with SHA baseline • http://<DPS>:29924/mbean?objectname=Topaz%3Aservice%3DBaseline+Services • Look for extractDataAndBaselineSleeve and fill the information from previous step. The CSV file path refers to the DPS.
  22. 22. Part II - SHA Build a custom graph for the metric with SHA baseline • Open the baseline viewer on the DPS – BSMToolsBaselineViewer BaselineViewer.bat and upload the CSV file you created in the previous step.
  23. 23. Part II - SHA Build a custom graph for the metric with SHA baseline If you don’t have baseline data yet, you won’t be able to export the metric data to a CSV file. If you don’t want to wait a week until the baseline calculation takes place, you can manually initiate it by performing the following steps: • Find SiteScope task ID (100 in this example) and invoke Show Tasks http://<DPS>:29924/mbean?objectname=Topaz%3Aservice%3DBaseline+Services
  24. 24. Part II - SHA Build a custom graph for the metric with SHA baseline • On the same page, invoke calculateNow (the second one) with Value=false • Restart analytics_loader process on the gateway server in order for the changes to take effect immediately.
  25. 25. Part II - SHA Anomalies and Investigation In order for SHA to recognize anomaly it may take some time until the baseline and sleeves are built correctly and an anomaly is being detected. After SHA detects anomaly, you can start investigating it by going to ApplicationsService Health Analyzer. You can also see all open anomalies in the following link: http://<GW>/topaz/pi/AnomaliesList.do? If you see anomalies there, but not in BSM UI, you need to add ‘Breached’ column
  26. 26. Part II - SHA Anomalies and Investigation • Select the Anomaly you want to focus on and click on Investigate. We can see the relevant topology, events and other information in the Topology View tab, or move to the Metrics View: • We can select both metrics and see their behavior and events over time, correlation between them, and the baseline sleeves (green metric is Humidity and purple is Temperature)
  27. 27. Part II - SHA Correlation • Click on the upper-right tab ‘Correlation’ and drag the comparison metric there, and the correlating metric(s) to the bottom pane. You will see the correlation score between the metrics: • In our example, we can see that the correlation between Temperature and Humidity in Tokyo is not significant – only 59%

×