OS services monitoring
OneAgent version 1.239+
Dynatrace version 1.240+
Dynatrace provides out-of-the-box availability monitoring of OS services.
Requirements
To monitor Linux services, systemd version 230+ is required on the monitored host.
Monitor a service
To monitor an OS service, perform the following steps.
Access OS services monitoring
Add service monitoring policy
Select services you want to monitor
Add custom properties
Access OS services monitoring
In Dynatrace, go to OS services monitoring for the level you are configuring.
Add service monitoring policy
Based on the service state and the rules, the service monitoring policy defines the way Dynatrace is monitoring your service. By default, Dynatrace comes with Auto-start Windows OS Services
and Auto-start Linux OS Services
policies for auto-started Windows and Linux services with failed status.
The order of service monitoring policies is important. Policies that are higher on the list will proceed before those on lower positions until they are fulfilled. This allows for the creation of selective alerts or monitoring with minimal policies. If you want to monitor all auto-started services and not just those created by Microsoft, you need to add a policy with disabled alerting and/or monitoring that will verify if the manufacturer is Microsoft.
-
On OS services monitoring for the level you are configuring based on your OS, select Add policy and define the policy, which is a collection of rules.
-
System: select your operating system.
-
Rule name: enter the name that will be displayed in the Summary field.
-
Monitor: decide whether you want to monitor service availability using the OS service availability (
builtin:osservice.availability
) metric. If available, the metric sends the service status every 10 seconds. The status is carried by the Service status (dt.osservice.status
) dimension.
Note that the metric consumes DDUs. For more information, see DDU consumption. -
Alert: decide whether you want alerting for your policy.
-
OneAgent version 1.257+ Alert if service is not installed: whether you want to receive alerts about OS services that are not installed on the host.
-
Service status: set the service status for which an alert should be triggered.
You can use logic operations to monitor the service status. For example,
$eq(running)
monitors the running service state.Available logic operations:
$not($eq(paused))
– Matches services that are in state different from paused.$or($eq(paused),$eq(running))
– Matches services that are either in paused or running state.
These are the service statuses you can monitor. Use one of the following values as a parameter for this condition:
running
stopped
start_pending
stop_pending
continue_pending
pause_pending
paused
You can use logic operations to monitor the service status. For example,
$eq(active)
monitors the active service state.Available logic operations:
$not($eq(active))
– Matches services with state different from active.$or($eq(inactive),$eq(failed))
– Matches services that are either in inactive or failed state.
These are the service statuses you can monitor. Use one of the following values as a parameter for this condition:
reloading
activating
deactivating
failed
inactive
active
-
optional OneAgent version 1.257+ Alerting delay: the number of 10-second measurement cycles for a service to be in configured state before an event is generated.
Next, you need to select which services you want to monitor based on service properties.
Select services you want to monitor
Select Add rule and then select the service you want to monitor.
Service property used for matching:
- Display name visible for system user.
- Path to the binary used by OS service.
- Manufacturer from the binary file of the service.
- Service Name
- Startup Type
A monitoring rule may consist of multiple detection rules. All detection rules must be satisfied for the OS Service to match, as a logical AND
operation is applied across all specified conditions.
Service property used for matching:
- Service Name
- Startup Type
Add custom properties optional
OneAgent version 1.247+
Dynatrace version 1.247+
-
Select Add property to specify a custom key-value property for the policy.
-
Select Save changes.
Configure automatically applied tags and management zones
Dynatrace version 1.257+
You need to manually configure automatically applied tags and management zones for OS service entities, as Dynatrace no longer automatically associates OS services with their respective hosts.
To set up automatic tagging for OS services
-
In the Dynatrace menu, go to Settings.
-
Go to Tags > Automatically applied tags and select Create tag.
-
Enter a Tag name and an optional Description for your tag.
-
Select Add a new rule to define the conditions for the tag.
-
Rule type: select Entity selector.
-
Entity selector: define the conditions under which the tag should be applied to OS services.
-
To assign a tag based on the host where the OS service is running, use the following format:
type(os:service),fromRelationship.runsOn(type(HOST),entityName.startsWith("<host name>"))
The tag will be applied to any OS service that runs on a host with a name that starts with
<host name>
. -
To assign a tag based on the process group instance where the OS service is running, use the following format:
type(os:service),toRelationship.runsOn(type(PROCESS_GROUP_INSTANCE),entityName.startsWith("<PGI name>"))
The tag will be applied to any OS service that runs on a PGI with a name that starts with
<PGI name>
.
-
-
Select Save changes.
To set up management zones for OS services
-
In the Dynatrace menu, go to Settings.
-
Go to Preferences > Management zones and select Add new management zone.
-
Enter a Management zone name and an optional Description for your management zone.
-
Select Add a new rule to define the conditions for the management zone.
-
Rule type: select Entity selector.
-
Entity selector: define the conditions under which the management zone should be applied to OS services.
-
To assign a management zone based on the host where the OS service is running, use the following format:
type(os:service),fromRelationship.runsOn(type(HOST),entityName.startsWith("<host name>"))
The management zone will be applied to any OS service that runs on a host with a name that starts with
<host name>
. -
To assign a management zone based on the process group instance where the OS service is running, use the following format:
type(os:service),toRelationship.runsOn(type(PROCESS_GROUP_INSTANCE),entityName.startsWith("<PGI name>"))
The management zone will be applied to any OS service that runs on a PGI with a name that starts with
<PGI name>
.
-
Manage monitored OS services
To manage the OS services
-
In Dynatrace, go to OS services monitoring for the level you are configuring.
-
The OS services you monitor are displayed in a table under the Add policy button.
- To stop monitoring a listed service, turn the Enabled setting off.
- To delete a service from the table, select the delete button in the Delete column
- To view and edit details, select the expand control in the Details column.
Monitor service availability
Dynatrace version 1.243+
OneAgent version 1.243+
The Host overview page contains the OS services analysis section listing the OS services for which any policy (with active alerting or monitoring) is fulfilled.
- In the Dynatrace menu, go to Hosts.
- In the OS services analysis section, select the service name to open the Service overview page.
For more information, see Host monitoring with Dynatrace
Configure at scale using Settings API
You can use the Settings API to configure your service availability monitoring at scale.
- To learn the schema, use GET a schema with
builtin:os-services-monitoring
as the schemaId. - Based on the
builtin:os-services-monitoring
schema, create your configuration object. - To create your configuration, use POST an object.