Warning and error messages in the ITSI logs. Click a failed job to drill down to the logs. The number of failed jobs in the refresh queue. The refresh queue ensures data integrity and eventual consistency of your ITSI configuration. The number of searches that were not executed in the last hour. Lists names of saved search with error messages that include details about count, average run time, message key, and error messages. A headroom percentage close to 100 is best, and a value closer to 0 indicates a problem. The runtime headroom percentage indicates how much time has been used up out of the search's frequency. Any failed or skipped searches indicate a problem. If any search jobs are failed or not running, this could indicate a problem.īasic performance information for each KPI in your ITSI instance. itsi_mad_context and itsi_mad_cohesive_context handle metric anomaly detection and are stored in /SA-ITSI-MetricAD/local/nf once KPI anomaly detection is turned on. itsi_event_grouping handles event grouping for notable event aggregation policies and is stored in nf. For instructions, see Trim down notable event KV store collections in the Event Analytics manual. If a collection is approaching the limit, consider trimming it to retain three months or less of metadata. The number of KPIs using each base search.Īll ITSI KV store collections, the number of objects in each collection, acceleration information, and the collection size. Click Configure > Service Templates to see the current sync status of your service templates.įor each host, lists the number of services, searches, and entities, as well as KV store and HEC information. These versions should be the same.Ĭhecks whether any service templates are currently syncing. The current version of ITSI and the ITSI KV store. The ITSI Health Check dashboard provides basic statistics about your ITSI environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |