Migrate From Datadog

SigNoz provides a unified OpenTelemetry native solution for monitoring metrics, traces, and logs, allowing for greater flexibility and control over your data. This guide will walk you through the steps to migrate your existing Datadog setup to SigNoz, covering all essential signals: metrics, traces, and logs.

Migrating Metrics

Transitioning your metrics monitoring to SigNoz involves adopting the OpenTelemetry Protocol (OTLP) and configuring your systems to export metrics accordingly.

Switch to OTLP Metrics

It is recommended to switch to OTLP Metrics to monitor your existing system whereever possible. Below are some of the benefits of using OTLP:

Benefits of OTLP:

  • Standardization: OTLP is an open standard, reducing vendor lock-in and promoting interoperability.
  • Data Control and Privacy: Ensures complete ownership and security of telemetry data without third-party dependencies with help of OTel SDKs, Processors and collectors.
  • Compatibility: OTLP can be used with any OpenTelemetry-compatible vendor. 50+ observability/monitoring vendors today support OTLP.
  • Ecosystem Support: Widely adopted, ensuring compatibility with various tools and platforms.

Steps to Switch to OTLP Metrics:

  1. Configure Exporters:

    • Set up OTLP exporters to send metrics data to SigNoz.
    • Ensure your applications are exporting metrics using the OTLP protocol.
  2. Add OpenTelemetry Receivers:

    • Add OTLP receivers to your OpenTelemetry Collector. There are around 100 OpenTelemetry receivers available.
    • Refer to this SigNoz Guide on adding an OpenTelemetry receiver to OpenTelemetry Collector.
  3. Verify Data Reception:

    • Check SigNoz dashboards to confirm that metrics are being received and displayed correctly.

Use Prometheus Receiver if OTLP Metrics are not supported

If exporting OTLP metrics is not supported by tool, you can utilize the Prometheus receiver.

Configuration Steps:

  1. Enable Prometheus Receiver:

  2. Expose Prometheus Metrics:

    • Configure your applications to expose metrics in Prometheus format.
  3. Update Scrape Configurations:

    • Adjust the scrape configurations in the SigNoz OpenTelemetry Collector to include your application's endpoints.

Custom Metrics: From DogStatsD to OTLP

Replace DogStatsD with OpenTelemetry

For a more integrated approach, replace DogStatsD with OpenTelemetry metrics.

Steps:

  1. Update Client Libraries:

    • Replace DogStatsD client libraries with OpenTelemetry SDKs in your applications.
  2. Instrument Metrics:

    • Use OpenTelemetry APIs to instrument your custom metrics.

Example in Python:

from opentelemetry import metrics
from opentelemetry.sdk.metrics import MeterProvider

metrics.set_meter_provider(MeterProvider())
meter = metrics.get_meter("my_app", "0.1.2")

counter = meter.create_counter(
    name="requests",
    description="Number of requests",
    unit="1",
)

# Record a metric
counter.add(1, {"endpoint": "/api/v1/resource"})
  1. Configure Exporter:
    • Set up the OTLP exporter to send metrics data to SigNoz.

Continue to Use DogStatsD

You can continue using DogStatsD for custom metrics by configuring a Datadog receiver at your OTel Agent.

Using Datadog Receiver:

Import Prebuilt SigNoz Dashboards

Leverage prebuilt dashboards to visualize your metrics data effectively.

Available Dashboards:

  • Host Metrics
  • MySQL
  • JVM Metrics
  • And more...

Steps to Import:

  1. Access the Dashboards Repository:

  2. Choose Dashboards:

    • Select the dashboards relevant to your infrastructure and applications.
  3. Import Dashboards:

    • Follow the instructions provided in the repository to import dashboards into your SigNoz instance.

Handling Unsupported Datadog Integrations

If certain Datadog integrations are not directly supported by SigNoz, you can utilize the Datadog receiver to bridge the gap.

Refer to this ingesting Datadog metrics tutorial for detailed instructions.

Steps:

  1. Configure Datadog Receiver:

  2. Update Agents:

    • Point your Datadog agents to send data to the SigNoz OpenTelemetry Collector.

Migrating Traces/APM

Transitioning your tracing setup involves re-instrumenting your applications with OpenTelemetry SDKs to send trace data to SigNoz.

Switch to OpenTelemetry SDKs

Steps:

  1. Install OpenTelemetry SDKs:

  2. Instrument Your Application:

    • Use automatic or manual instrumentation to capture trace data.
  3. Verify Traces in SigNoz:

    • Use the SigNoz dashboard to ensure that trace data is being collected and displayed.

Migrating Logs

To migrate your logging setup, you need to configure appropriate log receivers and set up parsing pipelines in SigNoz.

Use OpenTelemetry Log Receivers

Available Receivers:

  • Filelog Receiver: For reading logs from files.
  • TCP/Syslog Receiver: For receiving logs over network protocols.
  • And more...

Steps:

  1. Configure Log Receivers:

  2. Update Log Sources:

    • Ensure your applications are writing logs to locations or endpoints monitored by the receivers.

Use SigNoz Log Parsing Pipeline to Structure Logs

Structuring logs enhances their usability and allows for more effective querying and alerting.

Steps:

  1. Understand Log Pipelines:

  2. Define Parsing Rules:

    • Create rules to parse unstructured logs into structured formats (e.g., JSON).
  3. Configure Pipelines:

    • Set up pipelines in SigNoz to process incoming logs according to your parsing rules.
  4. Test and Validate:

    • Verify that logs are correctly parsed and that the structured data is available in SigNoz.

Conclusion

Migrating from Datadog to SigNoz empowers you with an open-source observability platform that is flexible, extensible, and based on open standards. By leveraging OpenTelemetry, you avoid vendor lock-in and ensure compatibility across various tools and services. This guide provides a roadmap for transitioning your metrics, traces, and logs to SigNoz. For more detailed instructions and support, refer to the SigNoz documentation and community resources.


Additional Resources:

Was this page helpful?