Release
Put application behavior alongside the release that changed it.
See the health, performance, and runtime evidence behind each Shipploy application, with the release context that explains what changed.

Put application behavior alongside the release that changed it.
Distinguish missing signals from measured application health.
Find the runtime evidence behind an error or unexpected response.
Keep the same application and time interval as you investigate.
Start with an application, a release or an error.
Keep the relevant sources and time interval together.
Separate running infrastructure, observed health, and signal freshness. An app without fresh data does not quietly look healthy.
See which version is serving, which candidate failed, and when behavior changed. A failed release never becomes the story of the app that is running.
Move from an application to its logs without losing the interval you are investigating. Planned trace links will extend that same context across requests.

Generic dashboards make you reconstruct a deployment story by hand. Shipploy starts with the application and makes the release a first-class part of the investigation.
Explore documentationSearch the runtime signal tied to a release.
See real runtime behavior as support is verified.
Understand the evidence behind a condition.
Follow a request when instrumentation is enabled.
Tell us what you need to observe. We’ll help you assess the available QA scope.
Get started