SCOM Insight – Configuration
Objects on the dashboard
SCOM Insight uses groups in SCOM to determine which objects to present. These groups may be configured as you wish, to either statically or dynamically include whatever objects you would like to present.
In SCOM Insight, the structure is:
This corresponds, in SCOM, to the this group structure:
For example, the default page's group is
SCOM Insight: Default, and it contains sub-groups that define the sections on the page and the tiles that they contain. By default, this looks like:
The three groups are:
1 Distributed Applications, which is dynamically populated with the distributed applications in your management group; and the prefix
1indicates to SCOM Insight that this is the first section on the page;
2 Websites, which is dynamically populated with the websites; with the prefix
2, as it's the second section on the page; and
3 Computers, which contains the computers and is displayed as the third section.
This default set-up looks something like:
These sub-groups can be fully customised. For example:
- they can contain any objects you would like to be displayed – simply change their group membership;
- they can be renamed;
- their positions can be altered, by changing the numerical prefix (e.g. renaming
- they can be deleted; and
- groups can be added, which would add sections to the page.
To make any changes, amend the groups in the SCOM console.
|✓||All groups must be saved in the
After configuring the homepage dashboard, you may want to create new pages to display additional objects. For example, you could display websites, grouped by environment, on a second page. To do this, create a new group structure, e.g.:
Populate the four groups,
Dev, which will become the new sections on the page, with the objects that you wish to be displayed.
The new page will be accessible at
/?group=Environments. For example, if your site is configured as
https://scominsight.org.demo/, the new page will be
You may create as many pages as you require.
A custom logo can be added to the dashboard; for example:
To add a logo:
- Save the logo, in either JPEG or PNG format, to
- In the
Web.configfile (located in
C:\Program Files\Pendlenet\SCOM Insight\):
CustomLogoFileto the name of your logo file, e.g.
<add key="CustomLogoFile" value="Logo.png" />
- If required, change
CustomLogoHorizontalPositionto set the position of the logo. The valid settings are:
- By default, the logo is shown only on the tile view. If you would like it to be displayed on the alerts view as well, set
The Web.config file contains the following configurable settings:
||The SCOM management server from which information should be retrieved.|
||The interval between polls of SCOM. You may reduce this value to provide more frequent updates in SCOM Insight, but it will increase the load on your management server.|
||The interval between rotations of the carousel view (|
||A regular expression to determine the top-level SCOM groups that provide the group configuration (see group configuration).|
||A regular expression to determine the names of objects that are included in the SCOM groups but which are to be excluded from the dashboard, e.g. any object containing the word Deprecated: |
||The name of the top-level SCOM group that is used to define the homepage configuration (see group configuration).|
||Indicates whether the names presented by SCOM Insight for the objects contained in the SCOM groups are to exclude the name of the containing group, if the entity name contains the group name.|
For example, if the group is called Production and the contained entities are called Site A Production and Site B Production, and this key is set to
||A regular expression to specify any portion of an alert name that is not to be shown. For example, to exclude Test from an alert with the name Monitor A Test, this key should have the value |
||Specifies the thresholds for the highlighting of state change alerts on the dashboard. The first threshold is used for the flashing border highlight, and the second for the solid border highlight.|
For example, if both thresholds are 600 seconds, a new alert state will cause the tile border to flash for 10 minutes, then be solid for 10 minutes, before returning to normal.
||Controls the standard number of tiles that can be present in a row. If tiles are added, and this value is exceeded for a row, the tiles will wrap on to the next row.|
||Enabled by default, this setting causes computer names to be capitalised across the application, for consistency.|
||A comma-separated list of domain names that are not to be shown on the tiles that represent computers/servers. When populated with a list of your internal domains, this property will reduce FQDNs to individual computer names, so that they more easily fit onto tiles.|
||Enabled by default, this setting causes clicked-on tiles to load a view of the alerts particular to that tile. The full alerts view can still be accessed via |
||This is the filename of a custom logo to be shown at the top of the dashboard. The supported file formats are JPEG and PNG. Save the file in |
||Used when |
||Used when |
||Used when |
In addition, the
<connectionStrings> section contains the database connection string, which you will need to change if the SCOM Insight database is moved. This key takes the form of standard SQL Server connections strings.
The following are advanced settings that you probably won't have cause to change:
||Specifies the system name of the management pack that contains the SCOM groups used in the configuration of the SCOM Insight (see New pages).|
||Specifies the age the information in SCOM Insight's database can reach before being considered stale, after which point, a warning message is displayed on each page. This threshold may be reached if, for example, SCOM is unavailable.|
||Specifies how long must pass before an object's health state is considered valid when it is in the state No Data. This health state occurs when there is no information for the state, e.g. when a distributed application contains no valid objects, or when a distributed application exits maintenance mode. If a distributed application has a state of No Data within this threshold, the previous health state is considered to be the current one. This helps to prevent No Data states being presented to on the dashboard unnecessarily, e.g. when exiting maintenance mode, before the health roll-up calculation has completed, which can take a few minutes.|
||Specifies the age at which the SCOM data cache, which is maintained between import cycles, will be cleared and refreshed. The cache is used to temporarily store certain objects and relationships that rarely change, in order to improve the performance of the import process. It isn't usually necessary to alter this value, as the data import process examines the last-changed time of each object and dynamically flushes the cache where appropriate.|
||A minor setting, specifying the length of time that data is retained in the |
||Indicates that previous versions of SCOM Insight may be allowed to import data from SCOM. By default, only the current version of the application can import data. This is to ensure that, in a web farm, when an upgrade of the application takes place, an old version can't process an import or write to the database. If, however, a version downgrade takes place, it may become necessary to adjust this parameter.|
||Defines, relative to |
||Defines the path to the file used when audio notifications are enabled.|
||A regular expression to determine the title strings, such as alert titles, that shouldn't automatically be corrected to title case. This includes, for example, short words such as on and in.|
||Specifies the number of tiles that will be presented before switching to static mode. In static mode, the tiles have a fixed position and can't be moved. This parameter defaults to 100 and is helpful in increasing performance of the view, where a large number of tiles are presented.|
||Specifies whether snow is shown in December.|
This may be overridden in the browser by the
||Specifies whether snow is shown in December when in kiosk mode.|
This may be overridden in the browser by the
||Used when |
SCOM Insight can be deployed to a web farm, i.e. to multiple web servers. This approach may be used to provide fault tolerance and/or additional capacity. You may install SCOM Insight to as many web servers as required. The application's nodes will negotiate so that only one connects to the SCOM management server to import data, thereby maintaining the load on your SCOM infrastructure at a constant level.
A single back-end database must be used, although this may be on a SQL Server cluster or in an Always On availability group.
|⚠||The web garden feature of IIS, where an application pool creates more than one process, is not currently supported.|