Monitoring signals
Request history
Request history records method, tool, status, duration, and byte counts. It does not store request or response bodies. Use it to find blocked calls and slow operations without creating a second copy of resource data.Investigate a failed request
- Check whether the response was
401or403. - For
401, confirm the key is current and the client sends it as an HTTP header. - For
403, open Permissions and check the scope and resource allowlist. - If the request succeeded but was slow, compare its method and resource with the latency view.
