# Debugging faulty API access tenant side?

**URL:** <https://community.dynatrace.com/t/debugging-faulty-api-access-tenant-side/56613>\
**Category:** Open Q&A\
**Tags:** dql, dynatrace-api\
**Created:** [August 1, 2026, 10:31am UTC](https://community.dynatrace.com/t/debugging-faulty-api-access-tenant-side/56613 "2026-08-01T10:31:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AntonioSousa](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antoniosousa/32/50_2.png) [@AntonioSousa](https://community.dynatrace.com/u/AntonioSousa)\
**Post date:** [August 1, 2026, 10:31am UTC](https://community.dynatrace.com/t/debugging-faulty-api-access-tenant-side/56613/1 "2026-08-01T10:31:47Z")

</div>

I have debugged API access inside dt.system.events, using several approaches (origin.address,authentication.token, etc.), but I don’t seem to get errors. I can get successful ones, but not those giving 401s/404s/etc.  
I understand that these might lead to lot’s of issues, but is there a way to tackling this?

---

<div class="post-metadata">

**Author:** ![sujit\_k\_singh](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sujit\_k\_singh](https://community.dynatrace.com/u/sujit_k_singh)\
**Post date:** [August 2, 2026, 11:49pm UTC](https://community.dynatrace.com/t/debugging-faulty-api-access-tenant-side/56613/2 "2026-08-02T23:49:21Z")

</div>

Hi&nbsp;[@AntonioSousa](https://community.dynatrace.com/user/17213)

I think this is expected behaviour, becuase dt.system.events and audit logs primarily record authorized, successful operations.&nbsp;&nbsp;I mean to say rejections like 401 or 404 are dropped at the edge/gateway proxy layer before reaching the internal event-logging pipeline.

Worth checking: Settings → Preferences → Log audit events is enabled (captures config-changing API calls), but again this only helps for calls that succeeded and made a change ,&nbsp; not blocked/failed ones.

Here are the primary ways to troubleshoot these:&nbsp;Check ActiveGate HTTP Logs: If traffic passes through an ActiveGate, check its local access.log&nbsp; It captures HTTP status codes (401, 403, 404).

Dynatrace Support (For Tenant Edge Logs): SaaS edge proxies drop unauthenticated traffic to prevent log flooding, so raw 401/404 logs aren’t exposed in DQL. If you are troubleshooting a specific issue, then i feel best option is a support ticket.

Thanks,

Sujit