Lumigo Release Notes logo

Release Notes

Back to Homepage Subscribe to Updates

Labels

  • All Posts
  • Announcement
  • feature
  • Improvement

Jump to Month

  • June 2024
  • April 2024
  • January 2024
  • October 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • February 2022
  • November 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
Improvement
11 months ago

Explore Page Advanced Analytics

We are excited to announce an improvement to the Explore page analytics!

The new, advanced analytics feature gives you more control over the visualization of your application’s performance, allowing for easier proactive troubleshooting and providing better insight into errors, bottlenecks, anomalies, and more.

With the new advanced options you can:

  • View a count of requests and errors, and the sum, avg., max., min., and p95 of the duration of requests.
  • Visualize the data over time, or by endpoint, resource name, execution tags, issue type, or service type.
  • Choose how to group the data - by resource name, execution tags, endpoint, or HTTP status code.
Improvement
a year ago

Enhanced Visibility into RED Metric Issues

We're happy to announce the release of a new Detailed Issue page for RED metric issues in Lumigo. With this latest update, troubleshooting metric issues becomes more efficient than ever before.

Key Benefits:
  • Easily pinpoint the conditions triggering the alert.
  • Access historical data on alert occurrences and duration.
  • Visualize metric values over time and identify threshold crossings.
  • Track resource activity over time, including request volume and error rates.
Create your own RED metric alerts from the alerts page and start debugging your issues easily and quickly.
Improvement
a year ago

Experience the Revamped Live Tail Page!

We're thrilled to announce a makeover of our Live Tail page, designed to enhance your debugging experience, with a more user-friendly, efficient, and visually appealing interface. 

Here's what you can expect from the new Live Tail:

  1. Autocomplete filter for simplified search: Say goodbye to multiple filters! With the autocomplete filter, finding specific requests or invocations has never been easier. 
  2. Links open in new tabs: We understand the importance of preserving your workflow. Now, all links within the Live Tail page, including open channels and collected data, open in new tabs.
  3. Direct link to Issue Details view: Quickly delve deeper into any issues you encounter with a direct link to the Issue Details view, where you can gain comprehensive insights into the root cause of problems.
  4. Better and easier-to-use UI: Our new UI is thoughtfully crafted to provide a seamless user experience.

For further information refer to our documentation.

Improvement
a year ago

Troubleshoot containers requests in real-time with Lumigo Live-Tail

We're excited to announce an upgrade to Lumigo's Live Tail feature. Now, Live Tail supports container requests, offering real-time monitoring and troubleshooting for your containerized services, in addition to Lambda function invocations.

Live-Tail streams your requests and invocations and adds the much-required information such as exceptions and the payload of each request that are needed to troubleshoot containerized services easily in near real-time.  

Use Live-Tail for:

  • Faster Debugging: Identify and resolve container-related issues with ease, reducing debugging time.
  • Streamlined Development: Get quick feedback during development with real-time insights.
  • Real-Time Troubleshooting: Access critical details like exceptions and request payloads for proactive issue resolution.

For further information refer to our documentation.

Improvement
2 years ago

Runtimes visualized in transactions and invocations

Many serverless and microservice applications are polyglots, with components written in different programming languages based on the task to accomplish, desired performance characteristics, libraries to reuse, developers' preferences and many other reasons. Lumigo now shows you the Lambda runtime and OpenTelemetry SDK language in the invocation and transactions graph, making it easier for you to contextualize the transaction and its components, and react faster to issues. Also, it is a nice splash of color ;-)

P.S. To keep transactions easy to read, the runtime will be hidden when, due to zoom level and screen size, graph nodes are less than 40px wide.

Improvement
2 years ago

Automatically filtering out healthchecks on ECS and Kubernetes

Health-checks are peculiar things

Healthchecks is a monitoring technique with a special place flavor: healthchecks are fired off at regular, frequent intervals (sometimes every 10 seconds, sometimes 1 minute) by orchestration platforms and monitoring tools. Most healthchecks are HTTP-based, and the returned HTTP response is checks based on the status code and (sometimes) content. But really, the only healthchecks a person needs to know about, are those that fail, which usually lead to containers being torn down and other disruptive infrastructure changes.

Issues with health-checks in Lumigo

Given that Lumigo's pricing model is based on the amount of requests we process, the large amount of successful healthchecks that every container workload undergoes leads to undesirable consumption of quota, for data that is effectively not useful. Moreover, successful healthchecks lead to noise in the Explore and Transactions view, degrading the overall experience.

Cutting the Gordian knot

Luckily, one can often spot recognize HTTP requests that are healthchecks pretty easily! Both AWS ELB health-checks, as well as Kubernetes ones (including EKS), come in with specific User-Agent headers. Lumigo now automatically drops in the data processing pipeline in the Lumigo platform all the spans that:

  1. Carry the User-Agent HTTP header with values that are known to be health-checks, specifically ELB-HealthChecker/* (AWS ELB, often used with Amazon ECS) and kube-probe/ (Kubernetes, including Amazon EKS)
  2. Return an HTTP status code that denotes a successful response (a.k.a.: `2xx` like `200 OK`, `201 Accepted`, etc.). This is because if a Health-check fails (e.g. returning HTTP status code 500), usually something bad is about to happen to your containers :-)

What do you need to do on your end?

Nothing. It just works with every version of tracers we released so far for containers and all HTTP OpenTelemetry instrumentations we have ever seen. Enjoy :-)

P.S.: Matching health-checks by path (e.g., /health) sounds like a good solution on paper, but in practice it leads to very annoying false-positives (i.e., HTTP calls that are NOT related with health-checks). Moreover, healthcheck paths are configurable, and practitioners do make use for that configurability, which would lead to false negatives (health checks we let through). User-Agent headers, on the other hand, are far less often changed by healthcheck systems. User-agent matching, on the other hand, is usually rather reliable for this use-case.

Improvement
2 years ago

Improved batch containerized workload support

Since we launched Amazon ECS support earlier this summer, we have come across many user workloads that behave like batch jobs (which, incidentally, we see often scheduled via AWS Batch and, occasionally, via AWS Step Functions). Rather than relying on long-running processes that receive request over HTTP, these workloads execute jobs pulled from the Amazon SQS or sometimes the process environment, perform computation involving databases, other services and messaging queues, and then terminate.

The most intuitive representation for such transactions consist of a "root" span representing the "main" method, with the outgoing requests to databases, messaging queues and other service nested directly under the "main" span. And this is how Lumigo will now represent these workloads, provided that you use the OpenTelemetry API to create the "root" span.

Lumigo now also supports the case where the distributed trace starts with an outgoing request, but given there is no common parent span, multiple such ongoing requests will each result in a separate transaction.

Enjoy this improved support for your containerized workloads and let us know what you think about it!

P.S. If you want a hand using the OpenTelemetry API to create root spans, we are happy to help! Let us know through the support channel, and we'll gladly arrange a call to help you out. It's usually just 5 minutes coding, and then pushing it to your environment to validate :-)

P.P.S.S. Lumigo now also shows Elastic Load Balancers that serve HTTP requests issued by containerized workflows.


Improvement
2 years ago

Amazon ECS OpenTelemetry Resource Attributes Now Supported


We extended Lumigo's support of OpenTelemetry resource attribute semantic conventions to cover the `cloud.platform` key and the Amazon ECS semantic conventions.

Our goal with implementing the OpenTelemetry semantic conventions is to enable you to get the best integration with Lumigo for your workloads even when not using the Lumigo OpenTelemetry distributions, but rather using upstream OpenTelemetry SDKs.

The Amazon ECS semantic conventions are not yet widely implemented in OpenTelemetry SDKs, but we are very much looking forward to contributing them to the community!

For more information about the OpenTelemetry semantic conventions supported by Lumigo, refer to the OpenTelemetry Supported Semantic Conventions documentation.

Improvement
3 years ago

New and improved System-Map

A new UI brings a best-in-class visual experience to your System Map, all with the same features you love, including filtering, to give you a detailed bird's eye view of your whole stack.

Improvement
3 years ago

Global Search Shortcut Has Been Improved

Search for pages, functions, and product documentation — all with keyboard shortcut to maximize your efficiency.

Hit Ctrl + K for Windows and Cmd + K for macOS to search for pages, functions, and saved documents.