View all content tagged with Get Started
Get started with Lightstep by learning about how Lightstep works, how to get your application's telemetry data into Lightstep, and how to view that data to perform root cause analysis.
Learn how to improve your incident response capabilities using high-cardinality attributes in your instrumentation, creating alerts, and configuring Workflow Links.
Lightstep offers role-based access control (RBAC) to features and functionality. You can add users manually or automatically via domain whitelisting, allowing any user at the domain access without an explicit invitation.
You can have several projects in Lightstep. For example, you might have one project for your development environment and one for production. Or you may have projects for different areas of your application while they're in development.
It's easy to get started with Lightstep. Sign up for an account, add OpenTelemetry instrumentation to your service, and see data flow into Lightstep.
Learn how tracers, Satellites, the Hypothesis Engine, and the web UI work to analyze 100 percent of unsampled transaction data from distributed, deep systems to produce complete end-to-end traces and robust metrics that explain performance behaviors and accelerate root cause analysis.
Lightstep Satellites are straightforward to deploy using a Docker image, AWS/AMI, or a Debian package.
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.
Lightstep uses *Satellites* to collect 100% of the performance data that your tracing instrumentation generates. Satellites collect spans generated by instrumented clients and servers, and then process and temporarily store that data during trace assembly.
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.
When you are in Developer Mode, your Satellite runs on your machine, allowing you to collect and see only data that you create locally. You can start, stop, and configure your Satellite.
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.
Learn how to use Lightstep for many of your daily activities
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.
Developer Mode allows you to run a Satellite locally to view traces generated from your instrumented code as you write it. Reliable feedback helps build confidence that your code is correct, by quickly verifying your instrumentation using a console-like output.
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.