ActiveGate plugin FAQs

We provide you with a Plugin SDK free of charge. You don't need a special license to develop and deploy your own custom plugins. Alternatively, you can have one of the DESK partners develop the plugin for you, in which case your license fee depends on your contract. Whichever approach you take, after you successfully deploy and start using your plugin, you'll be charged for the custom metrics your plugin reports. For more information, see Custom metric ingestion and analysis.

DESK doesn't propagate ActiveGate plugins automatically. You need to upload the plugin package to DESK Server and to each ActiveGate you want to run it on. Each plugin should be placed unpacked in its own folder in plugin_deployment directory in the installation directory. By default, /opt/DESK/remotepluginmodule/plugin_deployment on Linux or C:\Program Files\DESK\remotepluginmodule\plugin_deployment on Windows.

Remember, you have to upload the plugin to each ActiveGate that will run it and your DESK Server.

For more information, see Deploy an ActiveGate plugin

Open the Process Group details view of a technology, expand Properties section and look for the technology in the Main technology property. Add this value to technologies field in your plugin.json file. For more information, see plugin metadata in json file

The plugin logs are saved by default in
/var/lib/DESK/remotepluginmodule/log/remoteplugin on Linux or
C:\ProgramData\DESK\remotepluginmodule\log\remoteplugin on Windows

For more information, see logging.

To start plugin development you need to install python3, pip3 and pluginSDK. For more information, see ActiveGate plugins hands-on

See External libraries.