Kubernetes metric alerts now include direct links to related logs, giving you instant context when issues arise.

When you set an alert on a Kubernetes resource metric (e.g. high CPU usage), the notification will contain a link to the logs from the affected pod or container at the time of the alert. With one click, you jump straight to the relevant logs, no searching required.

• Correlated insights: Correlation between metrics and logs, providing immediate context.
• No log hunting: Go directly to the right logs with a single click.
• Faster resolution: Move from detection to root cause in less time.

We’ve made a small but impactful improvement to our Slack alert notifications:

• Back to normal in threads: Instead of sending a separate message, the 'Back to normal' notification now appears as a thread reply to the original alert.
• Notification status updates: The original alert is updated with a ✅ once the issue is resolved.

This change makes it easier to track the status of alerts while keeping Slack channels cleaner and free of unnecessary clutter.

We’ve added more context to your alerts: the log lines that are related to the alert are now included directly in the notification.
This means you can quickly see what happened without logging into Lumigo, and then dive deeper in Lumigo if you need to investigate further.

This small but handy update saves you time and makes it easier to understand and act on alerts right away.

When chatting with Lumigo Copilot, you’ll now see two smart follow-up suggestions automatically generated by Copilot based on your ongoing conversation.

This feature saves you time and helps you uncover the next logical step in your troubleshooting or investigation session with Copilot.

Why use follow-up suggestions?

• Fresh perspectives: Explore new angles and directions you might not have thought of.
• Efficiency: Quickly jump to the next step without having to type a new question.

Just click on a suggested question, and Copilot will immediately start answering it, while also giving you two new suggestions to keep your investigation moving forward.

We’re excited to announce the release of Lumigo Operator version 67, which includes two key enhancements:

Cluster logs batching: You can now collect cluster logs with a batching mechanism. This lets you send a large volume of logs without hitting sending limits. The batching behavior is configurable via Helm parameters.

Prometheus Node Exporter image on ECR: In addition to supporting the official Prometheus Node Exporter by default, we now also provide the image on ECR (currently available for amd64 only) for improved reliability and accessibility.

To upgrade and start using these improvements, follow the documentation instructions.

Quickly find the exact trace you’re looking for by filtering based on specific JSON field key:value pairs from the request or response payload.

To get started:

1. Select the relevant JSON field name from the autocomplete dropdown, or simply type it into the search bar.
2. Enter the exact value you want to match and hit Enter.
3. Instantly see all traces containing that JSON field and value in their payload.

This feature gives you a powerful new way to pinpoint the datapoints that matter most, taking you one step closer to full visibility across your system.

Need to add something you forgot? Hit "Enter" too soon? Changed your mind or have a more urgent question?

You can now stop Copilot mid-response with the new stop button. No need to wait for the answer to finish, just interrupt and move on, saving valuable time and staying focused on what matters.

Lumigo’s new Kubernetes Event Issue Page lets you quickly understand recurring Kubernetes issues by showing error frequency over time, along with key metrics like CPU, memory, and pod statuses for the affected object.

Assess the blast radius by seeing which other issues impacted the same object or which other objects experienced the same error.

Use this page as a starting point to dive deeper into related logs, traces, metrics or Kubernetes events, everything you need in one place to move from detection to resolution faster.

We’re excited to announce the release of the Pod Application Issues Page: a new consolidated view that brings all your pod-related application issues into one place.

This page completes the observability cycle for your pods. In addition to metrics, logs, and events, you can now also see applicative issues, giving you a comprehensive understanding of each pod’s health and behavior.

What’s Inside?

• A clear list of all application issues affecting the pod.
• Key details like issue type, number of occurrences, and a distribution breakdown of error messages.
• A direct link to the latest invocation for each issue, so you can seamlessly continue your investigation.

How to Access It?

Navigate to your pod via the Kubernetes page, then click on the new Application Issues tab.

As Copilot performs investigations or queries your traces, you can now see the exact searches it performs directly on the Traces Search page, along with their results. This gives you full visibility into the queries Copilot generates and lets you pick up right where it left off! Just make sure the “Apply on page” feature is toggled on to view these searches as they happen.