# Logs Explorer The Logs Explorer is a comprehensive tool to **query and export logs from job executions and live deployments** on the Data Platform. ![logs](picts/cc-logs-explorer.png) Like all subcomponents in the Control Center, the Logs Explorer can be opened at the level of the organization. However, logs exploration will only be possible inside a specific Project. If the Logs Explorer is opened at the level of one Project, then this field cannot be edited. ![logs](picts/cc-right-dataplant.png) - [Get logs](#get-logs) - [Get logs of past job executions](#get-logs-of-past-job-executions) - [Get logs of deployments](#get-logs-of-deployments) - [Use the streaming mode](#use-the-streaming-mode) - [Filter logs](#filter-logs) - [Search in logs](#search-in-logs) - [Severity](#severity) - [Timestamp](#timestamp) - [Share logs](#share-logs) - [Share an Explorer link](#share-an-explorer-link) - [Export a log file](#export-a-log-file) --- ## Get logs ### Get logs of past job executions The Logs Explorer allows you to check the logs of: - [Data Processing Engine actions](/en/product/dpe/actions/index) job executions - [Data Processing Engine workflows](/en/product/dpe/workflows/index) job executions - [Connectors metadata extract](/en/product/connectors/analyzer/extract-metadata) jobs - [Lakehouse Manager physical build](/en/product/lakehouse-manager/tables/table-interactions) jobs Choose *Jobs* as the **Resource** on the left column. ![logs](picts/cc-right-jobs.png) Choose the **type of jobs** to explore. ![logs](picts/cc-jobs-type.png) By default, the Logs Explorer will display the logs for all jobs matching this type. You can drill-down on a specific object in the bottom left list - ranked by number of executions. ![logs](picts/cc-jobs-object.png) You can drill-down further by filtering on a specific **execution ID** or a specific time-range above the display. !> Make sure that the execution that you want to display is contained in the time-range that you are filtered on. ![logs](picts/cc-jobs-execution-timeframe.png) > Note that logs will be queried by successive batches of at most 250 logs. Scroll down in the console to load more logs. ### Get logs of deployments The Logs Explorer also allows you to check the logs of: - [APIs](/en/product/api-manager/index) - [Applications](/en/product/app-manager/index) - [Notebooks](/en/product/dpe/notebooks/index) - [Always-up deployments in the Data Processing Engine](/en/product/dpe/actions/settings/index?id=always-up) - The *App Service* component: an infrastructure service to control APIs and apps Choose *Deployments* as the **Resource** on the left column. ![logs](picts/cc-right-deployments.png) Choose the **type of deployment** to explore. ![logs](picts/cc-deployments-type.png) By default, the Logs Explorer will display the logs for all deployments matching this type. You can drill-down on a specific object in the bottom left list - ranked by number of active workers. By default, the logs of all workers for that deployed object are aggregated altogether in the display. ![logs](picts/cc-deployments-object.png) You can drill-down further by filtering on a specific **worker ID** or a specific time-range above the display. ![logs](picts/cc-deployment-worker-timeframe.png) > Note that logs will be queried by successive batches of at most 250 logs. Scroll down in the console to load more logs. ### Use the streaming mode By default, the Logs Explorer must be refreshed manually to display new logs. ![logs](picts/cc-left-refresh.png) Activate the **streaming mode** to receive the latest logs in real time. ![logs](picts/cc-left-streaming.png) --- ## Filter logs ### Search in logs To filter down your log result, it is possible to either search for an exact substring or to match to a [regular expression (Regex)](https://en.wikipedia.org/wiki/Regular_expression) using the search bar above the console. Searching something in the searchbar will **run a new log query on the whole timeframe** and return the logs matching the search filters. By default, simply typing text in the searchbar will search for all logs containing this substring, ignoring lowercase/capital letters. ![logs](picts/cc-left-searchlog.png) Alternatively, it is possible to start your search with any of the following operators: - `=` followed by text: search for all logs containing this substring (case sensitive) - `!=` followed by text: search for all logs not containing this substring (case sensitive) - `~` followed by a regex: search for all logs matching the regular expression - `!~` followed by a regex: search for all logs that don't match the regular expression ![logs](picts/cc-left-searchlog2.png) ### Severity Logs have different level of severity - ranged from *INFO* to *CRITICAL* - to filter on. > If you don't see all the levels that you should be seeing, make sure your jobs are [configured to export the correct level](/en/product/dpe/actions/settings/index?id=logs-level) of logs. ![logs](picts/cc-left-severity.png) ### Timestamp As mentioned above, logs are all associated to a specific timestamp, so they can be filtered on a time-range. For jobs execution logs, it is also possible to filter on one specific execution. ![logs](picts/cc-jobs-execution-timeframe.png) --- ## Share logs Logs can be shared in one of two ways: by sharing the link to the Logs Explorer or by exporting a text file containing the logs. ### Share an Explorer link Click on the **link** icon to get a link for the page with the current filter configuration. ![logs](picts/cc-left-link.png) ### Export a log file Click on the **export** icon to download a .log file containing the logs currently displayed in the UI. ![logs](picts/cc-left-export.png) ?> Share those log files to the Data Platform Support team whenever you need help debugging a Project on Data Platform. --- ### Need help? 🆘 > At any step, you can create a ticket to raise an incident or if you need support at the [OVHcloud Help Centre](https://help.ovhcloud.com/csm/fr-home?id=csm_index). Additionally, you can ask for support by reaching out to us on the Data Platform Channel within the [Discord Server](https://discord.com/channels/850031577277792286/1163465539981672559). There is a step-by-step guide in the [support](/en/support/index.md) section.