Howto: Adding a link that opens the target Health Explorer Web Console.

Howto: Adding a link that opens the target Health Explorer Web Console.

In this HowTo I explain how we can open a SCOM Health Explorer by clicking on a ProView dashboard shape

What we need:

  1. The web console URL.
  2. The target ID that we want to show the Health Explorer on.
  3. Construct the URL.
  4. Add the URL as visio shape link.

1 The Web Console URL

Open the web console and copy the URL name, see the yellow part

http://scom2012r2/operationsmanager/#/overview(name=Microsoft.SystemCenter.Monitoring.ViewFolder.Root)

2 The Target ID

To get the Target ID (1) select the correct health state shape you added already to the dashboard. Now open the Shape Data (2)

Now copy the MonitoringObjectID guide

3 Construct the URL

Now we construct the URL that we are going to call when we press on the shape.

We can open, for example, the views below. Replace the ObjectID with the MonitoringObjectID got from the step 2 above and also replace the <web console url> with the correct URL got from step 1.

StateView single object http://<web console url>/MonitoringView/default.aspx?DisplayMode=Pivot&ViewType=StateView&PmoId=objectId

AlertView single object http://<web console url>/MonitoringView/default.aspx?DisplayMode=Pivot&ViewType=AlertView&PmoId=objectId

HeathExplorer single object
http://<web console url>/MonitoringView/ResultViews/ViewTypeHealthExplorer.aspx?targetId=objectId

Diagram view http://<web console url>/MonitoringView/default.aspx?DisplayMode=Pivot&ViewType=DiagramView&PmoID=PmoId

An example for a Health Explorer would be: http://scom2012r2/MonitoringView/ResultViews/ViewTypeHealthExplorer.aspx?targetId=68b6018a-ebec-d945-7f8e-7df8c08ea3fa

And for an Alert view: http://scom2012r2/MonitoringView/default.aspx?DisplayMode=Pivot&ViewType=AlertView&PmoId=68b6018a-ebec-d945-7f8e-7df8c08ea3fa

We will take the Health Explorer view.

4 Add the URL as visio shape link

Now you select (1) the shape you want to put the Health Explorer on and (2) open the hyperlink option.

Copy and paste (1) the constructed URL from part 3 and press OK (2)


To test you now press the dashboard preview and hover over the shape that you applied with the hyperlink. Click on it when the cursor changes to a hand (1).

Using the Thresholds in the Forecast Performance Percentage Value Reports

Using the Thresholds in the Forecast Performance Percentage Value Reports

The Capacity Reports Management Pack contains a set of reports that give you a powerful forecasting tool for your Operations Manager environment. This blog focuses on the “Forecast Performance Percentage Value Report” reports.

Besides providing forecasted capacity values, the Forecast Performance Percentage Value Reports allow you to identify thresholds in time to proactively respond to the forecasted capacity issue and resolve it before it causes downtime or becomes an issue.

Consider the graph above. The graph shows a steady decline in free disk space (of a particular storage device) over time. The X- Axis shows the date and the Y-Axis shows the percent of free disk space expressed in a percentage. The blue line represents the actual data in the SCOM data warehouse on the free disk space (of a particular storage device). The red-dotted line represents the forecast line (or trend line) for the free disk space data points. When looking at the forecast line, we can see that the trend for free disk space is downwards towards 0%. This would mean that (at point T3 in the graph) the disk would be completely out of free space. Now, as we know, being out of free disk space only means bad things and potentially angry customers or users. Ideally we would like to know well in advance that we are going to run out of free disk space so that we can proactively take action such as cleaning up the disk, or extending the disk.

The “Forecast Performance Percentage Value Report” reports are specifically designed to help you avoid a situation where you would unexpectedly end up at point T3 in the graph, where you have 0% free disk space left. By letting you set thresholds, the report allows you to receive warnings on approaching capacity issues.

When we examine the configurable parameters in the “Forecast Performance Percentage Value Report – displays all capacity objects” report, there are two parameters that can be set in order to receive a warning before the disk is at capacity (T3). The two parameters that can be set are:

  • Number of days for Warning Level
  • Number of days for Critical Level

The “Number of days for Warning Level” corresponds with point T1 in the Free Disk Space graph. When we set the “Number of days for Warning Level” threshold, it will cause the report to show a warning when this threshold is breached as shown in the image below. In this example, the threshold is set to 150 days. This is the distance in days between T1 and T3 on the graph.

The “Number of days for Critical Level” corresponds with point T2 in the Free Disk Space graph. When we set the “Number of days for Critical Level” threshold, it will cause the report to show a critical state when this threshold is breached, as shown in the image below. In this example the threshold is set to 100 days. This is the distance in days between T2 and T3 in the graph.

You might also notice that the “Today” point is still to the left of T1 and outside of the area between T1 and T3. If today is 1-Jan-2016 and T3 is 10-June-2016, the number of days between Today and T3 is 165. Thus, the number of days until capacity (T3) is reached is 165. This means that in this case, “Today” is outside of both the warning (T1) and critical (T2) thresholds set, and therefore displaying a healthy state in the report as shown below.

KB 150983 – Capacity Reporting Management Pack rsErrorExecutingCommand error

KB 150983 – Capacity Reporting Management Pack rsErrorExecutingCommand error

 

Issue:

In some cases after importing the Capacity Reporting Management Pack, you might receive the error message “An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset ‘DataSet_LinearRegression’. (rsErrorExecutingCommand) For more information about this error navigate to the report server on the local server machine, or enable remote errors” when trying to run one of the reports.

Cause:

This error is usually caused by a setting on the SQL server which hosts the SCOM data warehouse database. The setting on the SQL server prohibits the reports from executing the assembly needed for forecasting portion of the reports. For additional information please see the following Microsoft knowledge base article: https://msdn.microsoft.com/en-us/library/ms254506(v=vs.80).aspx

 

Solution:

To allow the reports to make use of (and execute) the assembly, the query below should be run on the SQL server which hosts the SCOM data warehouse database. This query can only be run by an account with sysadmin privileges.

 

sp_configure ‘clr enabled’, 1

GO

RECONFIGURE

GO

BlackBerry Management Pack Custom connection string to BES database

BlackBerry Management Pack Custom connection string to BES database

 

In most cases the BlackBerry Management Pack is able to construct the connection string in order to connect to the BlackBerry Enterprise server database. In special cases where SQL standby servers are used or other forms of SQL redundancy, the connection string might not reflect the correct configuration. An example is that the BlackBerry management pack cannot construct a connection string that reflects a standby server. In order to allow the BlackBerry Management Pack to connect to SQL back-ends with varying configurations, the option is given to create a custom connection string by overriding the default configuration. In order to override the default connection string follow the steps below.

 

  1. The default connection string outomatically generated by the BlackBerry Management Pack has the following form: Provider=SQLOLEDB;Database=BESMgmt;Server=olxsql01;Trusted_Connection=Yes;IntegratedSecurity=SSPI
  2. The management pack cannot automatically build connection strings for failover or standby databases, so you will need to override the default connection string to the following format (You will need to determine the exact format of the connection string for your environment):Provider=SQLOLEDB;Database=BESMgmt;Server=olxsql01;Failover Partner=olxsql02;Initial Catalog=myDataBase;Trusted_Connection=Yes;IntegratedSecurity=SSPI.
  3. Once you have determined the correct connection string, in the SCOM console browse to the authoring section and set the scope as shown in the screenshot:
  4. Then select: Authoring -> Management Pack Objects -> Object Discoveries and double click BlackBerry 5.0.x Enterprise Server Discovery
  5. Select the Overrides tab and select For all objects of class: BlackBerry 5.0.x servers.
  6. In the Overrides Properties window check the checkbox next to ConnectionString and enter the new connection string into the Override Value field. Save the override in an appropriate management pack and save the changes.

Sizing SCOM for the Oracle Management Pack

Sizing SCOM for the Oracle Management Pack

When implementing a new Management Pack in System Center Operations Manager (SCOM) sizing is extremely important if you want to keep your SCOM environment healthy and responsive. For implementing the OpsLogix Oracle Management Pack there are a few sizing scenarios you might want to consider before importing the Management Pack.

There are also 5 main factors that determine the number of instances you can monitor from one monitoring node:

  • Number of tablespace in an Oracle instance
  • Type of SCOM server used
  • Other workflow that are run on the SCOM agent
  • Number of enabled/disabled/custom rules and monitors in the management pack
  • Hardware sizing

This post is based on V1.3.12.130 of the OpsLogix Management Pack for Oracle.

 

Scenario’s for running the Oracle Management Pack on a Monitoring node:

  1. Running the management pack from a SCOM Management server
  2. Running the management pack from a SCOM Gateway Server
  3. Running the management pack from a SCOM Agent machine

 

 

Running the management pack from a SCOM Management server

When running the management pack from a dedicated SCOM Management server you should be able to monitor 20 instances when the following criteria are met:

  • The Management Server does not run any other major workloads
  • The average number of tablespaces per instance should not exceed 20
  • The server has at least 8 GB RAM and 2 CPU’s
  • Only the default monitors and rules in the management pack are enabled

 

 

Running the management pack from a SCOM Gateway Server

When running the management pack from a dedicated SCOM Gateway server you should be able to monitor 20 instances when the following criteria are met:

  • The Gateway Server does not run any other major workloads
  • The average number of tablespaces per instance should not exceed 20
  • The server has at least 4 GB RAM and 2 CPU’s
  • Only the default monitors and rules in the management pack are enabled
  • For the increased workload you will need to configure registry settings and overrides on the Gateway Server as shown in the appendix.

 

Running the management pack from a SCOM Agent machine

When running the management pack from a dedicated SCOM Agent server you should be able to monitor 20 instances when the following criteria are met:

  • The SCOM Agent Server does not run any other major workloads
  • The average number of tablespaces per instance should not exceed 20
  • The server has at least 4 GB RAM and 2 CPU’s
  • Only the default monitors and rules in the management pack are enabled
  • For the increased workload you will need to configure registry settings and overrides on the SCOM Agent Server as shown in the appendix.

Appendix: Adding registry settings and overrides to scom agents:

In order for the SCOM Agent or Gateway to be able to handle the larger workload the following registry settings need to be set on the server:

  • reg add “HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters” /v “State Queue Items” /t REG_DWORD /d 20480 /f
  • reg add “HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters” /v “Persistence Checkpoint Depth Maximum” /t REG_DWORD /d 104857600 /f

 

 

For the increased workload you will need to set the following overrides on the SCOM Agent or Gateway Server:

Navigate to:

System Center 2012 Operations Manager – Operations Console > Authoring > Management Pack Objects > Monitors

Locate Health Service > Entity Health > Performance> System Center Management Health Service Performance > System Center Management Health Service Memory Utilization > Health Service Private Bytes Threshold

Right-click and select Properties > then from the ‘Health Service Private Bytes Threshold Properties’ select the Overrides tab> click the Override… button and choose ‘For a specific object of class: Health Service

Find the server you are using as a monitoring node, select it and click OK

Check the Override box by ‘Agent Performance Monitor Type – Threshold’ and change the ‘Override Value’ (scroll to the right) to 31457280000

Save the override.

Navigate to:

System Center 2012 Operations Manager – Operations Console > Authoring > Management Pack Objects > Monitors

Locate Health Service > Entity Health > Performance> System Center Management Health Service Performance > System Center Management Health Service Memory Utilization > Health Service Handle Count Threshold

Right-click and select Properties > then from the ‘Health Service Handle Count Threshold Properties’ select the Overrides tab> click the Override… button and choose ‘For a specific object of class: Health Service

Find the server you are using as a monitoring node, select it and click OK

Check the Override box by ‘Health Service Handle Count Threshold – Threshold’ and change the ‘Override Value’ (scroll to the right) to 31457280000

Save the override.

Sizing SCOM for the Oracle Management Pack

You receive an “Oracle Instance Connection Monitor” Alert after configuring an instance in the “Oracle IMP Configuration Dashboard”

When configuring the Oracle Management Pack, the management pack sometimes throws “Oracle Instance Connection Monitor” Alerts because it cannot connect to the Oracle database/instance.

 

When this happens, check if the Host Name and Instance Name you configured in the “Oracle IMP Configuration Dashboard” correspond with the names in the TNSNames.ora file.

 

The TNSNames.ora file is usually found in the following directory on Linux servers installed with Oracle 11g: /u01/app/oracle/product/11.2.0.db_1/network/admin.

The Host Name in the “Oracle IMP Configuration Dashboard” should correspond with the HOST field highlighted in the TNSNames.ora.

The Instance Name in the “Oracle IMP Configuration Dashboard” should correspond with the SERVICE_NAME field highlighted in the TNSNames.ora.