Introducing Pipelines


February 20, 2020

When debugging a production system it is important that you can collect data at any time without impacting the system.  Keeping track of errors as they occur can be difficult, this is why we have added integrations to popular messaging systems so that you can be alerted in your chosen system when the Tracepoint is fired and take you straight to the snapshot.

Configuring a Pipeline

With these new pipelines, you can now trigger an alert into the services that you already use. The first this to do is to configure a pipeline, using the 'create' button in the top bar, and following the configuration options.

Pipeline Configuration

Alerting on a Tracepoint

Once you have a pipeline configured it is a simple matter of attaching the pipeline to a Tracepoint. This can be done via the Tracepoint selector, in the Tracepoint panel. Then when the Tracepoint is next triggered, the Pipeline will be triggered sending the context of the Tracepoint to the channel selected.

Tracepoint Selector

Coming Next

At this stage we are seeing simple alert messages in slack, discord etc with links back to to view the full context. The next stage in the pipeline roadmap is to add additional data to the integrations, such as watchers and stack trace. We are also looking to improve the number of services that we support by adding several new integrations including:

  • Datadog
  • Jira
  • Flowdock
  • and Custom webhooks

To request an integration please submit a request on the roadmap.



Experienced developer in various languages, currently a product owner of leading the back end architecture.