Health and overview
The Overview page is the fastest way to confirm whether an application is running, which version is active, and where it is available. Health checks continue after deployment so a later problem can be reflected in the application status.
- Open the live URL from Overview after the application becomes healthy.
- Check the active deployment and provider details when confirming what is running.
- Use Monitoring for recent health samples and availability context.
Application logs
Logs collects output from the running components and the deployment process. Filter the timeline by source or component to reduce noise while investigating a problem.
- Start with the time when the status changed or a deployment began.
- Compare application output with the related deployment events.
- Keep customer data and credentials out of log messages.
Note: Logs can reveal what the application reported, but they do not replace application-level error handling and user-safe failure messages.
Activity and builds
Activity explains the stages Infrastry completed for an application. Builds groups the source revision, artifact, and deployments created from the same build work.
- Use Activity to find the stage that stopped or needs input.
- Use Builds to verify which source revision produced a release.
- Keep earlier attempts as context when comparing a successful launch with a failed one.
Shell access
Shell opens a live terminal in a running application or dependency container. Use it for focused inspection when the overview and logs do not answer the question.
- Choose the container you intend to inspect before connecting.
- Prefer read-only checks until you understand the state of the runtime.
- Treat manual changes as temporary; make durable fixes in the repository or application configuration and deploy them.
Note: A runtime can be replaced by a later deployment. Never rely on a manual shell change as the permanent fix.