...
The Aggregation agent publishes different MIM parameters depending on the storage selected in the Aggregation profile. For information about the MIM the MIM and a list of the general MIM parameters, see Administration and Management in Legacy Desktop.
...
MIM Parameter | Description |
---|---|
Created Session Count | This MIM parameter contains the number of sessions created.
You can reset the value by using |
Online Session Count | This MIM parameter contains the number of sessions cached in memory.
|
Session Cache Hit Count | When an already existing session is read from the cache instead of disk, a cache hit is counted. This MIM parameter contains the number of cache hits.
You can reset the value by using |
Session Cache Miss Count | When an already existing session is requested and the Aggregation profile cannot read the session information from the cache and instead reads the session information from disk, a cache miss is indicated. If a non-existing session is requested, this will not be counted as a cache miss. This MIM parameter contains the number of cache misses counted by the Aggregation profile.
You can reset the value by using |
Session Count | This MIM parameter contains the number of sessions in storage on the file system.
|
Couchbase Storage and Redis Storage
...
MIM Parameter | Description |
---|---|
Created Session Count | This MIM parameter contains the number of sessions created.
You can reset the value by using |
Online Session Count | For Elasticsearch, the value for this MIM parameter is always 0. This MIM parameter is retained for Elasticsearch to retain backwards compatitlity for workflows created with File Storage.
|
Session Cache Hit Count | When an already existing session is read from the cache instead of disk, a cache hit is counted. For Elasticsearch, the value for this MIM parameter is always 0. This MIM parameter is retained for Elasticsearch to retain backwards compatitlity for workflows created with File Storage.
You can reset the value by using |
Session Cache Miss Count | When an already existing session is requested and the Aggregation profile cannot read the session information from the cache and instead reads the session information from disk, a cache miss is indicated. If a non-existing session is requested, this will not be counted as a cache miss. For Elasticsearch, the value for this MIM parameter is always 0. This MIM parameter is retained for Elasticsearch to retain backwards compatitlity for workflows created with File Storage.
You can reset the value by using |
Session Count | This MIM parameter contains the number of sessions in storage on the file system.
|
...