Migration Guide

Switching to Nodewarden from your existing monitoring solution is straightforward. This guide covers migration paths from popular monitoring tools.

Why Migrate to Nodewarden?

• Simplicity: No complex configuration files or steep learning curves
• Cost-effective: Transparent pricing without hidden fees
• Easy setup: Get monitoring in minutes, not days
• Unified platform: Metrics, alerts, and dashboards in one place

Migration from Datadog

Step 1: Export Your Dashboards

Before migrating, document your critical dashboards and alerts:

bashCopy
# Export dashboard definitions (if using Datadog API)
curl -X GET "https://api.datadoghq.com/api/v1/dashboard" \
  -H "DD-API-KEY: ${DD_API_KEY}" \
  -H "DD-APPLICATION-KEY: ${DD_APP_KEY}" > datadog-dashboards.json

Step 2: Install Nodewarden Agent

Replace the Datadog agent with Nodewarden's lightweight agent:

bashCopy
# Uninstall Datadog agent
sudo systemctl stop datadog-agent
sudo apt-get remove datadog-agent

# Install Nodewarden agent
curl -sSL https://app.nodewarden.com/install | bash

Step 3: Configure Metrics Collection

Nodewarden automatically collects system metrics. For custom metrics:

yamlCopy
# nodewarden.conf
api_key: "your-api-key"
host_id: "your-host-id"
api_url: "https://api.nodewarden.com"

# Custom process monitoring (replaces Datadog process checks)
processes:
  - name: "nginx"
    enabled: true
  - name: "mysql"
    enabled: true

Step 4: Recreate Dashboards

Use Nodewarden's dashboard builder to recreate your visualizations:

1. Navigate to Dashboards → Create New
2. Add widgets for CPU, memory, disk, and network metrics
3. Configure alerts with similar thresholds

Step 5: Set Up Alerts

Migrate your alert rules:

• Datadog: avg(last_5m):avg:system.cpu.user{*} > 80
• Nodewarden: Create alert with "CPU Usage > 80%" condition

Migration from Prometheus

Step 1: Identify Key Metrics

List your essential Prometheus queries:

promqlCopy
# Common Prometheus queries
rate(node_cpu_seconds_total[5m])
node_memory_MemAvailable_bytes / node_memory_MemTotal_bytes
rate(node_disk_io_time_seconds_total[5m])

Step 2: Install Nodewarden Agent

Nodewarden can run alongside Prometheus during migration:

bashCopy
# Install Nodewarden agent
curl -sSL https://app.nodewarden.com/install | bash

# Agent will auto-discover and monitor your services

Step 3: Configure Prometheus Integration

If you want to keep Prometheus for specific use cases:

yamlCopy
# nodewarden.conf
integrations:
  prometheus:
    enabled: true
    endpoint: "http://localhost:9090"
    scrape_interval: 30s

Step 4: Migrate Alerting Rules

Convert Prometheus alerts to Nodewarden:

Prometheus Alert:

yamlCopy
- alert: HighCPUUsage
  expr: rate(node_cpu_seconds_total[5m]) > 0.8
  for: 5m

Nodewarden Alert:

• Create alert: "CPU Usage"
• Condition: "> 80%"
• Duration: "5 minutes"

Migration from New Relic

Step 1: Document APM Requirements

Identify which New Relic features you actively use:

• Infrastructure monitoring ✓ (Nodewarden covers this)
• APM traces (Consider keeping for deep debugging)
• Synthetic monitoring ✓ (Nodewarden HTTP checks)

Step 2: Parallel Run

Run both agents temporarily:

bashCopy
# Install Nodewarden alongside New Relic
curl -sSL https://app.nodewarden.com/install | bash

# Both agents can coexist during migration

Step 3: Migrate Synthetic Monitors

Convert New Relic Synthetics to Nodewarden HTTP monitors:

1. Go to Hosts → Add New Host
2. Select "HTTP/HTTPS Website"
3. Configure URL, check interval, and expected status code

Step 4: Transition Infrastructure Monitoring

Once comfortable with Nodewarden:

bashCopy
# Stop New Relic infrastructure agent
sudo systemctl stop newrelic-infra
sudo systemctl disable newrelic-infra

# Nodewarden agent continues running

Migration from Grafana + InfluxDB

Step 1: Export Dashboard JSON

Export your Grafana dashboards:

1. Open each dashboard in Grafana
2. Click Share → Export → Save to file
3. Document the InfluxDB queries used

Step 2: Set Up Nodewarden

Install and configure the agent:

bashCopy
# Install agent
curl -sSL https://app.nodewarden.com/install | bash

# Nodewarden automatically collects system metrics
# No need for Telegraf configuration

Step 3: Recreate Visualizations

Nodewarden's dashboard builder supports:

• Time series graphs
• Gauges and stats
• Tables and lists
• Heatmaps

Step 4: Historical Data

For historical data preservation:

• Keep InfluxDB running for historical queries
• Use Nodewarden for real-time monitoring going forward
• Export critical historical data if needed

Migration Checklist

• [ ] Inventory current monitoring

  • List all monitored hosts
  • Document critical alerts
  • Export dashboard configurations

• [ ] Plan migration phases

  • Start with non-critical systems
  • Run agents in parallel initially
  • Gradually move production systems

• [ ] Install Nodewarden agents

  • Use automated installation script
  • Configure API keys and host IDs
  • Verify data collection

• [ ] Recreate monitoring setup

  • Build dashboards
  • Configure alerts
  • Set up notification channels

• [ ] Validate and optimize

  • Compare metrics accuracy
  • Adjust alert thresholds
  • Train team on new interface

• [ ] Decommission old system

  • Stop old monitoring agents
  • Archive historical data
  • Cancel old subscriptions

Common Migration Questions

Can I run multiple monitoring agents?

Yes, Nodewarden's lightweight agent can run alongside other monitoring tools during migration.

Will I lose historical data?

Nodewarden starts collecting data from installation. For historical data, you can:

• Keep your old system running for historical queries
• Export critical historical metrics
• Use Nodewarden for all new data

How long does migration take?

• Small environments (< 10 hosts): 1-2 hours
• Medium environments (10-100 hosts): 1-2 days
• Large environments (100+ hosts): 1-2 weeks with phased approach

What about custom integrations?

Nodewarden provides:

• REST API for custom metrics
• Webhook support for alerts
• Prometheus compatibility mode
• Agent SDK for custom collectors

Need Help?

Our migration support team is here to help:

• Documentation: Full API reference
• Email: support@nodewarden.com
• Chat: Available in-app during business hours

Start your migration today and experience monitoring that just works!