An AppDynamics extension that monitors the SSL certificates for configurable domains and should be used with a stand alone Java Machine Agent.
Note : Please make sure to not use tab (\t) while editing yaml files. You may want to validate the yaml file using a yaml validator http://yamllint.com/
1. Edit the file config.yml located at
<MachineAgent_Dir>/monitors/SslCertificateMonitor The metricPrefix of the extension has to be configured as specified here. Please make sure that the right metricPrefix is chosen based on your machine agent deployment, otherwise this could lead to metrics not being visible in the controller.
2. Configure the domains in config.yml file.
#This will create this metric in all the tiers, under this path metricPrefix: "Custom Metrics|SslCertificate" #This will create it in specific Tier. Replace
#metricPrefix: Server|Component: |Custom Metrics|SslCertificate domains: - domain: "www.google.com" port: 443 displayName: "Google" - domain: "www.ebay.com" port: 443 displayName: "eBay" - domain: "www.amazon.com" port: 443 displayName: "amazon" # Point to .sh for unix based and .bat for windows. # Incase if you are using Cygwin's openssl, please make sure to change the openssl.bat to point to Cygwin's openssl. # For eg. echo | C:\Cygwin64\bin\openssl s_client -connect %1:%2 2> null | C:\Cygwin64\bin\openssl x509 -noout -enddate cmdFile: "monitors/SslCertificateMonitor/cmd/openssl.sh" #cmdFile: "monitors\\SslCertificateMonitor\\cmd\\openssl.bat" #### Configurations below this need not be changed.### # number of concurrent tasks numberOfThreads: 10 #timeout for the thread threadTimeout: 5
3. Configure the path to the config.yml file by editing the in the monitor.xml file in the
<MACHINE_AGENT_HOME>/monitors/SslCertificateMonitor/ directory. You can also change the frequency at which the MachineAgent calls the extension by changing the <execution-frequency-in-seconds> in monitor.xml.
4. If needed, configure the openssl command in the cmdFile pointed by config.yml.
Always feel free to fork and contribute any changes directly via GitHub.
Find out more in the AppDynamics Exchange.
For any questions or feature request, please contact firstname.lastname@example.org.