• The Datadog plugins allows to integrate Redpeaks with Datadog via its cloud API
• Devices, events and metrics discovered by Redpeaks will become visible in Datadog
• Predefined dashboards can be downloaded from Datadog market place on Redpeaks's page.

• The Datadog plugin will directly connect to your cloud instance by using several API endpoints.
• To configure the plugin, you need to register the parameters below.
• Note: API & Application keys must be generated first on your cloud instance for allowing connection.

If you want to stop the data flow between Redpeaks and Datadog, you can deactivate the plugin.

• To create those keys, connect to your datadog instance and open the Organization settings
• Navigate to API keys and Application keys sub menus and create your new keys

• To use a proxy for outgoing HTTP and HTTPS connections, edit bin/setenv.sh file from promonitor server
• Add to the JAVA_OPTS variable the following parameters:
  • -Dhttps.proxyPort=<HTTPS proxy port> and -Dhttps.proxyHost=<HTTPS proxy host>
  • -Dhttp.proxyPort=<HTTP proxy port> and -Dhttp.proxyHost=<HTTP proxy host>

• All alarms produced by Redpeaks will be sent to datadog

• All metrics produced by Redpeaks will be sent to datadog

Redpeaks is using logs interface to send collected data, by example:

SAP jobs

• tags:
  • job_name
  • client
  • status
  • start_date
  • end_date
• Example:
  • Mar 16 09:22:48.000 10.222.2.2 SAP_JOBS name:SAP_COLLECTOR_PERFMON_RSHOSTDB client:000 user: status:FINISHED Start:09:22:48 End:09:22:48

Shortdumps:

• tags:
  • date
  • client
  • user
  • error
  • instance
  • message
• Example:
  • Mar 16 08:00:27.000 10.222.2.2 SAP_SHORTDUMPS instance:saa69_PSM_00 client:001 errorid:DYNPRO_SEND_IN_BACKGROUND report:RLCR_XI_STAYING_ALIVE

System logs

• tags:
  • instance
  • date
  • area
  • program
  • subid
  • user
• Example:
  • aglges4has.agentil.local SAP_SYSLOGS instance:aglges4has_S4H_00 user:BASISJOBS program:RSSNAPDL area:AB subId:D text:Short dump deleted with default tool RSSNAPDL

• If the tracking is active, the distinct times series sent to Datadog will be recorded
• This gives the possiblility to know how many metrics have been created in datadog
• This also allows to analyze the cardinality of the metrics and fine tune the configuration
• The list of distinct time series can be collected by this HTTP API call:

GET /plugins/statistics/distinct_ts?type=DATADOG

• You can force a set of tags to be always associated to each metric, log and event.
• This can be configured via two ways:

From the plugin menu:

From the properties file:

the file conf/monitoring.properties

• Set the property: plugins.datadog.custom_tags
• Example:
  • plugins.datadog.custom_tags=tag1:val1,tag2:val2

Once set, you must restart Redpeaks

• The custom prefix will be used in metrics naming and references to events and logs.
• Dashboards automatically generated when subscribing to the integration in the Datadog Marketplace are designed to work with a prefix set to redpeaks. Changing this prefix may disrupt queries that rely on it.
• The prefix will help maintaining backward compatibility with existing dashboards still using the previous agentil_software prefix

Helps to easily integrate any syslog drain with Datadog.
This is specially adapted to logs produced by Cloud Foundry applications

• Edit the plugin configuration screen to set below parameters:

• HTTP:
  • Received logs will be buffered and sent to the datadog http-intake interface.
• AGENT:
  • Logs will be output in logs/syslog_drain.log file.
  • A Datadog agent can be configured to collect logs
  • The syslog files will be automatically rotated, keeping maximum 10 files.

• Activate listening of syslog in your Datadog plugin
• Open you CF CLI and run the following commands

cf cups java-syslog-drain -l syslog://[REDPEAKS_HOST]:9999
cf bind-service [YOUR APPLICATION NAME] java-syslog-drain
cf restage [YOUR APPLICATION NAME]

• From now on, received logs will be sent to your Datadog instance.