This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
uls:overview [2014-01-21 08:45] uls [Overview] |
uls:overview [2017-04-04 12:55] (current) uls [Agents] |
||
---|---|---|---|
Line 21: | Line 21: | ||
----- | ----- | ||
+ | |||
==== Values ==== | ==== Values ==== | ||
Line 26: | Line 27: | ||
* numerical values with units, e.g. disk usage ''75 %'' | * numerical values with units, e.g. disk usage ''75 %'' | ||
- | * text expressions up to 32000 characters, e.g. ''no error found'' | + | * utf8 based text expressions up to 32000 characters, e.g. ''no error found'' |
* tuple-timestamps, e.g. ''Start 2013-08-22 12:39:01'' and ''Stop 2013-08-22 12:44:17'' | * tuple-timestamps, e.g. ''Start 2013-08-22 12:39:01'' and ''Stop 2013-08-22 12:44:17'' | ||
* files, e.g. images, PDF documents or text files | * files, e.g. images, PDF documents or text files | ||
Line 32: | Line 33: | ||
Each value **must** belong to a timestamp (and some more parameters). | Each value **must** belong to a timestamp (and some more parameters). | ||
The default retention time of 14 days for values can be individually defined for each detail. | The default retention time of 14 days for values can be individually defined for each detail. | ||
+ | |||
+ | ----- | ||
==== Logical Data Structure ==== | ==== Logical Data Structure ==== | ||
Line 71: | Line 74: | ||
The hierarchical structure allows a drill-down style analysis of the values. | The hierarchical structure allows a drill-down style analysis of the values. | ||
+ | ----- | ||
==== Features ==== | ==== Features ==== | ||
Line 120: | Line 124: | ||
* define e-mail addresses as destination for notifications on threshold violations | * define e-mail addresses as destination for notifications on threshold violations | ||
* domain-wide threshold pattern with automatic applying | * domain-wide threshold pattern with automatic applying | ||
- | + | * define ULS-internal ticket tracking destinations for notifications on threshold violations | |
- | (new in version 1.7.0) | + | |
- | + | ||
- | * define ticket tracking destinations for notifications on threshold violations | + | |
All stored data is periodically checked: | All stored data is periodically checked: | ||
Line 132: | Line 133: | ||
=== Ticket Tracking === | === Ticket Tracking === | ||
- | |||
- | (new in version 1.7.0) | ||
Notifications of violated thresholds from ULS can be directed to the ULS Ticket Tracking (UTT). | Notifications of violated thresholds from ULS can be directed to the ULS Ticket Tracking (UTT). | ||
Line 205: | Line 204: | ||
* Solaris 8 system agent | * Solaris 8 system agent | ||
* Powershell scripts for W*ndows monitoring and event log scanning | * Powershell scripts for W*ndows monitoring and event log scanning | ||
- | * Oracle 9/10/11 (no RAC specifics) database monitoring | + | * Oracle 11/12 (no RAC specifics) database monitoring |
- | * Informix 9/10/11 database monitoring | + | * Informix 11/12 database monitoring |
See the [[uls:agents]]. | See the [[uls:agents]]. | ||
Line 215: | Line 214: | ||
* a linux-like operating system | * a linux-like operating system | ||
* a MySQL database | * a MySQL database | ||
- | * the ULS-server package provided in the [[uls:install]] | + | * the ULS-server package provided in [[uls:install]] |