added

'Unnamed environment' special indication

When installing Helios in your services, the environment information of the root span for each trace is shown for full context. From time to time this bit is missing, often due to a slip in the installation itself. Now it's easy for users to flag this and act upon it, through the info/warning sign by the environments list dropdown.

improved

Operations list upgrade

We've improved the representation of operations on the 'Services' tab by explicitly and visually stating the origin and end of each operation.

added

Trace comments

Users can add comments on traces inside the Helios trace visualization. By tagging their team members, they can collaborate to gain insight and understand what's happened and what might need to change.

added

Custom instructions for using Helios

Users can now add custom instructions for using Helios in their team. Different dev teams have different methodologies of deploying and running Helios in their services, and often after the initial setup work is done - everybody can benefit from configuring Helios quickly in their environment and start using it.

added

Extracting variables from responses when building a test

Users can now extract a JSON value from a response in the test into a variable, and use it later in the test to perform the desired validation.

added

JSONPath validation support in test configuration

When generating tests in Helios, it's now possible to add validations on JSON structures. This allows for better granularity of control when building E2E tests based on traces already sent to Helios.

improved

Setup actions are part of test visualization

Setup actions are now an integral part of the test visualization - they are displayed as part of the flow on the test graph, and can be configured just as any other trigger or validation checkpoint included in the test.

improved

Better visibility into async (background) jobs

We've made it a lot more intuitive to understand what's going on with your asynchronous (background) jobs. Our trace visualization displays the different jobs that were triggered - within the same service or across multiple services - so that you can walk through the flow, inspect the triggers and really understand what went on.

added

Go instrumentation is live!

Developers working on microservices written in Go can now instrument their services using Helios and benefit from all that the platform has to offer in helping developers be more productive when designing, troubleshooting, testing and collaborating over distributed applications.

added

Span consumption breakdown

We've made the span consumption breakdown available so that it's easy to understand which services and environments are generating data and how.