Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
For security reasons such as,how to block the view of JVM variables in appdynamics console.
a different way to block, other than through config with agent.
through sensitive-data-filter and app-agent-config.xml.
I understand that you you need to control access to JVM-specific monitoring parameters at a controller UI-level. Is this correct?
I'm afraid that our access control does not provide this level of granularity. Here you can see what permissions can be configured: https://docs.appdynamics.com/accounts/appdynamics-saas-deployment-user-management/manage-custom-role...
When mentioning about the agent config, did you refer to the capability documented below?
I’m just wondering why actually do you want to do the filtering in another way... Do you need to control the access on a per-user basis or perhaps the agent configuration doesn’t provide the right granularity of filtering?
Also, do you use AppD on-prem or SaaS controller?