Description of problem: Viewing the Application dashboard will not show Metrics data while AdBlocking is enabled. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Install uBlockOrigin browser extension 2. View Application dashboard 3. Look for metrics data Actual results: No metrics data shown Expected results: Metrics data should not be blocked, since it's not an ad Additional info: The specific URL that's being blocked is "/metrics/metrics" by the EasyPrivacy blocking list: https://forums.lanik.us/ Many users browse with AdBlocking software enabled. They will assume the issue is on our end as they would not assume their AdBlocker would cause issues.
Changing the title unless we have proof that this affects more than one adblocker
The "EasyPrivacy" list can be added to other AdBlockers, I was able to test just now with AdBlock and AdBlock Plus. But uBlock Origin seems to be the only one in Chrome that enables this list by default.
I have opened a request with https://forums.lanik.us/ to see what our options are to get this unblocked. I am not sure what else we can do here. We could potentially change the route so that the "/hawkular/metrics" part of the url is no longer required. This would require changing the route and the URL in the master-config.yaml file. But this would also break anything else relying on the url to be formed like it is today, such as cloud forms. Since the alerts endpoint is under /hawkular/alerts, it would mean that we would have to create a new route for the alerts to work.
The upstream forum post to determine how to get our metric URLs unblocked: https://forums.lanik.us/viewtopic.php?f=64&t=35856
I don't know if we can get any progress with the upstream privacy blockers to get them to fix there filtering problem. A simple fix would be for Hawkular Metrics to alias the "/metrics" endpoint to be something like "/m". And then get the console team to update their code o that they use the aliased "/m" endpoint instead of the full "/metrics" one. Do we know what version(s) this needs to be fixed for exactly?
3.4 would be ideal, although 3.5 and forward is really the only need.
I am going to mark this as a duplicate of 1447405 which is already verified. *** This bug has been marked as a duplicate of bug 1447405 ***