topic Help configuring SSL Certificate Monitor Extension in Extensions

Help configuring SSL Certificate Monitor Extension

Raidan — Fri, 23 Jan 2026 07:28:03 GMT

Hi All,

I installed the SSL Certificate Monitor extension so I can monitor certificates in Dynatrace. I activated it at the ActiveGate scope and added the domain for direct monitoring, but I still can’t see any data in Dynatrace.

I also checked the Defender Portal and confirmed the certificate details are correct.

Do you have any suggestions on what I should check next?

Thanks

Re: Help configuring SSL Certificate Monitor Extension

AntonPineiro — Thu, 22 Jan 2026 13:42:31 GMT

Hi,

I would suggest checking ActiveGate extension logs.

Best regards

Re: Help configuring SSL Certificate Monitor Extension

Raidan — Mon, 26 Jan 2026 12:53:15 GMT

I checked the ActiveGate and extension logs on the ActiveGate host. The ActiveGate is running fine and the SSL Certificate Monitor extension is executing regularly.

I don’t see any errors in the logs, but no certificates are discovered and no data appears in Dynatrace.

The certificates do exist and are in use (confirmed in Microsoft Defender), and (I'm not sure )they are used by Kubernetes ingress endpoints.

Re: Help configuring SSL Certificate Monitor Extension

AntonPineiro — Mon, 26 Jan 2026 13:39:33 GMT

Hi,

I would open a support case with ActiveGate diagnostics attached.

Best regards

Re: Help configuring SSL Certificate Monitor Extension

t_pawlak — Mon, 26 Jan 2026 18:00:47 GMT

Hi,
I know this might be trivial, but it often happens that the ActiveGate can’t establish a TLS connection to the target domain/URL. You know, DNS, routing,firewall, proxy. Or, if you try reach kubernetess Ingress you can hitting the wrong certificate because SNI isn’t applied correctly
SSL Certificate Monitor extension
in this documentation Dynatrace explicitly notes that for remote monitoring the ActiveGate must have access to the provided URLs/domains and firewall/network changes may be required.

Test from the ActiveGate host do something like that nslookup your.domain or openssl s_client -connect your.domain:443 -servername your.domain </dev/null 2>/dev/null | openssl x509 -noout -subject -issuer -dates or just curl -vkI https://your.domain

It could be also SNI for Kubernetes Ingress - in documentation

Additional SNI domains An optional setting to configure additional Server Name Indication domains: Add domain. An advanced setting to provide a list of domains to use in with Server Name Indication. SNI is an extension to the TLS protocol which is used in HTTPS. Use this setting to specify the domain name of a website during the initial TLS Handshake instead of when the HTTPS connection opens after the handshake.

when multiple hostnames/certs share the same IP/LB; otherwise you may get the default cert or fail to extract the expected one. Also check that you monitor correct FQDN used by the Ingress.

Another option - Enable the certificate status metric

You can also Enable debug + domain discovery error alerts
From documentation:

Activate debug—check this box to activate debug level logging. Logs are available (by default) on Linux at: /var/lib/dynatrace/remotepluginmodule/log/extensions/datasources and on Windows at: C:\ProgramData\dynatrace\remotepluginmodule\log\extensions\datasources.

If all this checks look fine open a support ticket