I want to know if it is possible to simply perform a ping to a device that does not have OneAgent installed? I don't know if it is possible using a Dynatrace plugin or maybe there is a possibility to create my own plugin to do this?
Thank you in advance
Solved! Go to Solution.
I've built a simple ActiveGate plugin to ping devices (measures response time and availability). It creates custom devices. Works quite well for many devices.
As I mentioned in my earlier comment, at the moment no external pings can be done with plugins. This is planned for early next year and will allow you to execute plugins towards targets that cannot be instrumented with a OneAgent. In a first iteration this could allow us to have support for known devices such as an F5. Later-on that can be extended.
You can also perform the pings outside Dynatrace environment and just send the availability/performance data into Dynatrace using API. More details here:
However the execution itself is up to you.
We actually attend a HOT Day training session where we used a Dynatrace Plugin from an activegate to run Port pings. SO it is possible from within Dynatrace to do pings, we pinged a website, not sure if you can apply the same method to a device
Hi @Julius L. Are you able to share the activegate plugin?
One of our clients has not requested this, for web monitoring we use http monitor, but we want to reach the devices.
There is in Dynatrace Hub a synthetic monitor ping that you can use.
Just some additional two cents on this: the extensibility of Dynatrace is very good, and in our case we have even built an extension that pings with 1 second resolution, enabling the possibility of having strong network SLA measuring, in both latency & availability. I'm in the process of trying to solve a dependency issue, to make it available.
Anyone ever run into the error "Configuration error(Extension doesn't exist on given host)", in spite of the presence of custom.remote.python.thirdparty_ping in the ../remotepluginmodule/plugin_deployment directory on the ActiveGate selected on the Settings >> Monitoring >> Monitored technologies >> Ping configuration page?
It's usually one of three things (in order of commonality):
1. The package was unzipped incorrectly in the plugin_deployment folder, causing a nested folder structure.
2. The dtuserag (for Linux) does not have access to the files.
3. Another extension on the same ActiveGate has a conflicting dependency. This can be seen in the remote plugin agent log. Splitting it up over two AG's is the easiest fix.