No data arriving
Your Bot Activity report is empty, or the status line still says Log Hero is waiting for the first hits for this domain. Work through these four checks in order — they are ordered by how often each one turns out to be the cause.
1. Has enough time passed?
Section titled “1. Has enough time passed?”Bot traffic is not continuous. A small site may go several hours between crawler visits, and Logpush and other edge integrations batch records before sending.
- Origin integrations (WordPress, Apache, PHP): first hits within minutes.
- Edge integrations (Cloudflare, CloudFront, Azure Front Door, Fastly): allow up to an hour.
If it has been less than an hour, wait before changing anything.
2. Is the integration actually running?
Section titled “2. Is the integration actually running?”Check the integration’s own status before suspecting Log Hero:
| Integration | Where to look | What good looks like |
|---|---|---|
| WordPress | Settings → LogHero | An API key is saved, and no warning notice in the backend |
| Apache | apachectl -M |
The Log Hero module is listed as loaded |
| PHP SDK | Application error log | No Log Hero exceptions on recent requests |
| Cloudflare | Analytics & Logs → Logpush | Job status is Active, not Error |
| Amazon CloudFront | CloudFormation, us-east-1, stack LogHero-CloudFront |
Status is CREATE_COMPLETE, and the FirehoseLogGroupName output is empty |
| Fastly | Active version → Logging | An endpoint named loghero is listed, and the Error Stream is empty |
| Azure Front Door | Front Door profile → Diagnostic settings, and the Event Hub → Metrics | loghero-forward-to-eventhub is listed, and Outgoing Messages keeps pace with Incoming Messages |
Two failures are common enough to have their own pages: Asynchronous flush failed and Permission denied.
3. Does the domain match?
Section titled “3. Does the domain match?”Log Hero attributes hits by hostname. A mismatch means the requests arrive but land nowhere.
- The domain in Log Hero is
example.com, but the site serveswww.example.com— or the reverse. - The integration is installed on a staging hostname.
- The site serves several hostnames and only one is registered.
Compare the domain shown in Log Hero against the hostname in your browser’s address bar, character for character.
4. Is something blocking the bots before they are logged?
Section titled “4. Is something blocking the bots before they are logged?”If the integration is healthy and the domain matches, the requests may not be reaching the point where they get logged at all.
- A WAF or bot-mitigation rule. Cloudflare Bot Fight Mode, a rate limit or a security rule can drop AI crawlers before Logpush records them.
robots.txt. ADisallowfor a well-behaved crawler means it stops requesting your pages. It is not a Log Hero problem — the traffic genuinely is not there.- Full-page caching in front of the integration. An origin-side plugin never sees a request answered by a cache above it. Move to the edge integration for your CDN.
Still nothing?
Section titled “Still nothing?”Send the following to support@log-hero.com and we can trace it from our side:
- The domain as registered in Log Hero
- The integration and its version
- What the integration’s own status page reports
- Roughly when it was installed