This is an automated email from the ASF dual-hosted git repository.
remm pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/9.0.x by this push:
new d0a80ec2ee Improve status manager information
d0a80ec2ee is described below
commit d0a80ec2ee5e5e93a77885e5e0469c1bbd322ba1
Author: remm <[email protected]>
AuthorDate: Thu Nov 21 10:16:44 2024 +0100
Improve status manager information
---
webapps/docs/manager-howto.xml | 23 +++++++++++++++--------
1 file changed, 15 insertions(+), 8 deletions(-)
diff --git a/webapps/docs/manager-howto.xml b/webapps/docs/manager-howto.xml
index 54d5f4d7f0..f9ede9ddab 100644
--- a/webapps/docs/manager-howto.xml
+++ b/webapps/docs/manager-howto.xml
@@ -1044,22 +1044,27 @@
href="config/listeners.html#StoreConfig_Lifecycle_Listener_-_org.apache.catalina
<section name="Server Status">
<p>From the following links you can view Status information about the server.
-Any one of <strong>manager-xxx</strong> roles allows access to this page.</p>
+The <code>manager-status</code> role or any one of the other
+<strong>manager-xxx</strong> roles allow access to this page.</p>
<source>http://localhost:8080/manager/status
http://localhost:8080/manager/status/all</source>
<p>Displays server status information in HTML format.</p>
-<source>http://localhost:8080/manager/status?XML=true
-http://localhost:8080/manager/status/all?XML=true</source>
+<source>http://localhost:8080/manager/status?XML=true</source>
-<p>Displays server status information in XML format.</p>
+<p>Displays server status information in XML format. The XML format does
+not include the detailed per web application statistics.</p>
<source>http://localhost:8080/manager/status?JSON=true
http://localhost:8080/manager/status/all?JSON=true</source>
-<p>Displays server status information in JSON format.</p>
+<p>Displays server status information in JSON format. The JSON format does
+not include the per thread state information. If using a client visualization
+tool for active monitoring and server status alerts (such as Grafana), the JSON
+output provided by the Manager will likely provide the easiest and most secure
+solution.</p>
<p>First, you have the server and JVM version number, JVM provider, OS name
and number followed by the architecture type.</p>
@@ -1074,8 +1079,9 @@ The same information is available for both of them :
current thread count and current thread busy.</p></li>
<li><p>Request information : Max processing time and processing time,
request and error count, bytes received and sent.</p></li>
- <li><p>A table showing Stage, Time, Bytes Sent, Bytes Receive, Client,
- VHost and Request. All existing threads are listed in the table.
+ <li><p>If not using the JSON format, the state of threads with Stage,
+ Time, Bytes Sent, Bytes Receive, Client, VHost and Request.
+ All existing threads are listed in the table.
Here is the list of the possible thread stages :</p>
<ul>
<li><p><em>"Parse and Prepare Request"</em> : The request headers are
@@ -1102,7 +1108,8 @@ The same information is available for both of them :
</ul>
<p>If you are using <code>/status/all</code> command, additional information
-on each of deployed web applications will be available.</p>
+on each of deployed web applications will be available, except for the XML
+format.</p>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
