pasterassociates.blogg.se - What is ricoh agent

Monitoring → Dashboard → Problems widget (in popup window that opens when rolling the mouse over problem name|.

Tagging, if defined, can be seen with new events in: See also: Using macro functions in low-level discovery macros for event tagging. Tag name and value will be cut to 255 characters if their length exceeds 255 characters after macro resolution.

Define tags in the log trigger that will identify events using value extraction by the.

Identify problems in a log file and close them separately.

See all items tagged as 'MySQL' in Latest data by using the tag filter.

Define a tag on item level, for example 'MySQL'.

See how all problems of the host triggers are marked with these tags in Monitoring → Problems.

Define a tag on host level, for example 'Service=JIRA'.

See how those host problems that are created by triggers from this template are marked with these tags in Monitoring → Problems.

Define a tag on template level, for example 'App=MySQL'.See how all trigger problems are marked with these tags in Monitoring → Problems.Some use cases for this functionality are as follows: Similarly, a tag without value and the same tag with value can be used simultaneously. MySQL, Service:MySQL, Services, Services:Customer, Applications, Application:Java, Priority:HighĪn entity (template, host, item, web scenario, trigger or event) may be tagged with the same name, but different values - these tags will not be considered 'duplicates'. You can use only the name or pair it with a value: Tagging is realized as a pair of tag name and value. Item problems can be grouped based on tags. In other uses, actions can be defined based on tagged events. Importantly, events can be correlated based on event tags. Having custom event tags allows for more flexibility. Completely identical tag:value combinations (after resolved macros) are merged into one rather than being duplicated, when marking the event. with tagged triggers - any problem of this trigger will be markedĪ problem event inherits all tags from the whole chain of templates, hosts, items, web scenarios, triggers.with tagged items, web scenarios - any data/problem of this item or web scenario will be marked.with tagged hosts - any problem of the host will be marked.with tagged templates - any host problems created by relevant entities (items, triggers, etc) from this template will be marked.

If entities are tagged, the corresponding new events get marked accordingly: Tags have several uses, most notably, to mark events. There is an option to tag various entities in Zabbix.