Troubleshooting Issues
Overview
Lumigo Copilot is a powerful tool for troubleshooting issues inside of your production environment. We designed it to help you quickly identify what went wrong, and to understand how to fix it. Copilot relieves you of the need to cross-reference several streams of data at once to find an issue's cause.
- Traces
- Logs
- Metrics
- The request and response payloads for any service calls made inside the request flow.
Copilot will process this information to quickly deliver clear insights and conclusions, helping you solve or at least address the issue at hand. Additionally, it sifts through many logs and traces simultaneously. It does this in the span of seconds, saving you a considerable amount of time.
Troubleshooting Features
Below are some common scenarios and use cases where Lumigo's Copilot can help, sorted by where you will be using Copilot from. Copilot is available for direct questions about issues from Slack and Teams integrations, on the Issues page, and on the specific page of a Transaction.
From Slack & Teams
Using the integration, you can ask Copilot questions from Slack or Teams.
- “What’s causing this 405 error?” When you encounter a 405 Method Not Allowed error, Copilot can instantly aggregate information to pinpoint the root cause.
- “What’s the severity of this requests.exceptions.readTimeout issue?”
Timeout errors can have varying levels of impact depending on which services, endpoints, or user flows are affected. Copilot correlates alert data with real-time usage metrics and historical baselines to help you quickly assess the scope and severity of timeouts. - “Which users were affected by this Timed Out issue?”
Copilot analyzes request logs and error rates to identify affected users or user segments. This allows you to proactively reach out to impacted customers, monitor for recurring patterns, and implement more precise fixes.
From the Issues page
You can ask Copilot questions directly in the Issues page.
- "What's causing the timeout errors in my purchaseNewUnicron Lambda function?" Copilot can investigate the Timed out issue, analyze the root cause, and suggest solutions. This saves you time investigating yourself.
- "Which issue has been affecting my Kubernetes services the most in the last week?" Copilot can analyze issues like FailedToRetrieveImagePullSecret and Routing Error to identify patterns and impact. This allows you to see which issues are most impactful and need priority attention.
- "Has the TypeError in my getIssues Lambda been resolved?" Copilot can check if the TypeError is still happening or if it's been fixed. This allows you to see if you need to address the issue any further.

Copilot investigating whether an issue has been resolved
From the transaction page:
When on a specific transaction page only, you can ask Copilot in-depth questions about it.
- "Help me troubleshoot the Time Out concerning this Lambda page." Copilot can help you figure out a potential solution to a specific issue on your transaction's page.
- "Can you summarize this transaction for me?" Copilot can summarize what is happening in the transaction. In this case, it is a Lambda function.

Typical summary of a transaction
More
Updated 3 days ago