- What are triggered traceroutes
- When they are triggered
- What are the special triggered traceroute settings
What you are going to learn:
Triggered traceroutes, as the name suggests, are triggered when an network event occurs. The objective of these traceroutes is to catch the issue when it occurs to help with troubleshooting. This is very useful for intermittent network issues that are hard to catch with Live Traceroutes.
The triggered traceroutes are triggered when network events occur, such as:
- Session Down
- Packet Loss
- Higher Latency
- Higher Jitter
As an example, if a packet loss event is raised because the packet loss is over the Network Monitoring Thresholds, both monitoring agents involved in the monitoring session will launch a traceroute. When completed, the traceroute will be sent to the cloud and it will be available in the network monitoring session page with the tag
It is possible to launch a live traceroute even if a triggered traceroute is being executed without problems. They are completely separate and they don't need to have the same traceroute settings.
The traceroutes settings can't be changed for the triggered traceroutes. Below are the values for each setting. Refer to the Traceroutes for the setting details.
Hostname + IP
- Max TTL:
- Packet Size:
- ToS: Session TOS/DSCP Value
Each monitoring agent has a
Concurrent Triggered Traceroutes setting that sets the number of concurrent triggered traceroutes that can be executed. The default value is
5. It can not be changed in the App yet, but our Support Team can change it for you if needed.
When a monitoring agent wants to launch a new triggered traceroute, it validates the number of running triggered traceroutes with the concurrent value explained above. If the concurrent limit has been reached, the triggered traceroute is queued for a maximum amount of time. That time is defined by the
Triggered Traceroute Timeout with a default value of
5 minutes. This means that if a triggered traceroute stays in the queue for more than 5 minutes, when the agent will be ready to execute it, it will silently discard it.
For each network monitoring session on a monitoring agent, there is a timer that defines the minimum time between two triggered traceroutes on the session. The timer is defined by the
Triggered Traceroute Pause Timer with a default value of
5 minutes. This means that if a triggered traceroute needs to be launch but that another triggered traceroute for the exact same session has been done 5 minutes ago, the new triggered traceroute will be silently ignored.
A full article about the benefits of our Triggered Traceroutes feature is available on our Blog: Triggered Traceroutes Feature & How it Works.