Return
-
Title
How to exclude a server that's being reported by the dmgr but not instrumented -
Description
How to exclude a server that's being reported by the dmgr but not instrumented
-
Resolution
In 5.5.x - model filtering takes care of this completely. i.e no data collected for the excluded server, as well as no false alarms etc.
in 5.6.x and 5.7.x , model filtering doesn't completely exclude incoming data. false alarms can be removed though.To exclude a server from the dmgr collection, update the agent_model-filters.config. Only that in 5.6.x this alone doesn't work (JEE-7140), and so we have an additional step.On 5.5.x
**********
{ "server": /^.*SERVER_NAME_TOBE_INCLUDED$/ }, "include",
{ "server": /.*/ }, "exclude",On 5.6.x or higher
**********************
a. model-filters.config
( { "server": /^.*SERVER_NAME_TOBE_INCLUDED$/ }, "include" ),
( { "server": /.*/ }, "exclude" ),b. agent_collector_websphere-discovery-runtime-6.config
…and towards the end of the file there is a includeTypes section, just remove the APPLICATION_SERVER line."@includeTypes" : (
"APPLICATION_SERVER",
"DEPLOYMENT_MANAGER"If only modifying the rules but not the data collected by the fms, adjust the rule scope to exclude particular objectsi.e. WebSphere Server State RuleWebSphereProcess where shouldCheckState='true' and monitoredHost != ws61test.quest.com