Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Triggering Threshold Alarms

    Note that to trigger the threshold alarm, the corresponding collection (via the Task Manager or Traffic Collection Manager) should be scheduled on a recurring basis.

    • For CPUStats, the “mem” and “cpu” keys require scheduling. See Device SNMP Collection.
    • For LSPPingStats, the “lsp” keys require scheduling. See LSP Ping Collection.
    • For LatencyStats, the “latency” keys require scheduling. See Link Latency Collection.
    • For PingStats, the “ping” keys require scheduling. See Device Ping Collection.
    • For SLAStats, the “sla” keys require scheduling. See Device SLA Collection.
    • For the remainder of the keys in NodeScope, InterfaceScope, and TunnelScope, collection should be scheduled via the Traffic Collection Manager (see Performance Management: Traffic Collection Overview). The collection interval can be specified in the Collection Elements tab, for the given network (“Global Network” by default), in the “Traffic collection interval(s)” field.

    Modified: 2016-11-08