Bug 1513019 - [Docs][RFE][Metrics] Document how to use Journal to investigate log messages
Summary: [Docs][RFE][Metrics] Document how to use Journal to investigate log messages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Emma Heftman
QA Contact: Avital Pinnick
URL:
Whiteboard:
Depends On: 1453771
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-14 15:37 UTC by Emma Heftman
Modified: 2019-05-07 12:50 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-08 09:58:37 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Emma Heftman 2017-11-14 15:37:07 UTC
Troubleshooting for collectd and fluentd. Can use journal to investigate log messages from both. Need to check if fluentd or collectd have troubleshooting on their site and reference it.

Comment 1 Lucy Bopf 2018-03-01 04:34:36 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.

Comment 3 Emma Heftman 2018-04-02 11:58:29 UTC
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!

Comment 6 Rich Megginson 2018-04-03 16:34:21 UTC
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`

Comment 7 Emma Heftman 2018-04-04 06:32:21 UTC
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?

Comment 8 Shirly Radco 2018-04-04 08:22:44 UTC
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.

Comment 9 Emma Heftman 2018-04-04 12:40:41 UTC
(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.

Comment 15 Emma Heftman 2018-04-08 09:58:37 UTC
The documentation will be available with the release of Beta 3.


Note You need to log in before you can comment on or make changes to this bug.