Bug 1685768 - Servicemonitor object for fluentd isn't created when using community-operators to deploy logging.
Summary: Servicemonitor object for fluentd isn't created when using community-operator...
Keywords:
Status: CLOSED DUPLICATE of bug 1683359
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.1.0
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-06 01:46 UTC by Qiaoling Tang
Modified: 2019-03-12 14:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-06 14:17:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Qiaoling Tang 2019-03-06 01:46:30 UTC 
Description of problem:
Deploy logging via community-operators, check servicemonitor object, only 
monitor-elasticsearch-cluster create, no object for fluentd.

$ oc get servicemonitor
NAME                            AGE
monitor-elasticsearch-cluster   24m

Version-Release number of selected component (if applicable):
4.0.0-0.nightly-2019-03-05-065158

How reproducible:
Always

Steps to Reproduce:
1.Deploy logging via community-operators
2.check servicemonitor object in logging namespace
3.

Actual results:
Servicemonitor object for fluentd isn't created along with logging stack

Expected results:


Additional info:
Comment 1 Jeff Cantrill 2019-03-06 14:17:01 UTC 
Closing as duplicate.  The fact is we can't get metrics and part of that is OLM does not use the manifest so we need the operator to create a servicemonitor.  There isn't a need to introduce another issue.

*** This bug has been marked as a duplicate of bug 1683359 ***
Note You need to log in before you can comment on or make changes to this bug.