5f9c0d21c5
ref https://linear.app/tryghost/issue/ENG-1505/start-monitoring-event-loop-utilization-in-production-with - The two main constraints we've observed in Ghost are the database connection pool and the CPU usage. However, there is a third constraint that we may be hitting, but can't currently observe: the event loop. - This commit re-enabled OpenTelemetry (behind a config flag), removes the problematic tracing instrumentation which was breaking the frontend, and adds a Prometheus endpoint to export the eventLoopUtilization metric. - This should give us visibility into whether we are hitting constraints in the event loop and address the root cause if we are. |
||
|---|---|---|
| .. | ||
| e2e-api | ||
| e2e-browser | ||
| e2e-frontend | ||
| e2e-server | ||
| e2e-webhooks | ||
| integration | ||
| regression | ||
| unit | ||
| utils | ||
| .eslintignore | ||
| .eslintrc.js | ||