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.

We’re excited to introduce the Pod Page Events Tab - your new window into all Kubernetes events at the pod level.

This tab provides a chronological stream of Kubernetes events specifically scoped to an individual pod, making it easy to troubleshoot issues and track changes as they happen.

What you can do:

• Trace pod lifecycle events like scheduling, state changes, and container restarts.
• Quickly identify errors and warnings affecting your pod (e.g., image pull failures, probe issues).
• Drill into event metadata for full transparency.

To get started, head over to a specific pod page in your Kubernetes cluster and click on the Events tab.

We’re excited to announce the launch of the Container Page - a new view that gives you deep visibility into all containers within a pod.

What’s inside:

• Container Status & Readiness: Instantly understand the current lifecycle and health of each container.
• Key Resource Metrics: Monitor real-time CPU and memory utilization for each container.
• Container-Level Details: Inspect the image and restart count.

Whether you're debugging pod behavior, checking rollout health, or optimizing performance, this page gives you the insights you need at a glance.

The Container Page is available directly within the Single Pod Page. Try it out!

We’re excited to announce the release of our new Logs Live Tail page - giving you real-time visibility into your logs as they stream from your environment.

Whether you're troubleshooting live issues or debugging during development, Logs Live Tail helps you stay on top of what’s happening right now, with no delays.

Key Features:

• Real-time log streaming from your environment
• Advanced filtering to narrow down noise and focus on what matters
• Full log message and fields visibility
• Automatic correlation to invocations for seamless end-to-end investigation

Usage Notes:

• The live tail view is limited to 50 new logs/second.
• If this limit is exceeded, a sampling mechanism will be applied to the live tail only. All logs remain accessible via the main Logs Search page.
• To minimize sampling we recommend applying filters to focus your view.

Start using Logs Live Tail today to streamline your debugging workflow and speed up incident resolution!

Investigate your logs faster and more intelligently with Lumigo Copilot!
Ask questions in natural language to extract key insights, surface metrics, identify unusual patterns, and get to the root cause quickly and confidently without writing a single query.

Example questions you can ask:

• How many red unicorn orders did we receive last week?
• What were the top error messages in the checkout service yesterday?
• What happened before the first “PaymentFailed” error on June 14th?

Just head to the Logs Search or SQL page and start investigating.