Am 29.08.2018 um 05:45 schrieb Rainer Jung:
Am 28.08.2018 um 15:54 schrieb Yann Ylavic:
On Tue, Aug 7, 2018 at 4:19 PM <rj...@apache.org> wrote:
Log:
Propose a few monitoring improvements.
Those changes look fine (and great) to me, I wanted to +1 but I'm
wondering if they really belong in 2.4.x since the output of
mod_status is changed in a way that could break existing parsers.
I don't know the "policy" here...
I have for now only applied the uncontroversial "auto" mode part of the
accepted patches to make at least some progress.
The "html" part is now back in STATUS (with adjusted smaller patches) to
give some more time for feedback whether the HTML output format is
allowed to change during a patch release (at least on a case by case
basis).
I have kept Jim's and your vote. Please adjust if you do not want the
HTML changes to get applied as well.
I don't know how to proceed. I committed the uncontroversial auto part,
but for the HTML part, as a response to Yann's question whether it would
be OK to change the format in a patch release there were responses from
- Eric, saying changing auto is OK
- Jim responding with +1 to Eric's feedback, but who had also voted +1
on the complete change including HTML
- Yann, originally raising the question but then deciding to give +1 on
auto plus HTML
So the question is probably whether Eric thinks keeping the HTML output
stable is more important than adding response duration info and proxy
busyness info. I'm open to any decision.
IMHO auto is in reasonable shape since at least 2.4.16 (r1674659,
released July 2015) so automated monitoring should really switch there
(and tolerate new and unknown keys).
Regards,
Rainer
