Device Type: ServerView Platform
Glossary: TraceRoute Task
How to create devices and tasks
- Add a New Task to an Existing Device
- Create/Edit a single Device with a single task
- Create/Edit several Tasks within a single Device
How to Edit an TraceRoute Task
Once you have created a device and are adding or editing an TraceRoute Task, you will be prompted to adjust the following settings:
Task Name: Provide a descriptive name for the task so that you would be able to identify the task later among a list of similar tasks. For example, “www.example.com Traceroute 15 minute”.
Maximum Connection Timeout (in Milliseconds) Enter the number of seconds the task should wait for a response from the web page before aborting the task and returning an error. If this is left blank the default timeout for a task is 120 seconds.
Host: enter the server address to be monitored. This could be the URL or the IP address.
Ignore Protocol Errors: Selecting no will cause the task to error every time any node along the path to the host returns an error. It is quite common that any given traceroute request will return one or more timeouts from a node along the path. This does not mean that the request failed, simply that the node took too long to respond and the request was resent. Therefore, you may receive multiple request timeouts but the task will still complete the full traceroute.
Because of this, we recommend that you select yes when setting up an ongoing monitor, otherwise your reports may appear to contain many more errors from nodes outside of your control, even if the node responded to a second or third request.
DNS Options: are explained in detail in “DNS Mode Option” article.