Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1429875

Summary:	[RFE] Configure Apache collectd plugin
Product:	[oVirt] ovirt-engine-metrics	Reporter:	Shirly Radco <sradco>
Component:	RFEs	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED WONTFIX	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0.0	CC:	bugs, didi, lsvaty, pstehlik, sradco, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	sbonazzo: ovirt-4.3-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-05 11:10:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1402901, 1434573

Description Shirly Radco 2017-03-07 11:21:11 UTC

Description of problem:

The Apache collectd plugin requires
1. Enable the mod_status module in your Apache server.
2. Add the following configuration to your Apache server:

ExtendedStatus on
<Location /mod_status>
  SetHandler server-status
</Location>

3. Restart Apache.

4. Load the plugin and add the configuration to collectd.conf
This requires the following parameters:

Instance - The name of the server to be monitored

URL - The location at which collectd can retrieve output of mod_status.
Example: http://localhost:8080/mod_status?auto
Required to append the "?auto".

We need to add a way for the collectd.conf can consume this information.

Comment 1 Shirly Radco 2017-03-28 10:28:48 UTC

We discussed it in the scrub and lowered severity.

Comment 2 Lukas Svaty 2017-10-11 12:06:31 UTC

Is this on track for 4.2?

Please add specification of the feature, what is the benefits of this and how to properly verify. Thank you

Comment 3 Yedidyah Bar David 2017-11-19 11:54:35 UTC

Implementing this bz requires:

1. Configuring apache to load mod_status, probably by adding a file to /etc/httpd/conf.d. We usually do this during engine-setup.

2. I think we want to limit access to the mod_status page, so that it's available by default to local host only.

3. If we decide to do this in engine-setup, we have to make sure that the metrics conf script will only enable the collectd plugin after httpd was configured. Alternatively, the metrics conf script can do everything.

Comment 4 Shirly Radco 2017-11-26 12:52:50 UTC

I think engine-setup would be a more proper way to load mod_status, since it requires the apache service restart.
Yaniv, Do you agree?

Comment 5 Yaniv Kaul 2017-11-28 19:30:08 UTC

(In reply to Shirly Radco from comment #4)
> I think engine-setup would be a more proper way to load mod_status, since it
> requires the apache service restart.
> Yaniv, Do you agree?

(Not sure why there's a needinfo on PM?)
LGTM - but it missed 4.2.0 - moving to 4.2.1.

Comment 6 Yaniv Kaul 2018-02-26 12:43:41 UTC

What value do we get from collecting Apache data (over what we already have in ovirt-requests-log) ? I'm sure there are small items (Kerberos authentication? etc.), not sure it's worth the effort (over what we already can get from ovirt-requests-log)

Comment 7 Shirly Radco 2018-03-05 11:10:30 UTC

Closing this base on Yaniv's comment #6. Will be fixed in Bug #1475897