Skip to content

Add runtime logs filter guide #140

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hasathcharu wants to merge 3 commits into
base: main
Choose a base branch
from
+17 −1
Open

Add runtime logs filter guide #140

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
93be1f2
Add runtime logs filter guide
hasathcharu Nov 13, 2025
acfc31f
Address review suggestions
hasathcharu Nov 14, 2025
396146e
Address review suggestions
hasathcharu Nov 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion en/docs/monitoring-and-insights/logs-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ The log view also provides advanced filtering capabilities that allow you to eff

Devant runtime logs provide insights into both project and integration-level logs, covering application and gateway logs. These logs streamline the debugging process by centralizing diverse log sources.

In Devant, any organization member can view runtime logs via the runtime logs page. Devant allows you to apply filters based on parameters such as log **Type** (error, warn, info, debug), **Environment** (Development, Production), and **Time Range** to simplify debugging.
In Devant, any organization member can view runtime logs via the runtime logs page.

To access runtime logs, follow the steps below:

Expand Down Expand Up @@ -64,6 +64,22 @@ Each gateway log entry displays the following details:
- `integrationVersion`: The version of the invoked integration.
- `envName`: The environment of the inbound request. For example, Development, Production, etc.

### Filter runtime logs

Runtime logs can be filtered based on the following parameters:

- Type: Filter logs based on their type. Possible values are `Error`, `Warn`, `Info`, and `Debug`.
- Environment: Filter logs based on the environment in which the integration is running.
- Deployment Track: Filter logs based on the deployment track of the integration.
- Time Range: Filter logs based on a specific time range.
- Content Search: Filter logs based on specific keywords or phrases within the log messages.
- Regex Search: Filter logs using regular expressions to match specific patterns within the log messages.

You can type your search query in the search bar and press **Enter** to apply the content or regex search filter.

!!! note
Devant uses Lucene query syntax for regex search. For more information on Lucene syntax, see [Lucene Query Syntax Documentation](https://lucene.apache.org/core/2_9_4/queryparsersyntax.html).

## Audit logs

Audit logs, also called audit trails, enhance security, ensure compliance, provide operational insights, and help manage risks.
Expand Down