Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Coffee Break: Join us on Wednesday, April 5th at 10am PT to chat with Ben Gaines, Director of Product Management for Adobe Analytics. Ben will be online to answer your Analytics and Adobe Summit questions.

How to filter the AEM health checker (user agent Envoy/HC) from our stats?


Level 2

Anyone experience the AEM health checker artificially inflating their stats?


Out website traffic has significantly increase and upon further investigate, we're seeing the traffic is coming from the AEM Health Checker, using the user agent Envoy/HC. 

We've tried filtering the traffic with the bot rules, however the Health Checker isn't using a static IP address. 

Thanks in advance for any advice here.  

5 Replies


Community Advisor

Rather than using IP for your bot rule, could you not set up a rule based on User Agent contains?





Level 2

We set-up that exact bot rule, but it is not filtering the traffic. This is why we're so perplexed. 




Community Advisor

Hmm interesting... maybe case sensitivity? Maybe the / is causing issues?


I don't really use the Health Check, can you post the full user agent string that you have collected? 


Community Advisor

Wow... so it's not just "contains".. that's literally the entire string!


Have you tried contains "Envoy", that doesn't seem like it would show up in a lot of other user agents.... (this at least can check if the / is confusing things)


And you are sure that this data is coming into your tracking suite? Do you have an eVar set up to track the user agent that you can use to confirm..


The only other place you can get User Agent from your Adobe Data, that I am aware of, is your Raw Data feeds... but this you have to be careful of, since there is a special exclude data column and other processing that you need to take into consideration... and if you don't already have a process in place may not be a good option.


Or maybe you are confirming this simply by running in an isolated Dev environment and correlating the traffic in a Dev suite... I can see that what you sent is a server log, not from Adobe Analytics itself... so it's always a good idea to check everything 🙂

The ultimate experience is back.

Join us in Vegas to build skills, learn from the world's top brands, and be inspired.

Register Now