Log Field and Query Practices
When you need to make logs usable for recurring investigation, plan field semantics before configuring collection and use the same fields consistently in queries. This helps you narrow the scope of an issue with observable log records.
Plan the fields needed for investigation
Start with the fields that identify where a log came from and how it relates to other records, so that the same investigation can be repeated without relying only on raw log text.
- Use the Log Model Reference to distinguish predefined, parsed, entity, and tag attributes before defining or using a field.
- Check the model's Quick Filter? indicator when you expect a field to be available in the log query filter area. Not every parsed attribute is exposed there.
- Keep the field type in mind when preparing analysis. Parsed attributes are identified as text or numeric at creation time; query statistics use different aggregation options for qualitative and quantitative fields.
Align equivalent fields without changing source logs
When teams or historical log sources use different names for the same business concept, use Standard Attributes to correlate them while keeping the original application log structure unchanged.
- Go to Log Analysis > Log Configuration > Standard Attributes.
- Use an existing parsed attribute or create a Standard Attribute with its path, data type, description, and the source attribute names to map.
- Separate multiple source attribute names with English commas.
The mapping is especially useful for cross-team or historical log sources that cannot follow one naming convention. See Standard Attributes for the available default attributes and configuration details.
Expose fields that support the investigation task
Configure quick filters for the fields that operators need to use repeatedly, then use the displayed grouping, name, and description to make the filter easier to recognize.
- In Log Analysis > Log Query, select registered parsed attributes for the quick filter.
- Configure the display name, group, and description when needed. Changing these settings affects the filter panel display, not the parsed log field.
- In the query page, use the quick filter's column and Standard Attribute association actions to adjust how the field is used during analysis.
For the complete configuration procedure, see Log Query.
Start broad, then narrow the query with evidence
Use the list view to verify matching records first, then switch to charts, tables, rankings, or pattern recognition when you need to compare counts or field values.
- Select a precise time range and add conditions using keywords, attributes, or tags.
- Confirm the matching records in the log list and open a record when you need its context, source content, or related entities.
- Use chart analysis for dimensional statistics; statistical objects must be fields configured as quick filters.
- Use pattern recognition when you need to group logs with similar structures and inspect representative records.
Selecting a precise time range helps keep large-volume searches focused. The Log Query guide describes the available filter operators and analysis modes.
Review the model when fields or queries change
When adding a field or changing how it is used in a query, return to the model reference to verify its type, attribute category, and quick-filter availability before updating the query configuration.
Use Log Model Reference for field definitions, Standard Attributes for field mapping, and Log Query for investigation tasks.