Splunk AppDynamics

How to exclude EHCache from dashboard

CommunityUser
Splunk Employee
Splunk Employee

Each of our microservices uses an in-memory ehcache.  Appdynamics is showing an ehcache icon on the dashboard for each service and monitoring 'put' traffic.  This is not something we are interesting in seeing and it is clutter on the dashboard.

I had thought I would find EHCache listed in the 'Backend Detection' tab so that I can disable it but its not there.  Any hints on how to disable this monitoring?

Labels (1)
0 Karma
1 Solution

Arun_Dasetty
Super Champion

Hi howard Frost, 

Agent support many other OOTB interceptors listed below log message that are not part of backend detection and missing rules in UI is expected:

INFO ExitPointRuleApplier - Adding rules for exit point type [[SAP, Mail, LDAP, DangaMemcache, Coherence, EHCache, REDIS, MongoDB, Memcache]]

However you can update existing node property in UI below and add value as EHCache and see how it goes post saving changes in UI on target node/tier and check new load?

name: disable-custom-exit-points-for

Type: String

Value: EHCache

refer doc for to update node properties in UI  https://docs.appdynamics.com/display/PRO43/App+Agent+Node+Properties

If issue exists, share logs and while you share logs try below change in file app-agent-config.xml at path <AgenServerAgentt_install_Dir>/ver4.x.x.x/conf/app-agent-config.xml and add below entry under xml section and save changes and restart only node jvm process and see if exit call comes for new load in UI at node level: <bci-processing-excludes>.

<custom-exclude filter-type="STARTSWITH" filter-value="net/sf/ehcache/"/>

View solution in original post

0 Karma

Arun_Dasetty
Super Champion

Hi howard Frost, 

Agent support many other OOTB interceptors listed below log message that are not part of backend detection and missing rules in UI is expected:

INFO ExitPointRuleApplier - Adding rules for exit point type [[SAP, Mail, LDAP, DangaMemcache, Coherence, EHCache, REDIS, MongoDB, Memcache]]

However you can update existing node property in UI below and add value as EHCache and see how it goes post saving changes in UI on target node/tier and check new load?

name: disable-custom-exit-points-for

Type: String

Value: EHCache

refer doc for to update node properties in UI  https://docs.appdynamics.com/display/PRO43/App+Agent+Node+Properties

If issue exists, share logs and while you share logs try below change in file app-agent-config.xml at path <AgenServerAgentt_install_Dir>/ver4.x.x.x/conf/app-agent-config.xml and add below entry under xml section and save changes and restart only node jvm process and see if exit call comes for new load in UI at node level: <bci-processing-excludes>.

<custom-exclude filter-type="STARTSWITH" filter-value="net/sf/ehcache/"/>
0 Karma
Get Updates on the Splunk Community!

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 ...

Unleash Unified Security and Observability with Splunk Cloud Platform

     Now Available on Microsoft AzureOn Demand Now Step boldly into the AI revolution with enhanced security ...