> ## Documentation Index
> Fetch the complete documentation index at: https://developer.upsun.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Your logs have something to say

> Log Explorer and the AI Log Analyzer bring your application, service, and infrastructure logs into one place, so anyone on the team can troubleshoot with context, not guesswork.


Logs have puzzled me for a long time.

When something breaks, they're the first place I look. I want to know what happened, and in what context. Simple enough, at least on paper.

In practice, logs are scattered across too many files, and most of what's in them is noise. You spot something odd in one file, then go hunting for the line somewhere else that explains it. It's slow. And the hunt almost never happens on a quiet afternoon. It happens when the clock's running, someone keeps asking for an update, and you can barely think straight.

I don't do well under pressure. For years I assumed that was a "me" problem. Call it imposter syndrome: I was sure everyone else could read logs fluently. Then we started talking to our users about troubleshooting. CTOs, lead developers, agency teams juggling dozens of client projects: they all described the same struggle.

So it wasn't just me. Not by a long shot.

At Upsun, we think a platform should do more than tell you something broke. It should help you work out why, right there, so anyone on the team can go from "it's broken" to "I know what to fix" without waiting for the one person who knows where to look.

That's where these two features came from. They ship together.

The first is [Log Explorer](https://developer.upsun.com/docs/observability/logs/log-explorer.md): one place to browse your application, service, and infrastructure logs. A few clicks in the Upsun Console narrow things down by kind, severity, service, and other dimensions like host or container ID, until you've gathered the context you need. It covers the last 24 hours and is available on AWS and Google Cloud Platform projects (not Azure or OVHcloud).

![Log Explorer with filters applied](https://mintcdn.com/upsun-c9761871/jSC-FTmFMGNQJAoa/images/posts/releases/your-logs-have-something-to-say/log-explorer.webp?fit=max\&auto=format\&n=jSC-FTmFMGNQJAoa\&q=85\&s=39b413568cefbe2280be1729a1ebfe24)

I've used Log Explorer daily on my own projects for months, while we were still fine-tuning it. No more hopping between files and terminals. It has saved me a lot of time, and a few headaches.

However, even with all my logs in one place, a nagging doubt remains. What if the root cause is sitting in a service I didn't think to check?

Some of you already have an answer: you feed your logs to a coding agent. It's a good instinct. Models are well suited to this kind of reading, and the more context they get, the better their recommendations.

Context is the key. A log file pasted into a chat window arrives alone. The difference between a guess and a diagnosis is providing sufficient context.

That's why we built the [AI Log Analyzer](https://developer.upsun.com/docs/get-started/ai/upsun-cloud-log-analyzer-agent.md): it runs inside your project, with all its context, right next to your logs. Add it to your project once, bring your own LLM provider API key, and from then on it's one click away. Set the time window and filters for what you want help with in Log Explorer, click **Analyze logs**, and it reads that scope, widening it when needed to see the whole picture.

It tells you what it found, why it thinks it happened, and what to do next. You remain in charge of the fix.

![AI Log Analyzer report](https://mintcdn.com/upsun-c9761871/jSC-FTmFMGNQJAoa/images/posts/releases/your-logs-have-something-to-say/log-analyzer-report.webp?fit=max\&auto=format\&n=jSC-FTmFMGNQJAoa\&q=85\&s=ef685226573e34008f2ffc874f693c0f)

Both features rely on the same Log APIs, which sit on our observability pipelines. We designed those pipelines to ingest large volumes of data from your apps, services, and infrastructure, so Log Explorer remains fast as your projects grow. We'll use the same pipelines for the observability features we add next.

We built Log Explorer and the AI Log Analyzer to make troubleshooting easier and less stressful. The clock will still tick; you'll just have more room to think, and a second pair of eyes that knows your project.

Your logs have been trying to tell you something all along. Find out what, before an incident spells it out for you. Open Log Explorer, filter the last few hours down to warnings and errors, and ask the AI Log Analyzer what it sees. You might be surprised by a project you thought you knew.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.