Agent and modules generated by the plugin
- The plugin will create a global agent with the following modules:
| <Module prefix>.Datasources |
| <Module prefix>.Datasources count |
| <Module prefix>.Deployments |
| <Module prefix>.Deployments count |
| <Module prefix>.Threadpools |
| <Module prefix>.Threadpools count |
| <Module prefix>.committed.heap-memory-usage |
| <Module prefix>.committed.non-heap-memory-usage |
| <Module prefix>.committed.init.heap-memory-usage |
| <Module prefix>.committed.init.non-heap-memory-usage |
| <Module prefix>.max.heap-memory-usage |
| <Module prefix>.max.non-heap-memory-usage |
| <Module prefix>.used.heap-memory-usage |
| <Module prefix>.used.non-heap-memory-usage |
| <Module prefix>.committed.server.log |
In turn, if monitoring of these is enabled, it will create an agent for each :
| <Module prefix>.context-root |
| <Module prefix>.active-sessions |
| <Module prefix>.expired-sessions |
| <Module prefix>.highest-session-count |
| <Module prefix>.max-active-sessions |
| <Module prefix>.rejected-sessions |
| <Module prefix>.server |
| <Module prefix>.servlet |
| <Module prefix>.session-avg-alive-time |
| <Module prefix>.session-max-alive-time |
| <Module prefix>.sessions-created |
| <Module prefix>.virtual-host |
| <Module prefix>.websocket |
| <Module prefix>.<name thread>.active-count |
| <Module prefix>.<name thread>.completed-task-count |
| <Module prefix>.<name thread>.current-thread-count |
| <Module prefix>.<name thread>.keepalive-time |
| <Module prefix>.<name thread>.largest-thread-count |
| <Module prefix>.<name thread>.max-threads |
| <Module prefix>.<name thread>.queue-size |
| <Module prefix>.<name thread>.rejected-count |
| <Module prefix>.<name thread>.task-count |
It will create a boolean module, for each service, that will show whether it is True or False.