Bug 1538091 - Document fluentd file output plugin support
Summary: Document fluentd file output plugin support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: RFEs
Version: 1.0.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Shirly Radco
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On: 1523068
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-24 13:02 UTC by Shirly Radco
Modified: 2018-03-29 11:06 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-metrics-1.1.3.1-1.el7ev
Clone Of: 1523068
Environment:
Last Closed: 2018-03-29 11:06:33 UTC
oVirt Team: Metrics
Embargoed:
rule-engine: ovirt-4.2?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)

Description Shirly Radco 2018-01-24 13:02:13 UTC 
Description of problem:
Add  documentation for fluentd file output plugin.
Comment 1 Lukas Svaty 2018-01-26 15:29:37 UTC 
1. on incorrect input:
TASK [oVirt.ovirt-fluentd/client : Validate fluentd_output_plugin parameter] **************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "'incorrect_input' must be set to either 'elasticsearch' or 'fluentd'."}


there is no mentioning of 'file' param

2. this parameter is not mentioned in any of the readme, nor comment from config.yml, please document it
Comment 2 Yaniv Kaul 2018-01-29 08:39:19 UTC 
The patch is merged. Anything else needed here?
Comment 3 Shirly Radco 2018-01-29 16:52:17 UTC 
This is a clone of the original RFE, the patch attached is the RFE, I need to add documentation.

Since this is not meant for production use, but more for debugging I believe the priority is low.
Comment 4 Lukas Svaty 2018-03-07 12:13:44 UTC 
verified in ovirt-engine-metrics-1.1.3.2-1.el7ev.noarch
Comment 5 Sandro Bonazzola 2018-03-29 11:06:33 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.