Step by step instructions to Write Your First 360 Monitoring Plugin


First, you want to figure out where your 360 Monitoring modules are as of now introduced. To do as such, essentially execute the accompanying code:

agent360 info

Example output:

Version: 1.2.33

Plugins empowered: ping, well-suited refreshes, framework, iostat, httpd, loadavg, memory, mysql, nginx, diskusage, network, process, docker, central processor, swap

Plugins registry: /usr/neighborhood/lib/python3.7/dist-bundles/agent360/plugins

Server: 12354148123124

As depicted in the documentation for the modules, it will currently let you know the specific area. Following up, for my module I really want to make a record, which I have named in the given organizer (for example in the area found in the past advance).

Now basically open the document, glue the code and save it.

Before testing, we really want to ensure the client agent360 is permitted to get to the Plesk order line with sudo and without secret word. Along these lines we’re adding the accompanying line to/and so on/sudoers:

agent360 ALL=(ALL) NOPASSWD:/usr/sbin/plesk

To check the module is introduced and everything information can be gotten, run this code:

sudo - u agent360 agent360 test plesk-wpt

Now you ought to get a result with the genuine information. To at last actuate the module and ensure the information is accounted for in the 360 Monitoring framework, we really want to add the accompanying lines to/and so forth/agent360.ini:


empowered = yes

stretch = 600

This arrangement tells the agent360 not exclusively to begin utilizing the module yet to report the status each 600 seconds.

Once done, restart the observing service:

service agent360 restart



Please enter your comment!
Please enter your name here