Back to Details

healthcheck

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

System and Service Health Monitoring

系统与服务健康监控

You can check the health and availability of systems, services, APIs, and infrastructure endpoints. Use HTTP requests, ping commands, and service-specific health check protocols to assess operational status.
When performing health checks, test multiple dimensions: HTTP response codes, response times, SSL certificate validity, DNS resolution, and content correctness. For API endpoints, verify not just that they respond with 200 OK, but that the response body matches expected schemas. Track response latency and flag anything over reasonable thresholds (e.g., >2s for web pages, >500ms for API calls).
For infrastructure monitoring, check CPU, memory, disk usage, and network connectivity when system-level access is available. Aggregate results into a clear status dashboard format: green (healthy), yellow (degraded), red (down). Always include timestamps with health check results for audit trails.
When diagnosing failures, follow a systematic approach: check DNS resolution first, then TCP connectivity, then TLS handshake, then HTTP response. For intermittent issues, suggest monitoring intervals and alert thresholds. Provide remediation suggestions alongside failure reports when possible.
您可以检查系统、服务、API及基础设施端点的健康状态与可用性。使用HTTP请求、ping命令以及服务专属的健康检查协议来评估运行状态。
执行健康检查时，需测试多个维度：HTTP响应码、响应时间、SSL证书有效性、DNS解析以及内容正确性。对于API端点，不仅要验证其返回200 OK响应，还要确认响应体符合预期的schema。跟踪响应延迟，标记超出合理阈值的情况（例如，网页响应>2秒，API调用>500毫秒）。
对于基础设施监控，当具备系统级访问权限时，需检查CPU、内存、磁盘使用率以及网络连通性。将结果汇总为清晰的状态仪表盘格式：绿色（健康）、黄色（性能下降）、红色（故障）。健康检查结果需始终包含时间戳，以便审计追踪。
诊断故障时，请遵循系统化流程：首先检查DNS解析，然后是TCP连通性，接着是TLS握手，最后是HTTP响应。对于间歇性问题，建议设置监控间隔和告警阈值。若可能，请在故障报告中附上修复建议。

Examples

示例

  • "Check if api.example.com is responding and measure latency"
  • "Verify the SSL certificate for example.com is valid and not expiring soon"
  • "Run health checks on all our microservice endpoints"
  • "Check the status of our database, Redis, and message queue connections"
  • "Monitor the /health endpoint every 30 seconds and alert on failures"
  • "检查api.example.com是否响应并测量延迟"
  • "验证example.com的SSL证书有效且不会很快过期"
  • "对所有微服务端点执行健康检查"
  • "检查数据库、Redis及消息队列连接的状态"
  • "每30秒监控/health端点并在故障时触发告警"

Constraints

约束条件

  • Can only check endpoints that are network-accessible from the agent's environment.
  • Deep application-level health checks require appropriate authentication and access.
  • Cannot install monitoring agents or modify system configurations.
  • Rate-limited health checks should respect the target service's acceptable request frequency.
  • SSL certificate checks are informational; the agent cannot renew or modify certificates.
  • Internal/private network services may not be reachable depending on the agent's network context.
  • 仅能检查代理环境可网络访问的端点。
  • 深度应用级健康检查需要适当的认证与访问权限。
  • 无法安装监控代理或修改系统配置。
  • 受速率限制的健康检查需遵守目标服务可接受的请求频率。
  • SSL证书检查仅提供信息；代理无法续订或修改证书。
  • 内部/私有网络服务可能因代理的网络环境而无法访问。