Operations | Monitoring | ITSM | DevOps | Cloud

A Shopware store goes from smooth to sluggish—pages take 10 seconds to load, even longer in some cases. What happened? In this post, we tell the true story of how one overlooked plugin setting nearly collapsed a storefront, and how it was resolved using native tools. If you’re shipping code in Shopware without clear performance observability, this is your wake-up call. Everything was working, until it wasn’t.

How do you use ArgoCD and a GitHub workflow together with an external CI/CD tool (Jenkins in our case) to trace a specific PR/commit hash code in a GitHub repository that’s external to ArgoCD? The term ‘commit tracing’ comes from Michael Crenshaw – one of the lead developers of Argo.

Your checkout API just started throwing 500s during peak traffic. You SSH into production, tail logs across six microservices, and realize the database timeout buried in service's logs is causing cascade failures. Two hours later, you've fixed it, but you're thinking: "There has to be a better way." There is. Log monitoring tools centralize logs from your entire stack, making debugging systematic instead of archaeological.

Coralogix has released its APM Dependencies feature. This feature automatically surfaces and maps the relationships within and between your software and external services. It allows fine grained tracking of which endpoints within your APIs, depend on other endpoints, or external services and database tables.

Having spent two decades in technical leadership, I’ve seen first hand what separates great development teams from merely good ones. It’s not about the number of features shipped or the elegance of the codebase — it’s about the ability to consistently deliver value to the customer through really great user experience.

“You can’t investigate what you don’t have”. Every analyst knows the pain of missing context. You’re in the middle of a high-stakes investigation, but the logs you need are gone, archived weeks ago due to retention limits. Or worse, they were never collected in the first place to keep costs under control. This is the Visibility vs. Cost trap, and it puts analysts at a disadvantage every day.

Traces tell you what happened and when. Logs tell you why. When something breaks, logs are often your first clue—and if they’re correlated with traces, they can cut debugging time down from hours to minutes. In this section, we’ll wire up end-to-end structured logging across both server and browser environments in your Next.js app, complete with trace correlation and SigNoz integration.