Schema explorer
Overview
Schema explorer helps you unify and control the structure of your logs in Coralogix. Since logs often come from many sources with different naming conventions (username, userName, user-name), inconsistencies can quickly make analysis harder.
The Schema explorer automatically detects, highlights, and reports on these differences so you can:
- Prevent duplicate fields.
- Reduce query errors caused by inconsistent keys.
- Discover and resolve duplicate or conflicting fields.
- Provide feedback to developers when fields are misaligned.
Key Features
Schema Explorer
The Schema Explorer tab provides a complete view of the fields ingested across your logs. For each field, you can see:
- Path – The field name and location.
- Type – Data type (string, numeric, object, etc.).
- Popularity over time – How frequently the field appears.
- Cardinality – Number of unique values and how it changes over time.
- First seen / Last seen – When the field was ingested.
This helps you identify fields that may be redundant, inconsistent, or unexpectedly missing.
How It Works
- Ingestion – Coralogix ingests all log fields, regardless of structure or naming convention.
- Detection – Schema Management identifies duplicate or similar keys.
- Analysis – You can explore how each field is used, how often it appears, and its unique values.
- Unification – Align conflicting keys into a single schema, ensuring consistency across teams and services.
Example Scenario
You have three services sending user data:
- Service A uses
surname - Service B uses
familyname - Service C uses
family-name
Without Schema Management, your queries might miss data because the fields don’t match. With Schema Management, you can detect these variations and map them to a unified key such as last_name.
UI Walkthrough
- Go to Data Flow → Schema Explorer.
- Use the search bar to find specific fields.
- Review each field’s popularity, type, and cardinality to identify duplicates or inconsistencies.
- Use Mapping Exceptions to align similar fields into a single schema.
Best Practices
- Regularly check for new fields ingested to catch inconsistent naming early.
- Standardize field names with your development teams to reduce mapping exceptions.
- Reserve fields for critical identifiers that must remain consistent across services.
To take schema governance a step further, Coralogix provides Reserved Fields which are a way to explicitly define the fields that matter most for your queries, alerts, and dashboards. While Schema Explorer helps you discover and analyze fields, Reserved Fields let you lock in critical ones, ensuring they are always indexed with the correct type and available for use.