Bug 1513019
| Summary: | [Docs][RFE][Metrics] Document how to use Journal to investigate log messages | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Emma Heftman <eheftman> |
| Component: | Documentation | Assignee: | Emma Heftman <eheftman> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Avital Pinnick <apinnick> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.0 | CC: | lbopf, lsurette, rbalakri, rmeggins, sradco, srevivo, ykaul |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-08 09:58:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1453771 | ||
| Bug Blocks: | |||
|
Description
Emma Heftman
2017-11-14 15:37:07 UTC
From dev bug, which is CLOSED UPSTREAM: We should align with the ViaQ/OpsTools policy and guidance on how to log and collects logs from these services. Rich/Shirly I need some information regarding how we use journal to log collectd and fluentd. I've looked on the collectd.org site but come up blank. I found this link on OCP site about how they are using journal: https://docs.openshift.com/container-platform/3.6/install_config/master_node_configuration.html#master-node-config-logging-levels How much of this is relevant for us? What is the default logging level? What are the ViaQ recommendations? Thanks! Use `journalctl -u fluentd` to examine the fluentd logs. Use `man journalctl` to see more options about using journalctl (e.g. how to search, how to control line wrapping/truncating). Same with collectd - `journalctl -u collectd` Shirly, I'd also like to understand the context for using each of these log files. Should they refer to collectd for issues referring to collecting metrics and fluentd for issues referring to collecting logs, i.e. 1. Information that they expected to see is missing? 2. An entire metric is missing? 3. Information in Metrics store seems to be incorrect? For metrics collections, should the be looking at both collectd and fluentd logs and if yes, what kind of issues would you recommend referring to collectd and what kind of issues should they use fluentd for? The should open a bug if a feature is missing like a metric or if data seems incorrect. If this is indeed a bug in fluentd / collectd we will open the bug on them. (In reply to Shirly Radco from comment #8) > The should open a bug if a feature is missing like a metric or if data seems > incorrect. If this is indeed a bug in fluentd / collectd we will open the > bug on them. So when do you see users using journal. Can you describe the use case please. Hey Avital Please review this MR: https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Virtualization/merge_requests/933 The documentation will be available with the release of Beta 3. |