Reporter data overage issues

[#1]

We are running into problems keeping our reporting data usage under our current license limit. We recently increased our limit to try to keep reporting alive but we are still having problems. Has anyone had success tuning reporting to keep this data usage below a threshold? I can't find any information on how to find out exactly what bit(s) are eating our data up or how to effectivly adjust the reporter to account for that.

We have spooled up the Data Connector in a VM, and are using FQDN ETL filter to remove superfluous/internal information and that appeared to help for a little while and then our data went back up.

We've adjusted the Data Indexing to bare minimum, to no avail.

Adding the same domains that were in our ETL filter on the Data Connector to the "Exclude the following Domains" dialog in Grid DNS properties/logging/advanced seems to have made a difference but shouldn't the data connector be filtering them already?

I'm at a complete loss, any suggestions would be greatly appreciated!

[#2]

Hi Sean, 

I have the same situation, after opening a case, I was informed that is a RFE number is RFE-13074 regarding this but the RFE is still Under Consideration state. My sugestion is who has the same situation, should open a case asking to include your customer into this RFE so they can maybe consider more this.

[#3]

We ended up cancelling our reporting license and using ElasticSearch to colate the data we needed from our data connector. Maybe if enough people hit them in the pocketbook this way it will help expidite some change.