Page Comparison

...

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 topologyAPI v2: Read entities

   2. API v2: Write entities

   3. API v2: Ingest metrics

   4. API v2: Ingest events

...

• Nagios API URL - Nagios Core URL (mandatory to fill)

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

• Nagios Password- Password to connect to Nagios 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 in integration. Only member hosts are included other hosts are ignored (mandatory to fill)

• Nagios Service names to include - Service names specified as regular expressions delimited by a semicolon (other services are ignored), e.g. Mem.*sage;HTTP;Swa.*

• 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 (mandatory to fill)

• 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 (mandatory to fill)

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

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

  • API v2: Read entities

  • API v2: Write entities

  • API v2: Ingest metrics

  • API v2: Ingest events

• Verify Dynatrace SSL 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)

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

• Performance metrics - If there is no definition then no performance data are transferred. Define regular expressions/substrings delimited by a semicolon specifying service list (e.g. Mem;HTTP;Swa.*) Performance data for matching services list will be transferred into Dynatrace.

• Candidate to Custom device - Create a Custom device for Monitoring candidate, if not enabled events are sent to the monitoring candidate host

• 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 (mandatory to fill)

...