Unable to whitelist/blacklist nodejs autoattach independently from Java autoattach

Products

• DX SaaS

Issue/Introduction

We are currently blacklisting UMA Java auto-attach in the same cluster to ensure that all containerized Java deployments are monitored.

Unfortunately both nodejs auto-attach and Java auto-attach leverage the exact same whitelist/blacklist setting i.e. 

monitor:

  application:

    autoattach:

      filterType: whitelist

Ideally, nodejs and java (and any other type of auto-attach style instrumentation) would have the ability to be blacklisted or whitelisted independently from one another.

Resolution

ER defect created for view .

Additional Information

To sum up, what the customer is looking for is to have UMA autoattach supporting whitelist/blacklist configuration similar to below:

 

monitor:

  application:

    autoattach:

      filterType: whitelist

      java: 

        enabled: true

        filterType: blacklist

      dotnet: 

        enabled: false

        #default to the filterType setting from the general level above if not explicitly specified at this level: whtelist

      nodejs: 

        enabled: true

        filterType: whitelist

 

instead of the existing implementation to allow only one filterType setting to be used for all different application types:

 

monitor:

  application:

    autoattach:

      filterType: whitelist

      java: 

        enabled: true

      dotnet: 

        enabled: false

      nodejs: 

        enabled: true