Log List¶
Global Configuration¶
Note
This feature entry is visible only to members with management permissions.
On the Global Configuration page, you can centrally manage the following features at the workspace level:
-
Quick Filter Configuration: Customize the common quick filter panel across Explorers.
-
Top Fields Configuration: Configure the fields displayed at the top of each log entry in stack mode. Indexes without individual configuration use the global default configuration.
-
Display Items Configuration: Set the default display fields and their order in the data list for each index.
-
Query Acceleration Configuration: Enable acceleration for fields under an index to significantly improve query performance.
Quick Filter¶
Quick filter items configured here are applied to the quick filter panel on the left of all Explorers in the workspace and are visible to all members.
All filter fields added here automatically enable query acceleration for their respective indexes to ensure filtering performance. This association is a mandatory default behavior and cannot be disabled.
You can configure two types of fields:
-
Filter fields (currently active fields)
- Edit or delete individual fields.
- Delete all filter fields with one click.
-
Available fields (including business fields, system fields, and others)
- Add them as filter fields
If there are many fields, you can search for fields directly. If no query result exactly matches a value, you can create it and add it to "Filter Fields".
Empty (no data) entries in the quick filter are hidden by default; you can enable them here. After enabling, "No Data" entries are pinned to the top of each field value list and separated from other field values by a divider; they remain visible while scrolling the list. This configuration can only be operated by administrators and custom roles with the "Global Configuration" permission.
Global Quick Filter¶
Workspace administrators can centrally configure global quick filter items under Manage > Quick Filter. After the configuration is saved, all members can sync the latest global quick filter items by refreshing or re-entering the Log Explorer.
Global quick filter items and personal custom quick filter items are saved independently and do not overwrite each other:
- When administrators add, edit, reorder, or disable global quick filter items, members' existing personal quick filter items are not affected;
- In the quick filter bar, global quick filter items are displayed before personal quick filter items by default;
- If a global quick filter item and a personal quick filter item share the same name, both are displayed simultaneously and can be distinguished by their field identifiers.
When the global configuration changes, after you refresh the page, the system displays "Quick filters have been automatically updated to follow the global configuration." This message appears only once per Explorer and per version.
Top Fields Configuration¶
Configure the fields displayed at the top of each log entry in stack mode. Indexes without individual configuration use the global default configuration.
Global Default Top Fields¶
When an index has no dedicated top fields configured, the global default fields are used. Click "Edit" to adjust the globally displayed default fields.
Default fields: source, host, service, pod_name, container_name, duration.
Index Top Fields Configuration¶
Configure dedicated top fields for a specific index; these take precedence over the global default configuration.
- Click "+ Add Index Configuration", select an index, and configure the top fields (up to 8 fields);
- Top fields support selecting existing fields or manually entering field names; press Enter to add custom fields;
- After saving, logs under the index display the configured top fields in stack mode.
Added index configurations support editing and deletion.
Display Items Configuration¶
Configure the default display fields and their order in the data list for different log indexes, helping members quickly focus on the information they need when viewing an index. After configuration, when viewing the data list for an index, the system displays these fields in the configured order first, helping quickly focus on core information.
Select a log index on the left; on the right, select the fields displayed by default for the index and configure their display order.
For the current key field configuration, you can choose whether to sync all key fields to query acceleration.
Note
This configuration sets the default display template for the data list to optimize the initial viewing experience. Members can still customize the list fields in the Explorer through the "Display Items" feature, which is not limited by this default configuration.
Query Acceleration Configuration¶
Enable acceleration for fields under an index that are frequently used for filtering, grouping, or sorting, greatly improving query response speed for these fields. This configuration is applied at the index level.
- Left: index list;
- Right: select the available fields listed for each index to accelerate. You can view them later in the "Accelerated Fields" list above.
The "Accelerated Fields" list shows the complete list of accelerated fields for the current index, regardless of whether the fields appear within the current query time range.
After configuration changes, it takes about 5 minutes to take effect across the entire system. Once in effect, the fields are automatically added to the "Accelerated Fields" list.
Accelerated Fields That Cannot Be Disabled
The following three types of fields automatically appear in "Accelerated Fields" and cannot have acceleration disabled:
-
Official default accelerated fields: system-preset key fields;
-
Quick filter fields: fields from the quick filter configuration;
-
Synced key fields: when the sync toggle in the key field configuration is enabled, all key fields automatically have acceleration enabled.
Go to Log Explorer > Global Configuration > Query Acceleration Configuration. The index list is on the left, and the right side shows the complete list of accelerated fields for the current index. Even if an accelerated field does not appear within the current query time range, it is still displayed in the list.
Add Accelerated Fields¶
Click "+ Add Accelerated Fields". An add row appears above the Accelerated Fields list:
- Select a field from the dropdown, which supports fuzzy search; or enter a field name directly;
- Click "Add" to add the field to the Accelerated Fields list below;
- Click "Cancel" to exit the add state without adding a field.
JSON Path Nested Field Query Acceleration¶
For nested fields in JSON-format fields, you can configure query acceleration using JSON Path. JSON Path specifies the location of a field within JSON, such as the duration of a request or a value in a request header.
- Go to Log Explorer > Global Configuration > Query Acceleration Configuration, and select the target log index;
- Click Add Accelerated Fields, and enter the complete JSON Path to accelerate;
- Click Add to complete the configuration. Configuration changes take effect in about 5 minutes. After that, the field can be viewed in the Accelerated Fields list without re-adding.
Use the format fieldname@JSONPath; when the field name is omitted, the message field is used by default. For example:
| Configuration Value | Description |
|---|---|
@request.duration |
Enable acceleration for the nested field request.duration in message. |
payload@request.headers["user-agent"] |
Enable acceleration for the nested field user-agent under request.headers in payload. Keys containing special characters are represented with square brackets and quotation marks. |
For example, when the JSON content of message is {"request":{"duration":120}} and you need to accelerate the inner request.duration, enter @request.duration. The path must match the actual JSON structure. For the complete syntax, see DQL JSON Field Extraction.
Configuration After Switching to a Full-Line Index
If you have configured query acceleration for JSON Paths in the message field of the original log index, you need to reconfigure query acceleration for these JSON Paths after switching to a full-line index. Record the relevant configurations before switching, then re-add and verify them in the query acceleration configuration of the corresponding index after switching.
Remove Accelerated Fields¶
- Remove individually: click "Delete" for the corresponding field in the Accelerated Fields list;
- Remove in bulk: click "Delete All Accelerated Fields" to clear all accelerated fields of the current index.
Accelerated Fields That Cannot Be Removed
The following three types of fields automatically appear in "Accelerated Fields" and cannot be removed:
- Official default accelerated fields: system-preset key fields;
- Quick filter fields: fields from the quick filter configuration;
- Synced key fields: when the sync toggle in the key field configuration is enabled, all key fields automatically have acceleration enabled.
Note
- Field types and available acceleration methods are subject to the configuration page of the current index;
- Each index supports up to 200 query-accelerated fields. When the limit is reached, the system prevents further additions and displays: "The query acceleration field limit has been reached. Each index supports up to 200 fields."
Index¶
By setting up log multi-index, you can store logs that meet certain criteria in different indexes and select an appropriate data storage policy for each index, effectively reducing log data storage costs.
The index list uses a scroll-loading mechanism. Pagination and the batch load size of 50 only count regular indexes. Clone indexes are displayed as secondary rows under their source indexes and do not occupy the pagination quota of regular indexes. Scrolling to the bottom automatically loads the next 50. This loading method applies only to the index selection list and is unrelated to pagination or scrolling in the log data list.
You can perform the following operations:
-
Select all indexes (❗️may slow down queries due to excessive data volume);
-
Select multiple indexes;
-
Pin an index to the top;
-
Search and locate an index by name. Press Enter after entering a keyword to execute the search; the index list is not automatically refreshed during input;
-
Set the index display area to Small, Medium, or Large.
-
Click the jump icon at the end of an index to open the corresponding index in a new tab.
After configuration, you can switch between different indexes in the Explorer to view the corresponding log content.
Index Does Not Exist
When opening the Log Explorer via a link, if the index specified in the link does not exist, the system displays "The current index does not exist. Switched to available index 'xxx'." and automatically switches to the first loaded index.
Clone indexes are displayed as child nodes of their source index. The source index and its clone indexes cannot be selected at the same time; the wildcard * does not include clone indexes. To query clone indexes, you need to explicitly select the corresponding index.
For the display, search, and query scope of clone indexes, see Viewing and Querying Clone Indexes.
Index Query History¶
Click the history icon on the right side of the search box to view recently used log indexes.
- Single-index history displays the index name directly;
- Multi-selected indexes are separated by commas, for example
default,application,security; - After clicking a history record, the system selects all indexes in the record;
- If some indexes in a history record have been deleted or are currently unavailable, the page prompts and keeps only the available indexes;
- Applying index history does not clear the current time range, search conditions, or quick filter conditions.
Quick Filter¶
For more details, see Filtering.
In the Log Explorer, non-numeric field values in the quick filter are sorted by their occurrence count within the current full query scope in descending order by default, showing the true Top N. The statistics scope is jointly determined by the current index, time range, query mode, search conditions, and filter conditions; it does not use the data already loaded on the current page as a sample.
Display Items¶
The Display Items page displays two groups of fields:
-
Displayed fields: fields shown in the current log data list;
-
Available fields: all fields cached for the current data type.
You can perform the following operations:
-
Search for fields; if no query result exactly matches a value, you can create it and add it to "Displayed Fields";
-
Edit field aliases;
-
Drag to adjust field order;
-
Delete fields (or delete all fields);
-
Reset to default fields;
-
Set whether to display field aliases and the time column.
When you reopen the Display Items configuration, the system restores the position where you last stayed. After adding, deleting, or sorting fields, you do not need to search from the top of the list again when re-entering the configuration page.
Field Value Sorting¶
Candidate values for non-numeric fields in "Display Items" are sorted by occurrence count in descending order by default. The sorting is based on the complete statistics scope to generate a true Top N and is not affected by the current list pagination or scroll-loading count.
After switching Standard, DQL, log index, time range, or query conditions, the system recalculates statistics based on the new query context.
Filtering by null and Empty Strings¶
The field list on the left side of the Log Explorer counts and displays null and empty strings "" separately:
null: the field does not exist in the current log, or the field has no value;"": the field exists in the current log, but the field value is an empty string.
Click the corresponding value to add it as a filter condition. The value and its count are displayed in the list only when the corresponding data exists in the current query results.
Standard mode and DQL mode use the same display and filtering rules.
Reset to Default Fields¶
When performing "Reset to Default Fields", the system displays fields according to the following rules:
- Regular indexes:
timeandmessageare displayed by default; whether the time column is displayed is still controlled by the "Show Time Column" toggle; - Full-line indexes:
timeand the business fields of the current index are displayed by default;messageis not displayed by default; - If an administrator has configured key fields for the current index, the key field configuration takes priority for display;
- Users can still manually add, remove, or adjust display fields.
Saving Display Items by Index¶
The Log Explorer saves the Display Items configuration of the current user independently for each log index.
For example, when selecting Index A and Index B separately:
- Adding a display field in Index A does not automatically add it to Index B;
- When switching to Index B, the system restores the Display Items last saved for Index B;
- When switching back to Index A, the system restores the Display Items configuration of Index A.
Display Items configurations are stored in the current user's browser and do not affect other members in the workspace.
Status Distribution Chart¶
The distribution chart counts the number of logs by time interval under the current index, time range, and filter conditions, helping you track changes in log status and total volume.
By default, logs are grouped by status and the count of each log status is displayed as a stacked bar chart. You can select Count under Avatar Menu > Preferences > Explorer > Status Distribution Chart to view the total number of log entries in each time period as a single-color bar chart. For detailed rules, see Status Distribution Chart Preferences.
After filtering logs, the chart updates to show the filtered results; when the current data lacks an available status field, a count distribution chart is displayed.
-
Hover over the chart to export it; it can be exported to a dashboard, note, or copied to the clipboard;
-
You can customize the time interval.
Query Mode¶
After the workspace enables long-term log storage, a toggle for Standard Query and Long-term Query appears in the top-right corner. This toggle switches queries between data at different storage tiers, and its specific usage depends on your data storage policy configuration.
| Query Mode | Data Source | Use Cases | Query Limits |
|---|---|---|---|
| Standard Query | Logs within standard storage | High-frequency analysis, real-time monitoring, retrieval over any time range | None |
| Long-term Query | Logs within long-term storage | Historical log lookup, low-frequency auditing | Maximum time range of 24 hours per query; Status Distribution Chart is not displayed |
If the workspace has not enabled long-term log storage, this toggle is not displayed in the Explorer.
Click to view more details on log query modes.
Instructions¶
-
The default mode when entering the Explorer is Standard Query, which supports queries over any time range with real-time responses.
-
After switching to Long-term Query, click the time input box to open the time selection panel:
-
Select the date: choose the start date on the left;
- Set the start and end time: select the start time and end time separately using the wheels on the right. If the end time is earlier than the start time, the system automatically identifies it as the next day, and the input box displays
2026-05-19 23:00:00 ~ Next Day 05:00:00; -
You can also drag the blue range on the timeline to pan it as a whole, or drag the left and right handles to fine-tune the start and end times. You may drag across midnight during the process; the day boundary is marked as "Next Day 00:00".
-
Below the timeline, the currently selected query range and total duration are displayed in real time. After confirming, click "Query" to trigger the search.
Search Bar¶
The Log Explorer search bar supports multiple search and filtering methods.
After entering search or filter conditions, you can preview the results and copy the conditions for use in charts or query tools.
Log Search Tips
. is no longer used as a token separator. It is recommended to enter a complete class name or complete path when searching.
Manual Input¶
Click the toggle button on the right side of the search box to enter manual query input mode.
Returning JSON Fields¶
Note
This feature is only applicable to user roles with DQL query permissions.
DQL queries support extracting nested values from JSON fields in log data. You only need to add a field path with the @ symbol to the DQL query statement; the system automatically recognizes the configuration and displays the extracted values as independent fields in the query results. For example:
- Normal query:
- Query after extracting nested fields:
In the Log Explorer, to directly specify viewing the values extracted from the JSON text of each log's message in the data list, add a field in the format @targer_fieldname in the Display Columns. As shown below, we added @fail_reason, which was already configured in the DQL query statement, to the Display Columns:
Log Color Highlighting¶
To help quickly locate key information in logs, after entering search conditions, the page highlights all matched content in the current query results, not limited to the message field. Other fields actually displayed in the list, stacked list, and log content are also highlighted if they match the search conditions.
Expanding and Copying a Single Log¶
-
Click the button in a log entry to view the complete content of the log. If the log supports JSON format, it is displayed in JSON format; otherwise, the content is displayed normally;
-
Click the button to copy the entire log content to the clipboard.
Displayed Lines¶
In the log data list, the timestamp and content of each log are displayed by default. You can use the "Displayed Lines" option to choose "1 line", "3 lines", "10 lines", or "All Content" to view complete log information.
"Scanned Volume" and "Count"¶
- Scanned volume: the size of data scanned during the actual execution of this query, used to measure query consumption. The larger the scanned volume, the larger the data scope that this query needs to search and process.
- Count: the number of results finally returned by this query, used to measure the scale of the query results. The count only represents the number of matched results and is not equivalent to the amount of data scanned during the query.
Note that there is no fixed conversion relationship between scanned volume and count. Because the size of a single log is not fixed, and a query may scan a large amount of data but only match a few results, you cannot directly infer the scanned volume from the count, nor infer the returned count from the scanned volume.

Settings¶
Create Monitor¶
When filtering log data, if you need further alert monitoring on the filtered results, you can create a monitor with one click. The system automatically applies your selected index, data source, and search conditions, simplifying the configuration process.
Note
-
If you selected another workspace in the top-left corner of the Log Explorer, the search conditions will not be synced to the monitor configuration page, and the monitor configuration page will be left empty by default;
-
In the regular Commercial Plan, the site-level
left*query feature is enabled by default. You only need to enable the workspace-levelleft*query to supportleft*queries for monitors. For the Deployment Plan, you can enable or disable the site-levelleft*query on your own. Only whenleft*queries are enabled at both the site and workspace levels can monitors performleft*queries. Otherwise, if the Log Explorer is configured with aleft*query, a query error may occur when jumping to the monitor.
Copy as cURL¶
In the Log Explorer, you can retrieve log data via the command line. In the Settings on the right side of the log data list, click Copy as cURL to copy the corresponding cURL command. Paste the command into a host terminal and run it to retrieve log data that matches the filter and search conditions within the current time range.
Example
After copying the cURL command, it looks as shown below: replace <Endpoint> with your domain name, and replace <DF-API-KEY> with your Key ID from API Management.
For more information about related parameters, see DQL Data Query.
For more API information, see Open API.
curl '<Endpoint>/api/v1/df/query_data?search_after=\[1680226330509,8572,"L_1680226330509_cgj4hqbrhi85kl1m6os0"\]&queries_body=%7B%22queries%22:\[%7B%22uuid%22:%222eb41760-cf6e-11ed-a983-7d559044c3fc%22,%22qtype%22:%22dql%22,%22query%22:%7B%22q%22:%22L::re(%60.*%60):(%60*%60)%7B+%60index%60+IN+\[%27default%27\]+%7D%22,%22highlight%22:true,%22limit%22:50,%22orderby%22:\[%7B%22time%22:%22desc%22%7D\],%22_funcList%22:\[\],%22funcList%22:\[\],%22disableMultipleField%22:false,%22disable_slimit%22:false,%22is_optimized%22:true,%22offset%22:0,%22search_after%22:\[1680226330509,8572,%22L_1680226330509_cgj4hqbrhi85kl1m6os0%22\],%22timeRange%22:\[1680187562081,1680230762081\],%22tz%22:%22Asia%2FShanghai%22%7D%7D\]%7D' \
- H 'DF-API-KEY: <DF-API-KEY>' \
- -compressed \
- -insecure
Note
Only Standard Members and above can copy command lines.
In addition to this export path, you can also use other log data export methods.
Set Status Colors¶
The system presets default colors for status values. If you need to customize the colors displayed for different statuses in the Explorer, click Set Status Colors to modify them.
Formatting Configuration¶
Note
Only Administrators and above can perform Explorer formatting configuration.
With Formatting Configuration, you can hide sensitive log content, highlight important log content, or enable quick filtering by replacing log content.
-
Click Settings in the top-right corner of the Explorer list;
-
Click Formatting Configuration;
-
Add a mapping rule, enter the following content, and save:
-
Field: specify a log field (for example,
content); -
Match Method: select a match method (currently supports =, !=, match, not match);
-
Match Content: enter the content to match (for example, DEBUG);
-
Display As: enter the content to display after replacement (for example, **).
-
Log Data Export¶
In the Log Explorer, you can first filter the desired data, then export it as CSV, JSONL, or TXT files, or export it to a dashboard or note.
In an HTTPS environment, CSV and TXT files can export up to 1,000,000 logs per export; JSONL files do not support this count limit. The actual export time is affected by the data volume and query conditions. Please wait patiently for the export to complete.
To export a specific log, open the detail page of the log and click in the top-right corner.
Advanced Field Link Configuration¶
For more details, see Advanced Field Link Configuration.














