You've already got /tmp/lshttpd/.rtreport which is nice, we hook some stats into that... however, what I'd really love to see is a way to associate running external applications with their request information.
Something like:
{
external_pid: 1234,
start_time: 1471461438.423
user: litespeedrocks
virtual_host: litespeedtech.com
uri: /support/forum
peerAddr: 1.2.3.4
scriptHandler: php55
extProcessorName: lsphp5.5
(the more the merrier here imo: useragent, POST/GET)
}
... if there was some sort of array like 100 requests long that gets rotated out so you can see recent requests (including pending ones), that would be amazing as well.
... if you could provide web hosts with that information, it would make debugging customer web applications way nicer. As far as I know, there's no good way of looking up the information for a request that is currently being served. So we can come across an account where they've got back-end requests running for too long, but we have no way currently of knowing what triggered those application calls.
Anyway, if this sort of thing existed, it would be a priority for us to implement in our own interfaces because it would be sincerely helpful.
Thanks!!!
Something like:
{
external_pid: 1234,
start_time: 1471461438.423
user: litespeedrocks
virtual_host: litespeedtech.com
uri: /support/forum
peerAddr: 1.2.3.4
scriptHandler: php55
extProcessorName: lsphp5.5
(the more the merrier here imo: useragent, POST/GET)
}
... if there was some sort of array like 100 requests long that gets rotated out so you can see recent requests (including pending ones), that would be amazing as well.
... if you could provide web hosts with that information, it would make debugging customer web applications way nicer. As far as I know, there's no good way of looking up the information for a request that is currently being served. So we can come across an account where they've got back-end requests running for too long, but we have no way currently of knowing what triggered those application calls.
Anyway, if this sort of thing existed, it would be a priority for us to implement in our own interfaces because it would be sincerely helpful.
Thanks!!!