Filtering out Test Event Connectors from the Database
I am trying to setup a scenario which works like this:
An Auditor comes into my environment and wants to check to see if my content is working. I need to generate events which will fire off all of our rules for each of our monitored applications without impacting the apps themselves.
The solution I have come up with was to use a test event connector and save .events files which will have the events I need in them. Run those events through ESM so that the Rule Fires can be seen.
However, I do not want for any of the events generated from my test connector to mess with our reports/trends, etc.
Is there a way for me to filter all data from that connector from being written to the database. I know there is a way to filter out some ArcSight internal events from being written to the database, but is there a way to do that from 1 specific connector.
Any help is appreciated.
Re: Filtering out Test Event Connectors from the Database
I don't think you can prevent them from being written to the database while at the same time firing the rules, but you could exclude that connector's events from reports and trends.
You could also set a storage rule to dump these events to a storage group with a one day retention period to keep them in the database for as short a time as possible.