New Relic’s container orchestration team has developed best practices for maintaining integrity in services running on their platform. They emphasize the importance of health checks, which should respond with a status code representing the true state of the service's health. Health checks should be designed to ensure a service is "running" and not just responding. Latency, context, dependency handling, cold starts, and thundering herds are key considerations when writing effective health checks. Additionally, readiness checks provide a signal that a deployment is safe to continue, while monitoring and alerting solutions help keep the platform observable and operators happy. The CF team advises developers to use active external checks, such as New Relic Synthetics, to verify the network path for HTTP services. The CF metrics pipeline collects container events, metrics, and logs, powering key alerts that all services should use in production. By following these guidelines, teams can build highly available services that delight customers and keep operators rested and healthy.