ASM x DX integration should produce metrics/topology about destinations and certificate expiry
search cancel

ASM x DX integration should produce metrics/topology about destinations and certificate expiry

book

Article ID: 388652

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

For every monitor should create MONITOR_TARGET vertices, Eg:

For example, if MONITOR communicates with 4 HTTPS hosts (www.site.com, login.site.com, content.site.com, ads.partner.com) during execution, we should get 4 SYNTHETIC_MONITOR_TARGETS, one for each of those, that show details of those targets, including protocol, and potentially metric breakdowns by SYNTHETIC_MONITOR_TARGET

If any of those targets use a certificate-secured protocol (HTTPS, SFTP), we should have a METRIC associated with the MONITORING_TARGET of "Certificate Expiry (days)" with # of days remaining in the validity of the certificate, so that we can alert on any certificates that will expire in <10 days, for example.

If the monitor uses a client certificate, we should also add a metric for the certificate expiry of the client certificate, so that we can ensure that the monitor continues to work.

 

Environment

DX App Synthetic Monitor

DX O2 SaaS

Resolution

For now, we do not support it, an enhancement requested was already raised it, it will be evaluated and put in our backlog to be deployed soon.

To follow up on the status of this request, please raise a ticket on Broadcom Support Portal and refer to this knowledge article in order to get the status.