seedata.io DOCS
  • Welcome
  • Getting Started
    • What is seedata.io?
    • Core Concepts
    • Quick Start
    • Get Help
    • Subscriptions
  • Features
    • Dashboard
    • Alerts
    • Integrations
      • AWS
      • Webhook
    • Deployments
    • Seeds
      • Email
      • URL
      • Person
      • Microsoft Document (XLSX, DOCX)
      • PDF Document
      • HTML Page
      • SVG Image
      • AWS Credential
      • Virtual Machine Honeypot
      • EC2 Honeypot
    • Events
    • Intel
    • Settings
      • Whitelists
      • Users & Tokens
      • Profiles
  • Tutorials
    • Managing your alerts
      • Webhook
      • Webforms
      • Teams
      • Syslog
      • Slack
      • ServiceNow
      • Jira
      • Email
      • Elasticsearch
      • Datadog
    • Registering for a new account
    • Planting a VM honeypot seed
    • Preparing a VM Honeypot host
    • Planting an EC2 honeypot seed
    • Planting AWS Serverless Seeds
  • API reference
    • Activities
    • Api tokens
    • Copilot
      • Assessment
    • Data widgets
    • Deployments
    • Events
      • Next
      • Previous
      • Alert
      • Journal
    • Integrations
    • Intel
    • Notification recipients
      • Test
    • Seeds
      • Bulk
      • Retire
      • Test
      • Next
      • Previous
    • Stats
    • Whitelisted sources
Powered by GitBook
On this page
  • Step 1 - Get your Datadog site
  • Step 2 - Get a Datadog API token
  • Step 3 - Configure the alert

Was this helpful?

  1. Tutorials
  2. Managing your alerts

Datadog

Receive event alerts within your Datadog tenant

PreviousElasticsearchNextRegistering for a new account

Last updated 1 year ago

Was this helpful?

Our Datadog alert integration can be added to your account and configured to send the message of your choice to appear in the Datadog Event Management dashboard (as part of service management) whenever a new interaction or observation is detected against your seeds

Step 1 - Get your Datadog site

Datadog uses different domains for its API depending the site you have your tenant in.

You'll know this from the drop down used during Datadog authentication, or by looking at the URL used when accessing Datadog. The table below correlates your site with the DATADOG API DOMAIN you need to provide in step 3, later

SITE
SITE URL
LOCATION
API DOMAIN

US1

https://app.datadoghq.com

US

api.datadoghq.com

US3

https://us3.datadoghq.com

US

api.us3.datadoghq.com

US5

https://us5.datadoghq.com

US

api.us5.datadoghq.com

EU1

https://app.datadoghq.eu

EU

api.datadoghq.eu

US1-FED

https://app.ddog-gov.com

US

api.ddog-gov.com

AP1

https://ap1.datadoghq.com

Japan

api.ap1.datadoghq.com

Step 2 - Get a Datadog API token

To ensure messages from seedata are "trusted", you will need to pass an API token (generated by Datadog) with each message sent by seedata.io. To do this, please;

  • Navigate to Datadog / Organization settings, then click the API keys tab.

  • Click the New Key button.

  • Enter a name for your key.

  • Click Create API key.

Step 3 - Configure the alert

  • Log in to seedata and go to Alerts and find the tile for Datadog

  • Click Install

  • Give this installation a name and description so you know why you have created it.

  • Select the priorities of events you want to be sent by opting in (or not) for baseline events

  • Add the Datadog API Domain that you previously identified.

  • Add the API key that you previously generated on the datadog platform.

  • We provide a default template for the message that will be sent. You're free to change this, by adding any free text you wish along with any seedata.io variables. There's even a handy "Reset Template" button if you want to restore our default template at any time.

  • Hit Submit.

Make a temporary note of the new secret key value (for clarity, this is the value with the little key icon next to it. It's not the key ID). You will use this in step 3.