LightStep records a vast amount of data about your production system: so much that a search on Explorer often only surfaces data from the last few seconds.
Streams provide the flexibility and specificity of arbitrary Explorer queries with the durability and time series statistics of tracked operations.
Streams tell LightStep to summarize the behavior of arbitrary slices of that data, creating plentiful example traces along the way. Both the statistical time series data and example traces are stored for all time, and can be subject to SLAs and alerting rules like any tracked operation in LightStep [𝑥]PM.
It’s easy to create Streams:
- Navigate to Explorer via the top navigation bar
- Enter your search (see full syntax notes below)
- Click on the “Create Stream” icon at the right of the search box
To return to the results of a Stream at any time:
- Navigate to “Streams” via the top navigation bar
- Click on the search query text in the resulting table
- The Stream results are a stable and shareable URL: perfect for alert messages, slack messages, and bot auto-responses
Query Syntax: Streams (and Explorer) supports queries that combine zero or more of the following term types:
component:<name> → confine the query to a particular component
operation:<name> → confine the query to a particular operation
tag:<key>=<value> → query for a particular tag key-value pair
All query terms are
api-server calls when errors occurred
buy_something transactions associated with your customer,
your CEO’s requests
experiment 42’s impact on your customer,
beta_users of the
any spans, regardless of the component, with a
status_code of 500
Any Stream can be paired with an SLA and notification policy; this allows for continuous reliability monitoring of any slice of your production data in LightStep. For instance, some LightStep users assign SLAs to particular
customer_ids within their own systems to detect and correct per-customer problems before they're even reported.
Streams can be created, managed, and even added to LightStep dashboards via LightStep's programmatic API. Details can be found in the LightStep Public APIs.