Triggers in Helios enable users to reproduce specific flows fast. The trigger is essentially the root span of the trace, and can often be generated from a specific trace to reproduce that flow again.
In addition, through the trace visualization it is possible to generate the trigger for specific spans inside the trace itself. This functionality is accessible directly from each applicable span.
Learn more about unlocking the power of easily replaying E2E flows across distributed applications in this blog post by Helios senior software developer, Yaron Dinur.
Traces resulting from triggers generated in Helios are indicated as such using the Helios watermark.
Once the trigger code is generated, users can easily edit its configuration. Values can be updated inline directly, or alternatively variables may be used.
Editing triggers on the fly can be particularly useful when trying to test quickly how different parameters impact the flow at hand.
Generating trigger code is supported in Node.js and Python. Users can then quickly copy the generated code and use it to reproduce the flow.
Triggers can also be generated as a cURL command. Users may then quickly copy the output and run it to reproduce the flow.
Users can retrieve the trigger code in a file ready to be uploaded into Postman. There it can be easily executed and added to existing trigger collections.
You may choose to reproduce a flow by running the trigger directly in Helios. Once the flow execution is complete you will be automatically directed to the resulting trace visualization.
Running a trigger in Helios requires a one-time installation of Helios CLI - and afterwards no manual action is required when reproducing a flow.
Updated about 2 months ago