Bug 1425522

Summary: beakerd metrics queries should go to reports_engine if configured
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: generalAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact: Dan Callaghan <dcallagh>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: dcallagh, mjia, rjoost
Target Milestone: 24.1Keywords: FutureFeature, Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-28 16:50:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Callaghan 2017-02-21 16:15:32 UTC 
A while back we introduced a config option for an alternative database connection which is used for reporting queries: reports_engine.dburi and related directives in /etc/beaker/server.cfg.

The metrics queries which beakerd periodically runs are a good candidate to be sent to the reporting database, since they are quite expensive but can tolerate using slightly out of date data.

That will let us alleviate some load on the main DB in our production environment, by sending the metrics queries to the MySQL replica which we now have.
Comment 1 Dan Callaghan 2017-02-21 17:05:00 UTC 
https://gerrit.beaker-project.org/5644
Comment 5 Dan Callaghan 2017-02-28 16:50:42 UTC 
Beaker 24.1 has been released.