Lightstep Observability supports metric data from many different sources:

  • Datadog: You configure a Datadog agent to “tee” traffic to both Lightstep Observability and Datadog.
  • Prometheus: You use the OpenTelemetry Collector scrape metrics from OpenMetrics/Prometheus endpoints.
  • AWS: You create a Cloudwatch Metric Stream that pushes metrics to Lightstep. Lightstep retrieves resource metadata using an AWS role and policy that allows read-only access to your resources.
  • Google Cloud Monitoring (formerly Stackdriver): You send metrics and resource tags and metadata to Lightstep by creating a service account that allows Lightstep read-only access to the metrics.
  • Java/JMX: Use the OpenTelemetry Collector to receive metrics JMX metrics and export them to Lightstep.
  • Kafka: Use the OpenTelemetry Collector to receive metrics Kafka and JVM metrics and export them to Lightstep.
  • NGINX: Use the OpenTelemetry Collector to receive metrics NGINX metrics and export them to Lightstep.
  • Redis: Use the OpenTelemetry Collector to receive metrics NGINX metrics and export them to Lightstep.
  • OpenTelemetry: You can send metrics to Lightstep Observability using the OpenTelemetry Protocol (OTLP). If you are interested in experimenting with the latest from OpenTelemetry, you can use either the Collector or the SDK.

    This protocol and specification are still under development, so there may be features that are unsupported by Lightstep Observability. Please refer to this page for the most up to date information about our OpenTelemetry Protocol support.

Once you send metrics to Lightstep Observability, you can create charts, dashboards, and notebooks, set thresholds that trigger alerts, and use Change Intelligence to find the root cause of metric deviations, without leaving Lightstep.Change Intelligence