-
Notifications
You must be signed in to change notification settings - Fork 0
Log Message Reference
In preparation. This catalog is being built out per component and grows over time.
When a deployment emits a WARNING or SEVERE log message, this page tells you what it means and what to do about it. It is a lookup, not a manual - go straight to the component that logged the message.
Finding the component. Every log record carries the logger name (the ln field - see Operations: Logging); that name identifies the component and matches a section below. SEVERE means system-down; WARNING means an error the system is operating through.
Audience: Operator (primary), Developer.
One section per component. Within each, a row per message the component can emit at WARNING or SEVERE:
| Column | Meaning |
|---|---|
| Message | The message text (or its stable pattern, with variable parts shown as <...>) |
| Level |
SEVERE or WARNING
|
| Meaning | What the condition is |
| Action | What an operator should do about it |
The messages originate in each component's WARNING/SEVERE log statements, so the catalog is refreshed by sweeping the components' sources - and a new component simply adds its own section.
Sections are added as they are catalogued. Template for a new component:
| Message | Level | Meaning | Action |
|---|---|---|---|
| (to be catalogued) |
- Operations: Logging - how to query these messages live.
- Operations: Troubleshooting & FAQ - symptom-to-remedy, which references this catalog.
Elastic MDS documentation - (c) MetaFluent LLC - Confidential. Tracked in IssueTracking#586.
Getting Started
Deployment Cookbook
Concepts
- Architecture: Basics
- Access Control
- Architecture: Advanced
- Security: Basics
- Security: Advanced
- Glossary
Configuration
Configuration Cookbook
Deployment
Operations
- Monitoring & Diagnostics
- Logging
- Dashboard
- Troubleshooting & FAQ
- AI-Assisted Troubleshooting
- API Token Administration
Diagnostic Cookbook
Developing Applications
Reference