> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/log-activity.md).

# Log Activity

## Overview

The Log Activity dashboard provides a visual representation of log activity within your environment. It includes charts and a detailed table view.

## Metrics

When analyzing the log activity in the table or chart view, consider the following log levels, which are color coded for better visibility:

* Info (Blue)
* Warning (Yellow)
* Error (Red)
* Fatal (Black)

## Log Analyzer Dialog

To view detailed log activity:

1. Navigate to Application Environments (see navigation flow examples below)
   1. Applications -> Your Application -> Environments -> Click Environment tile
   2. Home -> Environments at-a-glance -> Click Environment tile
2. Click on the Log Activity tile
3. Click on the "show more" button of the log entry you want to analyze

<figure><img src="/files/2JHWIXTxPFkkdeTOBLOl" alt=""><figcaption><p>Example of log entry describing where to access the log analyzer</p></figcaption></figure>

### Log details

When you view the log details, you will see:

* Log type
* Log date and time
* Short log message
* Code Snippet with highlighted location in code or stack trace
  * If file and location available in the log and the repository is accessible, the dialog will display a highlighted code block and the Location (the file path and line in code)
  * If code highlighting is not available, the stack trace will be displayed

#### Log Analyzer with code highlighting

<figure><img src="/files/0TkDEFsbPaSgL3JIX3nt" alt=""><figcaption><p>Log Analyzer Dialog with code highlighting and Location</p></figcaption></figure>

#### Log Analyzer without code highlighting

<figure><img src="/files/vBagvCFSuH2383KQ52JJ" alt=""><figcaption><p>Log Analyzer Dialog without code highlighting</p></figcaption></figure>

Additionally, using the other buttons in the dialog, you can do the following:

* Toggle log stack trace
* Show full log message
* Copy the displayed message (either the short or the full message)

## Pattern Grouping

The Log Activity view has a **pattern grouping** mode that automatically groups your logs by recurring patterns. Instead of scrolling through thousands of individual lines, you instantly see which errors are most frequent.

<figure><img src="/files/eRAX5rYs2pBcgRrmslCT" alt="Log Activity pattern grouping view showing recurring log patterns sorted by frequency"><figcaption><p>Pattern grouping view</p></figcaption></figure>

### How to use

1. Navigate to the Log Activity view for your environment
2. Click the **Group by pattern** toggle button in the toolbar (next to the Filter button)
3. The table switches to a grouped view showing patterns sorted by frequency (noisiest first)

### Drill down

Click any pattern row to filter the log list to only that pattern. The histogram updates to show that pattern's volume over time — so you can immediately see when the issue started or spiked.

To go back to the full list, toggle off the pattern grouping button.

### Filters

Your existing toolbar filters (level, hostname, search, time range) still apply in pattern mode — patterns are computed on the filtered set. This lets you narrow down to a specific time window or log level before grouping.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/application-overview/applications/environments/metrics/log-activity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.