Debugging faulty API access tenant side?

AntonioSousa — Sat, 01 Aug 2026 10:31:47 GMT

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?

Re: Debugging faulty API access tenant side?

sujit_k_singh — Sun, 02 Aug 2026 23:49:21 GMT

Hi @AntonioSousa

I think this is expected behaviour, becuase dt.system.events and audit logs primarily record authorized, successful operations. 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 , not blocked/failed ones.

Here are the primary ways to troubleshoot these: Check ActiveGate HTTP Logs: If traffic passes through an ActiveGate, check its local access.log 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

topic Re: Debugging faulty API access tenant side? in Open Q&A

Debugging faulty API access tenant side?

Re: Debugging faulty API access tenant side?