Are you a member of the Splunk Community?
- Find Answers
- :
- Splunk Platform
- :
- Splunk AppDynamics
- :
- How to exclude EHCache from dashboard
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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/ 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/"/>
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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/ 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/"/>
Fastest way to demo Observability
September Community Champions: A Shoutout to Our Contributors!
Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps
