Datadog Integration (Coming Soon)

Overview

The Botbit Datadog integration automatically forwards robot telemetry data to your Datadog account, enabling:

• Unified Monitoring: View robot fleet metrics alongside your infrastructure
• Custom Dashboards: Build Datadog dashboards with robot operational data
• Advanced Alerting: Set up Datadog monitors for fleet-wide conditions
• Anomaly Detection: Leverage Datadog’s ML-powered anomaly detection on robot metrics
• Long-Term Analytics: Query historical robot data using Datadog’s analytics

How It Works

Data Flow

1. Botbit Collects Telemetry

   • Primary controllers report operational metrics to Botbit (via API integration)
   • Botbit stores telemetry: hours on, miles driven, battery cycles, component health

2. Botbit Forwards to Datadog

   • Telemetry automatically syncs to Datadog as metrics
   • Each robot becomes a unique source with tags for filtering
   • Updates send on same schedule as telemetry collection (hourly/daily)

3. Monitor in Datadog

   • Create dashboards showing fleet-wide trends
   • Set up monitors and alerts on robot conditions
   • Correlate robot telemetry with infrastructure metrics

Metric Format

Botbit sends metrics to Datadog with this structure:

botbit.robot.hours_on
botbit.robot.miles_driven
botbit.robot.battery_cycles
botbit.robot.component.health_score

Each metric includes tags for filtering and grouping:

serial_number:ROB-2025-00001
site:warehouse_east
build_config:delivery_bot_v2
robot_version:2.1
component:lidar_front

Sample Datadog Dashboard

Once configured, you can create dashboards like this:

Fleet Utilization Overview

Total Fleet Operating Hours (Last 30 Days)

• Timeseries graph: sum:botbit.robot.hours_on{*} by {site}
• Shows operational intensity per site

Battery Health Distribution

• Distribution graph: avg:botbit.robot.battery_cycles{*} by {serial_number}
• Identifies robots approaching cycle limits

Miles Driven by Build Config

• Top list: sum:botbit.robot.miles_driven{*} by {build_config}
• Compare performance across different robot models

Component Health Monitoring

Component Health Scores

• Heatmap: avg:botbit.robot.component.health_score{*} by {component, serial_number}
• Visual fleet-wide component health

Low Health Alert

• Monitor triggers when: avg(last_1h):avg:botbit.robot.component.health_score{*} < 70
• Proactive maintenance before failures

Alert Examples

High Battery Cycle Count

avg(last_4h):max:botbit.robot.battery_cycles{*} by {serial_number} > 500

Alert when any robot exceeds 500 battery cycles (approaching replacement threshold).

Fleet Utilization Drop

avg(last_1d):sum:botbit.robot.hours_on{site:warehouse_east} < 100

Alert when warehouse_east site utilization drops below expected levels.

Component Health Degradation

avg(last_1h):avg:botbit.robot.component.health_score{component:lidar_front} < 75

Alert when front LiDAR sensors show declining health across fleet.

Configuration

Setup Steps

1. Generate Datadog API Key

   • Log into your Datadog account
   • Navigate to Organization Settings → API Keys
   • Create new API key with name “Botbit Integration”

2. Configure in Botbit

   • Navigate to Settings → Integrations
   • Click “Add Integration” → Select “Datadog”
   • Enter your Datadog API key and site region
   • Choose metric prefix (default: botbit.robot)

3. Select Sync Frequency

   • Real-time: Forward telemetry immediately when received
   • Hourly: Batch updates every hour (recommended)
   • Daily: Once per day summary metrics

4. Choose Metrics

   • Select which telemetry to forward:
     • ✓ Operating hours
     • ✓ Miles driven
     • ✓ Battery cycles
     • ✓ Component health scores
     • ✓ Software versions (as tags)

Tag Customization

Add custom tags to all metrics for better organization:

• environment:production - Distinguish prod/staging fleets
• customer:acme_corp - Track multi-tenant deployments
• region:us_west - Geographic segmentation

Pricing Considerations

Datadog Metric Costs

Each robot generates these metrics:

• 3 base metrics (hours, miles, cycles)
• N component health metrics (where N = number of self-reporting components)

Example Fleet Costs:

• 100 robots with 5 components each = 800 custom metrics
• At Datadog’s pricing: ~$240/month (varies by plan)

Cost Optimization Tips

1. Limit Component Metrics: Only forward health scores for critical components
2. Reduce Frequency: Daily updates instead of hourly reduce metric volume
3. Use Datadog Metrics without Limits: If available on your plan
4. Aggregate at Site Level: Send site-level rollups instead of per-robot metrics

Monitoring Best Practices

Start with Key Metrics

Don’t forward everything - start with actionable metrics:

1. Battery Cycles: Predict replacement needs
2. Operating Hours: Track utilization and warranty
3. Component Health: Proactive maintenance triggers

Create Baseline Dashboards

Build these core dashboards first:

1. Fleet Health Overview: High-level status across all robots
2. Site Comparison: Compare operational metrics by location
3. Robot Detail: Drill-down view for individual robot troubleshooting

Set Smart Alerts

Avoid alert fatigue:

• Use anomaly detection instead of static thresholds
• Set recovery notifications so you know when issues resolve
• Configure alert groups to batch similar issues

Data Retention

Telemetry forwarded to Datadog follows your Datadog retention policy:

• Standard plan: 15 months
• Enterprise plans: Custom retention up to 3+ years
• Botbit retains full history regardless of Datadog integration

Security & Privacy

Data Transmission

• All data sent via HTTPS with TLS 1.2+
• Datadog API keys stored encrypted in Botbit
• No sensitive component details (only serial numbers and metrics)

Access Control

• Datadog integration requires Botbit Admin role
• API key rotation supported without downtime
• Disable integration anytime to stop data flow

Troubleshooting

Metrics Not Appearing

1. Verify Datadog API key is valid
2. Check Datadog site region matches configuration (US1, EU, etc.)
3. Confirm robots have recent telemetry in Botbit
4. Check Datadog Metrics Explorer for botbit.* namespace

Missing Tags

Ensure robots have required fields populated:

• Serial number
• Site assignment
• Build config association

High Metric Volume

If metrics exceed expectations:

• Review component health forwarding settings
• Check for duplicate robot serial numbers
• Verify sync frequency isn’t set too aggressive

Getting Started

1. Contact Support: Datadog integration is currently in development
2. Prepare Datadog Account: Ensure you have API access and metric capacity
3. Pilot Program: Join early access to test integration with your fleet

---

Coming Soon: The Datadog integration is under active development. Contact support@getbotbit.com to join the pilot program.