
250
Sentinel 6.1 User Guide
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
The information is divided into 3 sections:
Requests
Services
ThreadPools
Under Requests it keeps all the requests by channel (such as services.CorrelationService). Under
services it does the same by service. Sometimes it provides a breakdown by appending
“<category>” under the name, such as Services.CorrelationService or
Services.RemoteObjectService.EMap.getMapPK.
Under Services, all the remote method calls from user defined services (your XML services) are all
under services.RemoteObjectService. Under that it puts the name of the service (EMap) in the above
example and if asked, the name of the method (getMapPK in the above).
When a request is received by a server, such as DAS Query, a task is created and scheduled. The task
is then assigned to a thread pool for execution. There can be more than one thread pool and a thread
pool can service multiple services. For that reason, a request needs to wait for an available thread
even if the service is not heavily used. If the statistics indicate that the wait time for a request is large
and the number of requests for that service is low, check the information about the thread pools.
The numbers next to an entry are the sum for all its children. So requests 15 means that there are 15
requests for all requests method calls. Under that, requests.configurations 1 means that 1 of the 15
are to configurations, requests.esecurity.correlation.config 2 means that 2 of the 15 are to
esecurity.correlation.config and so on.
Figure 11-9
Das Statistics window
The information can be useful because it shows what is going on. The number of requests is
especially useful, you can see where they are all going or concentrated. The #waiting is useful
because it shows how busy the server is. That number should be small. If it is large, new requests
(even for simple tasks) will need to wait for potentially slow ones. This is not a good situation. The
average run time is very important because it shows which requests are actually taking all the time,
as opposed to waiting for others.
Содержание SENTINEL 6.1 SP2
Страница 4: ...4 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 20: ...20 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 34: ...34 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 57: ...Active Views Tab 57 novdocx en 7 January 2010 Figure 2 7 Organic View Figure 2 8 Hierarchical View ...
Страница 97: ...Incidents Tab 97 novdocx en 7 January 2010 Sort By You can set rules to sort the incidents in the display view ...
Страница 116: ...116 Sentinel 6 1 User Guide novdocx en 7 January 2010 Integer Variable String Variable ...
Страница 146: ...146 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 172: ...172 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 178: ...178 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 280: ...280 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 306: ...306 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 329: ...Quick Start 329 novdocx en 7 January 2010 ...
Страница 330: ...330 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 401: ...Sentinel Link Solution 401 novdocx en 7 January 2010 3 Select the Novell Sentinel Link Collector then click Next ...
Страница 405: ...Sentinel Link Solution 405 novdocx en 7 January 2010 6 In the Configure Connector window specify the following ...
Страница 412: ...412 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 430: ...430 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 440: ...440 Sentinel 6 1 User Guide novdocx en 7 January 2010 Figure 18 3 Reports ...
Страница 528: ...528 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...