Versions Compared

Old Version 19

changes.mady.by.user Bohdan Špes

Saved on

compared with

New Version Current

changes.mady.by.user Bohdan Špes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Before configuring the extension in the Dynatrace UI, please

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

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

    1. API v2: Read entities

    2. API v2: Write entities

    3. API v2: Ingest metrics

    4. API v2: Ingest events

  3. will use if you don’t want to use nagiosadmin user

Extension endpoint configuration provides these options:

  • License - Valid license required (mandatory to fill)

  • HTTP Proxy - Only necessary if ActiveGate cannot connect to the Nagios server URL directly. Proxy to use for the connection from ActiveGate to the Nagios server. Nagios API

    • Proxy user name - User name to connect to the proxy server.

    • Proxy password - Password to connect to the proxy server.

  • Nagios URL - Nagios Core Server web 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 certificateNagios host groups to include - 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 list - At least one Nagios HostGroup should be defined for synchronization (mandatory to fill)

Advanced configuration

  • Nagios timeout - Timeout in seconds for Nagios API response

  • Problems title prefix - The Nagios problem title will have a defined prefix if we want to distinguish problems from Nagios from problems generated from Dynatrace. We recommend the prefix [Nagios] with one space at the end.

  • Problems not older than - Synchronize problems not older than specified days. 0 means no limit for problem age.

  • Refresh Hosts list from Nagios - Interval (in minutes) for querying Nagios API for hosts and inventory data and building internal cache. Default value 20 minutes (mandatory to fill)Nagios refresh state of hosts and services - Interval (in minutes) for querying Nagios API for monitoring status of hosts services. Default value 1 minute (mandatory to fill)minutes.

  • Refresh Nagios Host entities in Dynatrace - Interval in minutes between refresh of Nagios Host entities in Dynatrace. If the interval is greater than 5 minutes, you will only see Nagios hosts with problems and other Nagios hosts will be displayed as "Inactive" or not displayed at all. Each Nagios host refreshed in Dynatrace consumes 0.001 DDU. Formula (0.001 DDU x number of Nagios hosts in Dynatrace x number of links to Nagios host groups per host) / Refresh Nagios Host entities in Dynatrace

  • Dynatrace problem resend time - Interval in minutes for resending events to Dynatrace to keep the problem opened in Dynatrace (otherwise, it expires after 15 minutes). Each problem event sent consumes 0.001 DDU

  • Notification enabled - Catch only Nagios problems with enabled notification. If enabled and the Nagios host has disabled notifications then all Nagios services from that host are ignored for problem synchronization.

  • 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 only Nagios problems with enabled notification

  • Dynatrace Environment URL - URL for Dynatrace environment used for Entity v2 API calls. If you want to communicate through the gateway and not directly to the server, use the address in the format: https://localhost:9999/e/EnvironmentID  In this case, the server certificate cannot be verified. (mandatory to fill)

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

    • 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 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, it expires after 15 minutes). Each problem event sent consumes 0.001 DDU. (mandatory to fill)Allow Davis merge - Allow Davis AI to merge events into existing problems (true) or force creating a new problem (false)

  • Nagios service names filter - List of Nagios service names specified as regular expressions or name substrings. Services that meet the filter will be monitored. If the list is empty, all services are monitored.

  • Performance metrics - If there is no definition then no Nagios service performance data are transferred. Define the list of Nagios service names specified as regular expressions or name substrings. Performance data for the matching services list will be transferred into Dynatrace.

  • Problem metric - Send problem metric (count of problems for each created custom devicemonitored Nagios host). If a problem doesn’t exist on the host, metric data are not sent. Consumes 0.001DDU/minute per entity with problems.

  • 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.

  • Metrics to hosts - Send Nagios metrics to the Dynatrace host. Infrastructure metrics are monitored by the Dynatrace agent, therefore Nagios metrics are not sent by default. Turn on if you want Nagios metrics to be sent to hosts monitored by the Dynatrace agent.

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

  • SSL Trust store - SSL CA certificate in PEM format for Nagios web server

  • Nagios host metadata configuration - List of Nagios host attribute keys to be synchronized from Nagios host to Dynatrace entity

  • Nagios problem metadata configuration - List of Nagios problem attribute keys to be synchronized from Nagios problem to Dynatrace event/problem

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

  • License - Valid license required (mandatory to fill)

Nagios alert keys

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

Code Block
"name": "Name"
"plugin_output": "Status information"
"long_plugin_output": "Status information long"
"perf_data": "Performance data"
"status": "Current status"
 # hardcoded"last_update": "Last update"
"has_been_checked": "Has been checked"
"should_be_scheduled": "Should be checked"
"current_attempt": "Attempts current"
"max_attempts": "Attempts max"
"last_check": "Last check"
"next_check": "Next check"
"check_options": "Check options"
"check_type": "Check type"
"last_state_change": "Last state changed"
 # hardcoded"last_hard_state_change": "Last hard state changed"
"last_hard_state": "Last hard state"
"last_time_up": "Last time up"
"last_time_down": "Last time down"
"last_time_unreachable": "Last time unreachable"
"state_type": "State type"
 # hardcoded"last_notification": "Last notification"
"next_notification": "Next notification"
"no_more_notifications": "No more notifications"
"notifications_enabled": "Notifications enabled"
"problem_has_been_acknowledged": "Problem has been aknowledged"
 # hardcoded"acknowledgement_type": "Acknowledge type"
"current_notification_number": "Current notification number"
"accept_passive_checks": "Accept passive checks"
"event_handler_enabled": "Event handler enabled"
"checks_enabled": "Checks enabled"
"flap_detection_enabled": "Flap detection enabled"
"is_flapping": "Is flapping"
"percent_state_change": "Percent state change"
"latency": "Latency"
"execution_time": "Execution time"
"scheduled_downtime_depth": "Scheduled downtime depth"
"process_performance_data": "Process performance data"
"obsess": "Obsession"
"url": "Nagios URL info"

...

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

...