From 93be1f23994cf9d5e42ba15aaa4205a9dfe7cea9 Mon Sep 17 00:00:00 2001 From: Haritha Hasathcharu <42366642+hasathcharu@users.noreply.github.com> Date: Thu, 13 Nov 2025 14:36:28 +0530 Subject: [PATCH 1/3] Add runtime logs filter guide --- en/docs/monitoring-and-insights/logs-overview.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/en/docs/monitoring-and-insights/logs-overview.md b/en/docs/monitoring-and-insights/logs-overview.md index de80c75..4c649f2 100644 --- a/en/docs/monitoring-and-insights/logs-overview.md +++ b/en/docs/monitoring-and-insights/logs-overview.md @@ -64,6 +64,21 @@ 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. +### Filtering 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 simply 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. From acfc31f68a61bdd784f29e39a89aba3dbfedc68e Mon Sep 17 00:00:00 2001 From: Haritha Hasathcharu <42366642+hasathcharu@users.noreply.github.com> Date: Fri, 14 Nov 2025 13:42:51 +0530 Subject: [PATCH 2/3] Address review suggestions --- en/docs/monitoring-and-insights/logs-overview.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/en/docs/monitoring-and-insights/logs-overview.md b/en/docs/monitoring-and-insights/logs-overview.md index 4c649f2..da6c401 100644 --- a/en/docs/monitoring-and-insights/logs-overview.md +++ b/en/docs/monitoring-and-insights/logs-overview.md @@ -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: @@ -67,6 +67,7 @@ Each gateway log entry displays the following details: ### Filtering 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. From 396146ead52dfff53f3adbb62239b9aad806366c Mon Sep 17 00:00:00 2001 From: Haritha Hasathcharu <42366642+hasathcharu@users.noreply.github.com> Date: Tue, 18 Nov 2025 08:42:13 +0530 Subject: [PATCH 3/3] Address review suggestions --- en/docs/monitoring-and-insights/logs-overview.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/en/docs/monitoring-and-insights/logs-overview.md b/en/docs/monitoring-and-insights/logs-overview.md index da6c401..3a6026f 100644 --- a/en/docs/monitoring-and-insights/logs-overview.md +++ b/en/docs/monitoring-and-insights/logs-overview.md @@ -64,18 +64,18 @@ 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. -### Filtering runtime logs +### 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. +- 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 simply type your search query in the search bar and press **Enter** to apply the content or regex search filter. +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).