AEM Production Troubleshooting: Trace Slow Requests Across the Platform.

Record the URL, relevant request context, access state and observed failure. Preserve a consistent time window across logs and monitoring so unrelated events are not mistaken for a causal chain.

An edge timeout does not establish whether Publish, a repository query or a remote dependency caused the delay. Likewise, a cache miss is evidence about delivery behavior, not proof that caching is the root cause.

Use Browser → CDN → Load Balancer → Apache → Dispatcher → AEM Publish as a starting delivery map, then inspect Sling, OSGi, JCR and external services as the request requires. This is a diagnostic model, not a claim that every request traverses each dependency serially.

Compare correlated timings and logs, service availability and repository or API activity. Collect JVM evidence under the operational procedures appropriate to the environment, avoiding disruptive diagnostics or unbounded logging during an incident.

• Compare cached and controlled origin paths where access is authorized.
• Separate upstream waiting from application execution time.
• Record deployment and configuration changes near the observed onset.

Write down the suspected failing boundary, the evidence and the expected observation after a correction. Avoid mixing a cache change, service refactor and runtime adjustment into an untraceable intervention.

Detailed logging and runtime captures can affect the system and contain sensitive information. Choose the smallest useful observation, limit its duration and follow access and retention procedures.

If evidence identifies a cache-policy defect, continue with cache eligibility, query parameters and freshness.

A successful retry alone is not enough to establish recovery.

• Compare the same request and access state after the change.
• Inspect error rates, service health and dependency behavior in the same window.
• Check adjacent requests and document unresolved hypotheses for follow-up.

A useful incident review explains which evidence supported the conclusion and which alternatives were ruled out. That makes the diagnosis reusable in code reviews, mentoring and future production investigations.

These sources document product behavior. The design and validation approach above are engineering proposals, not claims made by the vendors.

• Adobe: Dispatcher configuration reference
• OSGi: Declarative Services specification