Bug 2064982 - we can configure loglevel for alertmanager, the doc missed it
Summary: we can configure loglevel for alertmanager, the doc missed it
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Brian Burt
QA Contact: Junqi Zhao
Claire Bremble
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-17 03:04 UTC by Junqi Zhao
Modified: 2022-04-12 19:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-12 19:18:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHDEVDOCS-3875 0 None None None 2022-03-17 19:01:47 UTC

Description Junqi Zhao 2022-03-17 03:04:54 UTC
Document URL:
https://docs.openshift.com/container-platform/4.9/monitoring/configuring-the-monitoring-stack.html#setting-log-levels-for-monitoring-components_configuring-the-monitoring-stack

Section Number and Name:
Setting log levels for monitoring components

Describe the issue:
from 4.9, we could configure loglevel for alertmanager, see: https://issues.redhat.com/browse/MON-1661, but the doc does not mention it

Suggestions for improvement:
1. 
You can configure the log level for Prometheus Operator, Prometheus, Thanos Querier, and Thanos Ruler.
change to
You can configure the log level for Prometheus Operator, Prometheus, Thanos Querier, Alertmanager, and Thanos Ruler.

2.
Prerequisites section
If you are setting a log level for Prometheus Operator, Prometheus, or Thanos Querier in the openshift-monitoring project:
change to
If you are setting a log level for Prometheus Operator, Prometheus, Alertmanager, or Thanos Querier in the openshift-monitoring project:


Additional information:
apply for 4.9 and above versions


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