[GEOS-11613] Increase control-flow logging admin visibility in logs #8045
Conversation
aaime
force-pushed
the
control_flow_logs
branch
from
82fd829
to
33a5103
Compare
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <!-- This log4j configuration file needs to stay here, and is used as the default logging setup --> | ||
| <!-- during data_dir upgrades and in case the chosen logging config isn't available. --> | ||
| <Configuration name="PRODUCTION_LOGGING" status="fatal" dest="out"> |
There was a problem hiding this comment.
Maybe a silly question: is it ok to have it named PRODUCTION_LOGGING or it would be better to name it CONTROL_FLOW_LOGGING?
There was a problem hiding this comment.
Don't think this shows up anywhere, but good point, best be consistent.
|
|
||
| In this example: | ||
|
|
||
| * A RateFlowController imposes a delay of 10 seconds on WPS andm WMS requests requests. |
There was a problem hiding this comment.
Isn't actually imposing a 1 second delay to the WMS request?
There was a problem hiding this comment.
Needs to be clarified... WPS Is delayed 10000ms while WMS only 1000ms
| * A concurrency control on wfs.getfeature with 8 requests is in place, with 3 executing. | ||
| * A global concurrency control with 50 requests is in place, with 3 executing. | ||
| * In summary, 3 requests are executing, and 12 are blocked. From this situation, they are queued on the single IP flow controller. | ||
| * Looking at the timings, this request has been delayed for about 13 seconds on the single IP flow controller. |
There was a problem hiding this comment.
I'm not very familiar with Control Flow:
why all the logs reports WFS 1.0.0 GetFeature? Is it because those details are reported when evaluating the status during that WFS getRequest?
There was a problem hiding this comment.
It's the same request being processed through all the configured controllers.
aaime
force-pushed
the
control_flow_logs
branch
from
33a5103
to
bd5892c
Compare
See ticket for details
Checklist
mainbranch (backports managed later; ignore for branch specific issues).For core and extension modules:
[GEOS-XYZWV] Title of the Jira ticket.