If you’re managing a WordPress site – or a handful of them – you already know that things happen. A plugin gets updated without warning. An admin account you don’t recognise shows up. A page that was definitely published yesterday is suddenly a draft again. WordPress is a busy place, and not everything that happens there is obvious at first glance.
That’s why activity logging exists. Every login, every content change, every settings tweak – recorded, timestamped, attributed to a user. It’s the audit trail that answers the question: what changed right before things broke?
But here’s something I kept running into: for a lot of developers and teams, WordPress is not where they live. Their business monitoring lives in Datadog. Their business alerts live in Datadog. Dashboards, incidents, on-call routines – all of it in Datadog. And their WordPress logs? Sitting quietly in a WordPress admin panel, completely disconnected from everything else.
That gap bothered me.
The story that made it obvious
I was working with an agency managing around a dozen client sites. One Friday afternoon, a client calls – their site is down. The developer jumps into WordPress, checks the activity log, and sees it immediately: a plugin was deactivated about 20 minutes before the outage. Mystery solved in under a minute. Good outcome.
But then came the question nobody loves in a post-mortem: why didn’t we catch this sooner?
The team had alerts and dashboards for everything else in their stack. Uptime monitoring. Error tracking. Infrastructure metrics. All of it flowing into Datadog. But the WordPress layer – user activity, plugin changes, admin actions – was invisible from there. It only surfaced when someone remembered to go look.
That’s not a logging problem. That’s a visibility problem.
What “Log Channels” actually means
The idea behind Log Channels is simple: your WordPress activity log shouldn’t be stuck inside WordPress.
With Log Channels – a Premium feature in Activity Log Pro – every event your site records gets forwarded in real time to wherever your team already works. In this case, Datadog.
Each log entry arrives tagged with your site name and URL automatically. So if you’re managing more than one site, you can filter, search, and build alerts across all of them from inside Datadog. No switching between WordPress admin panels. No manual exports. Your WordPress events, living alongside everything else in your existing logging stack.
And because log delivery runs asynchronously in the background, your site does not wait on Datadog or any other destination—visitors and admins should not feel a slowdown; it just flows in the background. With Log Channels, your WordPress activity log becomes part of a broader logging and observability workflow – not just a standalone dashboard.
Why Datadog specifically makes sense here
Datadog is used by thousands of engineering and DevOps teams to monitor infrastructure, applications, and services. If your team is already there, the case for also pulling in WordPress events is pretty straightforward.
One place to investigate. When something goes wrong, you want the full picture in one place – not half the story in Datadog and the other half sitting in a WordPress admin you have to log into separately.
Alerting on the right events. You can build Datadog monitors directly on your WordPress log stream. A new admin user created at 2am? Alert. A payment gateway plugin deactivated on a WooCommerce store? Alert. The same alerting tools your team already knows, now applied to WordPress.
Your retention, your rules. Your Datadog account follows your own retention policies. And that external copy is out of reach if a site is ever compromised – even if someone clears the on-site logs, the external copy is already safely stored and untouched.
The multi-site view. If multiple WordPress sites are all streaming to the same Datadog account, you can search across your entire portfolio in one query. “Which of my sites had a user role changed this week?” One search. Done.
It’s called Log Channels, not “the Datadog integration”
The reason I named this feature Log Channels rather than tying it to a single destination is that your team might not use Datadog – and that’s fine. Log Channels supports a range of platforms: Better Stack, Grafana Loki, Slack, Papertrail, Loggly, custom Syslog/SIEM targets, and your own webhook endpoint. The idea is the same regardless: bring the logging platform you already use, and your WordPress events will meet you there.
But if Datadog is where your team lives, this was built with you in mind.
Getting started
Log Channels is available in Activity Log Pro Premium. Once you have the premium add-on installed, adding a Datadog channel takes a couple of minutes – paste in your API key, choose your region, hit the test button to confirm the connection is working, and you’re done. Every log entry goes straight to Datadog from that point forward.
No new SaaS dashboard to learn. No extra subscription. Just your WordPress events, in the tool you already use.
See Log Channels features and pricing →
Activity Log Pro is a WordPress activity log and audit trail plugin. Log Channels is a Premium feature available as part of the Activity Log Pro Premium add-on.