Sources & Sinks
Integrations
Datadog

Datadog

Datadog integrations are supported in both the UI and the API.

To create a Datadog integration, you'll need at least an API key. An App key is optional, but would allow Grepr to use the integration as a Cloud source and for automatic exception parsing. You'll use the same API key in your agent as the one you configure in Grepr. See details about API and App Keys in Datadog at https://docs.datadoghq.com/account_management/api-app-keys/ (opens in a new tab).

Grepr SaaS has a Private Link connection to Datadog in AWS us-east1 (Datadog's main site). However, Grepr also supports all other Datadog sites as well.

Server logs

To send data to Grepr from Datadog agents, you configure the agents to send logs to Grepr via the Datadog agent's logs_dd_url configuration key. Changing this configuration key depends on how you deploy your Datadog agents. See below for some of the more common deployment models or visit https://docs.datadoghq.com/agent/logs (opens in a new tab) for more information. You'll also need to enable the agent to send using HTTP, which corresponds to the force_use_http setting.

The endpoint that you need to configure for the logs_dd_url setting has the following format: https://<integration-id>-<org-id>.ingest.grepr.ai. The Grepr UI will format this endpoint and make it available for you to copy, if you're using the UI. Otherwise, the integration-id is the ID of the Datadog integration that you'd like to use, available via the API.

Basic standalone agent

If you have access to the Datadog agent datadog.yaml file:

  1. set logs_config.logs_dd_url to the Grepr endpoint.
  2. set logs_config.force_use_http to true (note this still uses HTTPS).

Cluster or Docker agent

These agents are usually configured via environment variables.

  1. set DD_LOGS_CONFIG_LOGS_DD_URL to the Grepr endpoint.
  2. set DD_LOGS_CONFIG_USE_HTTP to true (note this still uses HTTPS).

Browser logs

Grepr supports collecting browser logs (https://docs.datadoghq.com/logs/log_collection/javascript/ (opens in a new tab)). To send browser logs to Grepr, you configure your browser SDK with Grepr as a Proxy.

To send browser logs to Grepr:

  1. Create client token in datadog. Refer to Datadog documentation (opens in a new tab) for instructions on how to create a client token.
  2. Create a datadog integration in Grepr and add client token. Adding client token to Datadog integration
  3. Create a pipeline with the source with the above integration and copy the browser-intake ingest URL. Copying browser-intake ingest URL
  4. Configure your Datadog Browser SDK initialization with the Grepr endpoint from the previous step by setting the proxy using the following format:
// Initialize the Datadog Browser SDK with Grepr as a proxy
datadogLogs.init({
  clientToken: '<CLIENT_TOKEN>',
  site: '<DATADOG_SITE>',
  proxy: (options) =>
    `https://<browser-intake-ingest-url>/api/v2/logs?${options.parameters}`
  // other configuration options...
});

Consult the Datadog Browser SDK documentation for complete implementation details.

Exception Parsing

When your Datadog integration is configured with an App key, Grepr automatically monitors all log monitors configured in your Datadog account. It parses the log queries used in these monitors and makes them available as exceptions to the Log Reducer.

This powerful capability lets you deploy Grepr without modifying your existing monitors, ensuring your critical alerts continue to function while still achieving significant log volume reduction.

Sources & SinksNew Relic