24 Oct 2022
10:27 AM
- last edited on
25 Oct 2022
12:59 AM
by
MaciejNeumann
This post presents detailed instructions on how to install and configure the Ping Every Second extension. This extension enables you to monitor network latency, involving the use of ping, with a one second resolution.
The extension is available for download at https://github.com/MarketWare-EU/ping-every-second
Configuration begins by filling a set of requirements on the ActiveGate. At the moment, this extension is only available for Linux ActiveGates. Naturally, the ActiveGate will need to be able to communicate with the desired endpoints to be monitored with the system ping command.
On the ActiveGate machine, a ping command needs to be executed. This command needs to be executed for each and every one of the IPs to monitor. As can be seen below, besides specifying the destination for the ping command, you also have to exactly put the same IP in the name of the output file, in this case, the /tmp/dyna_<ip> file. An example for an hypothetical monitoring for IP 1.1.1.1:
The ActiveGate process needs read and write permission on files /tmp/dyna_<ip>.
Typically, the user is dtuserag, so the following example command should suffice (execute after the command above):
As can be observed, the first command (nohup ping) was executed with the options:
The ActiveGate extension, each minute, copies the /tmp/dyna_<ip> file to a /tmp/dyna1_<ip>file, and truncates the original file. It then processes the copied file and sends data to Dynatrace. The file will exist for one minute, until the next processing is done. At the moment, you have to guarantee that if the ping process dies, or the system restarts, the ping command is run again. The ping command is used as it doesn't require special privileges to run.
After the ping is running, upload the .ZIP extension to the Dynatrace platform. Detailed instructions on this process can be found here: https://www.dynatrace.com/support/help/extend-dynatrace/extensions/development/extension-how-tos/dep...
After that, the extension's UI configurations are visible. The needed fields to fill are:
Data is available through the “Metrics”/"Data explorer" menu. The following metrics are available at the moment (all values are averaged when aggregated):
There are some known caveats or missing functionality:
We have some ideas that we will be developing next and sharing here. If you need help in using it, please comment here.
Attaching a Dashboard JSON file, that can be used to visualize data for this extension. It's a TXT, but just upload it's content into Dynatrace dashboard.
Featured Posts