Skip to content

Datadog Integration

Forward detection events to Datadog for centralized security monitoring, alerting, and dashboards.

  • Datadog account
  • API key
  • Application key
  1. Log into Datadog
  2. Go to Organization Settings → API Keys
  3. Click New Key
  4. Name it “WebDecoy Integration”
  5. Copy the key
  1. Go to Organization Settings → Application Keys
  2. Click New Key
  3. Name it “WebDecoy Integration”
  4. Copy the key
  1. Go to Integrations → Datadog

  2. Click Add Datadog Integration

  3. Enter:

    FieldDescription
    API KeyDatadog API key
    Application KeyDatadog application key
    SiteYour Datadog site region
  4. Configure event forwarding:

    SettingDescription
    Forward all detectionsEvery detection as an event
    Forward high riskOnly critical detections
    Include metricsSend as custom metrics
  5. Click Connect

SiteRegionURL
US1US (Virginia)datadoghq.com
US3US (Virginia)us3.datadoghq.com
US5US (Oregon)us5.datadoghq.com
EU1EU (Frankfurt)datadoghq.eu
AP1Asia (Tokyo)ap1.datadoghq.com

Detections are sent as Datadog events:

{
"title": "WebDecoy: High-Risk Detection",
"text": "Decoy link triggered by 192.168.1.100\n\nPath: /admin/backup.zip\nScore: 85 (CRITICAL)\nMITRE: Reconnaissance (TA0043)",
"priority": "normal",
"tags": [
"source:webdecoy",
"detection_type:decoy_link",
"threat_level:critical",
"mitre_tactic:reconnaissance",
"country:US"
],
"alert_type": "warning",
"source_type_name": "webdecoy"
}
TagDescriptionExample
source:webdecoyAlways present-
detection_typeType of detectiondecoy_link, bot_scanner, endpoint
threat_levelRisk levelminimal, low, medium, high, critical
mitre_tacticMITRE ATT&CK tacticreconnaissance, initial_access
countrySource countryUS, CN, RU
propertyProperty nameproduction_site
is_botBot detectiontrue, false
is_vpnVPN detectedtrue, false

When “Include metrics” is enabled, WebDecoy sends custom metrics:

MetricTypeDescription
webdecoy.detections.countCountNumber of detections
webdecoy.detections.scoreGaugeAverage threat score
webdecoy.blocked_ips.countCountIPs blocked
webdecoy.bot_score.averageGaugeAverage bot score

All metrics include:

  • property - Property name
  • detection_type - Detection source type
  • threat_level - Risk level
  • country - Source country

Detection Overview:

  • Timeseries of webdecoy.detections.count
  • Group by threat_level

Geographic Distribution:

  • Geomap using country tag
  • Colored by detection count

Threat Level Breakdown:

  • Pie chart of detections by threat_level

Top Attacking IPs:

  • Top list from events
  • Filter by high threat scores
{
"title": "WebDecoy Security Dashboard",
"widgets": [
{
"definition": {
"title": "Detections Over Time",
"type": "timeseries",
"requests": [
{
"q": "sum:webdecoy.detections.count{*} by {threat_level}",
"display_type": "bars"
}
]
}
},
{
"definition": {
"title": "Threat Levels",
"type": "sunburst",
"requests": [
{
"q": "sum:webdecoy.detections.count{*} by {threat_level}"
}
]
}
}
]
}

Create Datadog monitors for WebDecoy events:

Monitor Type: Event Alert
Query: events("source:webdecoy threat_level:critical").rollup("count").by("source").last("5m") > 0
Alert: Notify security team
Monitor Type: Metric Alert
Query: sum:webdecoy.detections.count{*}.as_count() > 100
Window: 5 minutes
Alert: Anomaly detection triggered
Monitor Type: Event Alert
Query: events("source:webdecoy is_bot:true").rollup("count").last("1h") > 50
Alert: Potential bot attack in progress

WebDecoy can also send logs to Datadog:

{
"timestamp": "2025-01-15T10:30:00Z",
"level": "warn",
"message": "Detection created",
"service": "webdecoy",
"detection_id": "det_abc123",
"ip_address": "192.168.1.100",
"threat_score": 85,
"threat_level": "critical",
"detection_type": "decoy_link",
"property_id": "prop_def456"
}

Create a pipeline to parse WebDecoy logs:

  1. Go to Logs → Configuration → Pipelines
  2. Create new pipeline for service:webdecoy
  3. Add processors:
    • Grok parser for message
    • Status remapper for threat_level
    • GeoIP processor for ip_address
  • ✅ Use tags for filtering and grouping
  • ✅ Create dashboards for visibility
  • ✅ Set up alerts for critical detections
  • ✅ Use metrics for trend analysis
  • ✅ Correlate with other security data
  • ❌ Forward all events without filtering
  • ❌ Ignore high-volume periods (adjust alerts)
  • ❌ Skip dashboard setup
  • ❌ Use API key with excessive permissions
  1. Verify API and Application keys
  2. Check site region is correct
  3. Ensure integration is enabled
  4. Check Datadog event explorer with filter source:webdecoy
  1. Verify “Include metrics” is enabled
  2. Check Datadog Metrics Explorer
  3. Metrics may take a few minutes to appear
  4. Verify custom metrics quota
  1. Regenerate API key
  2. Verify Application key is correct
  3. Check keys haven’t been revoked
  4. Ensure correct Datadog site