View all content tagged with Instrumentation
If your app is written in .NET, you can get started quickly with Lightstep. Download the Auto-Installer, then configure it to communicate with your Lightstep Satellites. When you deploy your app, all supported libraries will begin sending trace data to Lightstep.
Lightstep can ingest infrastructure metrics from your instrumentation to report on things like CPU and memory usage to help you resolve incidents fater.
If you've already instrumented your system, but were using another tracing library, no worries! Lightstep can ingest that instrumentation with almost no additional code needed.
If you've already instrumented with OpenTelemetry using Collectors, then getting data into Lightstep requires only an edit to the configuration file.
Configure your tracer to communicate with the Lightstep Satellites and create a single span on your C# service. You install both the OpenTracing API and Lightstep tracer and then use the OpenTracing and Lightstep APIs to instrument your code.
This Quick Start will have you configure your tracer to communicate with the Lightstep Satellites and create a single span on your C++ service. You install both the OpenTracing API and Lightstep tracer and then use the OpenTracing and Lightstep APIs to instrument your code.
Best practices in distributed tracing for documenting the system behaviors that are expected to change along with a particular code change.
Lightstep use access tokens to identify the project the tracer is reporting for. Lightstep Satellites need this token to accept and store span data from the tracer.
A key part of an organization's observability strategy is creating and maintaining the ability to think about and compare applications “horizontally”. When telemetry for observability is unique to each application or framework it causes new organizational issues.
Configure your tracer to communicate with the Lightstep Satellites and create a single span on your Go service. You install both the OpenTracing API and Lightstep tracer and then use the OpenTracing and Lightstep APIs to instrument your code.
Use OpenTelemetry to instrument your services and have the resulting data sent to Lightstep.
Lightstep works with many service meshes, and Lightstep + Istio is an easy way to get quick visibility into service performance and availability from the perspective of the service mesh.
Observability gives you the necessary information about the health and efficiency of your system. However, systems are large and complex, so the question is what do you decide to measure and where do you start?
If your app is written in Java, you can get started quickly with Lightstep. Download the Java SpecialAgent, then configure it to communicate with your Lightstep Satellites. When you deploy your app, all supported third-party framework libraries (like the Elasticsearch client, RxJava, or the Kafka client) will begin sending trace data to Lightstep.
Configure your tracer to communicate with the Lightstep Satellites and create a single span on your Java service. You install both the OpenTracing API and Lightstep tracer and then use the OpenTracing and Lightstep APIs to instrument your code.
Configure your tracer to communicate with the Lightstep Satellites and create a single span on your JavaScript service. You install both the OpenTracing API and Lightstep tracer and then use the OpenTracing and Lightstep APIs to instrument your code.
Lightstep integrates with leading cloud-native technologies, service meshes for microservices, and enterprise data visualization and collaboration tools. These turnkey integrations make it easy to deploy Lightstep across large-scale production systems so users get the unrivaled performance insights it provides when they need it and as part of their standard, established workflows.
Having effective load balancing of your Lightstep Satellites is important to ensure a consistent and adjustable recall window for the Satellite pool and allow for efficient use of Satellite computing resources.
Lightstep automatically determines how well your services are instrumented and performing, and sends email notifications that let you know how you're doing.
The span data that you view and use in Lightstep for observability into your system depends on the quality of your tracing instrumentation. Lightstep analyzes the instrumentation on your services and determines how you can improve it to make Lightstep work even better for you.
Use OpenTelemetry bridges to easily move from OpenTracing to OpenTelemetry
Lightstep performance is based on the ingress and egress of data from the tracers to the Satellites, the amount of memory the Satellites have to store that data, and the length of the recall window. You can monitor the performance of Lightstep and tune Satellites to avoid dropped spans.
The Reporting Status page provides an active view of the Lightstep Tracer clients and Satellites over a trailing 60-second window.
If your app is written in Node.js, you can get started quickly with Lightstep. Download the Auto-Installer, then configure it to communicate with your Lightstep Satellites. When you deploy your app, all supported libraries will begin sending trace data to Lightstep.
Configure your tracer to communicate with the Lightstep Satellites and create a single span on your Objective-C/Swift service. You install both the Lightstep tracer and then use the Lightstep API to instrument your code.
Configure your tracer to communicate with the Lightstep Satellites and create a single span on your PHP service. You install the Lightstep tracer and then use the Lightstep API to instrument your code.
Learn how distributed tracing sampling impacts the ability to analyze observability data, using key=value restrictions for some keys and grouping the output based on other keys.
If your app is written in Python, you can get started quickly with Lightstep. Download the Auto-Installer, then configure it to communicate with your Lightstep Satellites. When you deploy your app, all supported frameworks, data stores, and libraries will begin sending trace data to Lightstep.
Configure your tracer to communicate with the Lightstep Satellites and create a single span on your Python service. You install both the OpenTracing API and Lightstep tracer and then use the OpenTracing and Lightstep APIs to instrument your code.
Learn how to instrument your application using OpenTelemetry and then send data to Lightstep.
Learn how to instrument your application using OpenTelemetry and then send data to Lightstep.
Learn how to instrument your app for distributed tracing using OpenTracing and Lightstep.
If your app is written in Ruby, you can get started quickly with Lightstep. Download the Auto-Installer, then configure it to communicate with your Lightstep Satellites. When you deploy your app, all supported libraries will begin sending trace data to Lightstep.
Use Ruby to instrument your app for distributed tracing using OpenTracing.
Configure your tracer to communicate with the Lightstep Satellites and create a single span on your Ruby service. You install both the OpenTracing API and Lightstep tracer and then use the OpenTracing and Lightstep APIs to instrument your code.
Distributed tracing provides a view of the life of a request as it travels across multiple hosts and services communicating over various protocols. With distributed tracing implemented, you have a window into performance at every step in the request.
A span can have zero or more key/value *attributes*. Attributes allow you to create metadata about the span.
If you're currently using Jaeger for tracing, you can configure the Jaeger agent to send that data directly to Lightstep Satellites with little change. This is a great way to reuse your existing instrumentation architecture either directly in production or to quickly try out Lightstep for the first time.
Learn about OpenTracing and how to instrument your app for distributed tracing and observability.
If you're currently using Zipkin for tracing, you can configure it to send that data directly to Lightstep Satellites with little change. This is a great way to reuse your existing instrumentation architecture either directly in production or to quickly try out Lightstep for the first time.