Page Comparison

Endpoint Prior to configuring the extension in the Dynatrace UI, please

1. Create Nagios user that will be used by the extension

2. Create a Dynatrace API token with the following permissions:

   1. API v1: Access problem and event feed, metrics, and topology

   2. API v2: Read entities

   3. API v2: Write entities

Extension endpoint configuration provides these options:

• Nagios API URL - URL of Nagios server server (mandatory to fill)

• Nagios Username - User name to connect to Nagios API API (mandatory to fill)

• Nagios Password- Password to connect to Nagios API API (mandatory to fill)

• Verify Nagios SSL certificate - Verify Nagios SSL certificate

• Nagios CA certificates - Path to CA bundle with CA certificates to be used for verification (if using custom CA) in PEM format. Used only if verification is turned on. If not specified, built-in CA certificates are used.

• Nagios HostGroups to include - Semicolon delimited list of Nagios host groups to include (other hosts are ignored)

• Nagios Service names to include - Service names regular expressions delimited by a semicolon (other services are ignored)

• Nagios metadata keys - Semicolon separated names of Nagios host attribute keys to be used in Custom device metadata

• Nagios alert keys - Semicolon separated names of Nagios alert state attribute keys to be used in Custom event metadata

• Nagios refresh hosts - Interval (in minutes) for querying Nagios API for hosts and inventory data. Hosts and inventory is queried on extension startup and periodically afterward afterward (mandatory to fill)

• Dynatrace refresh host entities - Interval (in minutes) for querying Dynatrace API for hosts and their IP addresses. Hosts are queried on extension startup and periodically afterward (mandatory to fill)

• Nagios metadata keys - Semicolon separated names of Nagios host attribute keys to be used in Custom device metadata. All possible keys are listed in chapter Negios metadata keys

• Nagios alert keys - Semicolon separated names of Nagios alert state attribute keys to be used in Custom event metadata. All possible keys are listed in chapter Nagios alert keys Notification enabled - Catch states with enabled notification only

• Nagios host DOWN - Nagios severity to Dynatrace severity mapping

• Nagios host UNREACHABLE - Nagios severity to Dynatrace severity mapping

• Nagios service CRITICAL - Nagios severity to Dynatrace severity mapping

• Nagios service WARNING - Nagios severity to Dynatrace severity mapping

• Nagios service UNKNOWN - Nagios severity to Dynatrace severity mapping

• Dynatrace Environment URL - URL for Dynatrace environment used for Entity v2 API calls calls (mandatory to fill)

• Dynatrace API Token - Dynatrace API token with the following scope access access (mandatory to fill)

  • API v1: Access problem and event feed, metrics, and topology

  • API v2: Read entities

  • API v2: Write entities

• Verify Dynatrace SSL certificate certificate - Verify Dynatrace SSL certificate

• Dynatrace CA certificate - Path to CA bundle with CA certificates to be used for verification (if using custom CA) in PEM format. Used only if verification is turned on. If not specified, built-in CA certificates are used.

• Dynatrace refresh host entities - Interval (in minutes) for querying Dynatrace API for hosts and their IP addresses. Hosts are queried on extension startup and periodically afterward (mandatory to fill)

• Dynatrace problem resend time - Interval in minutes for resending events to Dynatrace to keep the problem opened in Dynatrace (otherwise expires after 15 minutes) (mandatory to fill)

• Service Warning - Catch service in Warning state

• Nagios host DOWN - Nagios severity to Dynatrace severity mapping

• Nagios host UNREACHABLE - Nagios severity to Dynatrace severity mapping

• Nagios service CRITICAL - Nagios severity to Dynatrace severity mapping

• Nagios service WARNING - Nagios severity to Dynatrace severity mapping

• Nagios service UNKNOWN - Nagios severity to Dynatrace severity mapping

• Notification enabled - Catch states with enabled notification only

• Problem metric - Send problem metric (count of problems for each created custom device)

• Candidate to Custom device - Create Custom device for Monitoring candidate, if not enabled events are sent at to monitoring candidate host(mandatory to fill

• Use Events API - If enabled, Nagios problems are sent using Events API instead of the ActiveGate extension.

• Allow Davis merge - Allow Davis AI to merge events into existing problems (true) or force creating a new problem (false)

• Debug - Set to on to enable DEBUG logging on each extension query run

• License –  - Valid license required required (mandatory to fill)

Nagios alert keys

...