Splunk AppDynamics

action: VIEW_DBMON_UI

Sundarapandian_
Path Finder

Hello,

we repeatedly see the following error in or server.log. Can someone please help to understand what is "action: VIEW_DBMON_UI entity: APPLICATION 1" in this error, and also if we could restrict this operation for a specific user or a group ?

I also couldn't see much information in audit.log for the specific user. Are there any docs that explains different actions? 

Sample:

[#|2018-08-06T17:49:50.976-0500|SEVERE|glassfish 4.1|com.singularity.ee.controller.beans.ExceptionHandlingInterceptor|_ThreadID=266;_ThreadName=http-listener-1(21);_TimeMillis=1533595790976;_LevelValue=1000;|Encountered a permission exception; permission=[VIEW_DBMON_UI]; affected entity=[Type:APPLICATION, id:1]
com.singularity.ee.controller.api.exceptions.PermissionException: The current user 'xxxxxxx' does not have permission to do this.  (action: VIEW_DBMON_UI entity: APPLICATION 1)
        at com.singularity.ee.controller.beans.manage.permissions.PermissionsManager.isNotPermitted(PermissionsManager.java:352)
        at com.singularity.ee.controller.beans.manage.permissions.PermissionsManager.checkPermission(PermissionsManager.java:311)
        at com.appdynamics.platform.persistence.TransactionInterceptor$1.call(TransactionInterceptor.java:30)
        at com.singularity.ee.controller.beans.model.EJBManagerBean.runWithinSupportsTransaction(EJBManagerBean.java:58)
        at sun.reflect.GeneratedMethodAccessor306.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.glassfish.ejb.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1081)
        at org.glassfish.ejb.security.application.EJBSecurityManager.invoke(EJBSecurityManager.java:1153)
        at com.sun.ejb.containers.BaseContainer.invokeBeanMethod(BaseContainer.java:4786)
        at com.sun.ejb.EjbInvocation.invokeBeanMethod(EjbInvocation.java:656)
        at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:824)
        at com.sun.ejb.EjbInvocation.proceed(EjbInvocation.java:608)
        at com.singularity.ee.controller.beans.EntityManagerInterceptor.manageEntityManagerLifecycle(EntityManagerInterceptor.java:57)
        at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:883)
        at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:823)

Would appreciate any swift response on this...

Warm regards,

Sundar

Labels (3)
0 Karma

Yogesh_Chouk
Builder

Hi Sundar,

The error which you are seeing is because the user is trying to access the database monitoring page when it is not having enough permission to view. Do you see any functionality issue here? If not, you can ignore this as it is just a permission related error.

Also, please let me know the controller version you are using.

Thanks,

Yogesh

0 Karma

Sundarapandian_
Path Finder

Hi Yogesh,

Controller version is 4.3.8.0

-Sundar

0 Karma
Get Updates on the Splunk Community!

Best Strategies to Optimize Observability Costs

 Join us on Tuesday, May 6, 2025, at 11 AM PDT / 2 PM EDT for an insightful session on optimizing ...

Fueling your curiosity with new Splunk ILT and eLearning courses

At Splunk Education, we’re driven by curiosity—both ours and yours! That’s why we’re committed to delivering ...

Splunk AI Assistant for SPL 1.1.0 | Now Personalized to Your Environment for Greater ...

Splunk AI Assistant for SPL has transformed how users interact with Splunk, making it easier than ever to ...