Actions
Bug #50491
closedmgr/dashboard: centralized logging
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Monitoring
Target version:
% Done:
100%
Source:
Tags:
backport_processed
Backport:
quincy pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
User Story¶
As a Ceph operator I want to have a unified view of the logs from the different daemons, so that:- I can perform a backward/post-mortem analysis of events leading to an issue,
- I can monitor cluster events in real-time.
Persona¶
- Ceph cluster operator/sys admin
- Support engineer
- Developers
Context¶
Every daemon in Ceph stores its logs locally (there's a "cluster log" but it's extremely concise, and not useful for troubleshooting). This means that if a user wants to perform a post-mortem analysis of an issue, they have first to collect log traces from multiple hosts, which involves to:- Identify on which host a daemon is running,
- Log in to that host,
- Look for the log file in the filesystem,
- Open the log and perform a search.
For debugging a Ceph issue, users often have to follow the operational events from multiple daemons, so this tasks gets more and more complicated. Additionally, it's almost impossible to perform real-time (vs. post-mortem) troubleshooting.
Implementation details¶
To explore multiple stacks: ELK, Fluentd, Loki, etc.
This might be embedded via iframe as already done for Grafana dashboards, or accessed stand-alone.
References¶
Actions