You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-16Lines changed: 22 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
# OpsMgr GenericServiceMonitoring ManagementPack
2
2
3
3
## Introduction:
4
-
It is often necessary to monitor windows services across your entire SCOM environment. This MP gives you the ability to easily and quickly discover and monitor hundreds of services. The wildcard(*) notation allows great flexibility in discovering the services you are looking for.
4
+
It is often necessary to monitor windows services across your entire SCOM environment. This Management Pack gives you the ability to easily and quickly discover and monitor hundreds of services. The wildcard(*) notation allows great flexibility in discovering the services you are looking for.
5
5
6
-
This ManagementPack is currently under development and may contain errors. Please always test it in DEV environment befor importing the MP to production.
6
+
This Management Pack is currently under development and may contain errors. Please always test it in DEV environment befor importing the Management Pack to production.
7
7
8
8
## Key Features
9
9
@@ -13,41 +13,41 @@ This ManagementPack is currently under development and may contain errors. Pleas
13
13
## Supported Environments
14
14
15
15
- System Center Operations Manager 2012 R2
16
-
- System Center Operations Manager 2016 (LTSC)
17
-
- System Center Operations Manager 1807 (SAC)
16
+
- System Center Operations Manager Long Term Servicing Channel (2016)
17
+
- System Center Operations Manager Semi-Annual Channel (1807)
18
18
19
19
## How-To:
20
20
### 1. Import the Management Pack into SCOM.
21
21
### 2. Create the CSV file on one of your management server.
22
22
23
-
#### CSV File Schema:
23
+
#### CSV file schema:
24
24
25
25
__ServiceName;Include;Exclude__
26
26
27
-
Include: Comma separated List of Servername(ShortName)
27
+
Include: comma-separated list of servernames (ShortName; not FQDN)
28
28
29
-
Exclude: Comma separated List of Servername(ShortName)
29
+
Exclude: comma-separated list of servernames (ShortName; not FQDN)
30
30
31
-
*: Every Host in the "Microsoft.SystemCenter.ManagedComputerServer" ClasS
31
+
*: Every host in the "Microsoft.SystemCenter.ManagedComputerServer" class
32
32
33
-
#### CSV File Examples:
33
+
#### CSV file examples:
34
34
35
35
__ServiceA;HostA,HostB;none__
36
36
37
-
ServiceA is monitored for HostA and HostB. There is no (none) exclusion.
37
+
serviceA is monitored for hostA and hostB. There is no (none) exclusion.
38
38
39
39
__ServiceB;*;none__
40
40
41
-
ServiceB is monitored on every Host. There is no (none) exclusion.
41
+
serviceB is monitored on every host. There is no (none) exclusion.
42
42
43
43
__Service*;*;HostB__
44
44
45
-
Service*(wildcard) is monitored on every Host and excluded for HostB.
45
+
service*(wildcard) is monitored on every host and excluded for hostB.
46
46
47
47
48
-
### 3. Start Sevice Ingest Task
48
+
### 3. Start service ingestion task
49
49
50
-
1. The Task which starts the CSV ingestion process is found at the "Management Server View". Select the management server on which the CSV is located and execute the Task. (Example at Views -> State View Management Server)
50
+
1. The task which starts the CSV ingestion process is found at the "Management Server View". Select the management server on which the CSV is located and execute the task. (example at Views -> State View Management Server)
The discovery is configured to run every 24h and detect newly processed servers. This setting can be changed at the xml code to meet your requirements. So it can take up to 24 hours until the service can be discovered.
60
+
### 4. Check discoverd services
61
+
The discovery is configured to run every 24h and detect newly processed services. This setting can be changed at the xml code to meet your requirements. So it can take up to 24 hours until the service can be discovered.
0 commit comments