Copy ca.pem to /var/lib/dynatrace/remotepluginmodule/agent/conf/certificates on ActiveGate server
Restart the ActiveGate
Add ca.pem to credential vault as public certificate (two options are present, certificate and public certificate)
I went through the community thread but this extension was created using VScode and certificate exported via Visual studio (I used python to export the required certificates)
Thanks for sharing such case, I’d suggest checking the following points:
Ensure that the Dynatrace ActiveGate process has the necessary read/write permissions on the /var/lib/dynatrace/remotepluginmodule/agent/runtime/extensions directory and its contents.
Ensure that the extension is compatible with ActiveGate version, so kindly update the extension and ActiveGate to the latest supported versions.
Clear cached extension: through removing any potentially corrupted extension files in case you’re suspecting specific files in the extensions directory and attempt to reassign the monitoring configuration. You can achieve this through:
@erh_inetum, thank you for the response.
I’m using feature ‘custom extension creator’. Which I think, doesn’t require to upload the extension to tenant. Post generating developer.pem and adding ca.pem to cred vault and ActiveGate, we just have to deploy it from the extension creator page itself and it will start showing under hub page as self authored extension.
Adding screenshot below for information.
@Peter_Youssef, thank you for all the useful links. That gave me hint to resolve above mentioned issue. Restarting EEC (Extension execution controller) did work for me.
I’m using the same AG which were earlier used for another extension. Restarting EEC might have cleared the cache on AG, and it started working.
Regards,
AK
It’s my pleasure to contribute together till getting the raised concern sorted, Dynatrace documentation is a crucial pillar in troubleshooting activities.
EEC is playing a critical role specially in extensions.