The ability to observe and collect information about your application in production is often called “Observability”. If you have Node.js applications in production you should be thinking about Observability of those applications from the start. If you want to ramp up on the background Observability in 2022: Why it matters and how OpenTelemetry can help is a great place to start.
This short blog aims to help you with recommendations on what components to integrate into your Node.js applications as well as how to leverage them in an OpenShift environment.
Three key components of Observability include:
- Logging
- Metrics
- Distributed Tracing
For Node.js applications, the Node.js Reference architecture provides recommendations on components you can integrate into your application in order to generate Logging, Metrics and Distributed Tracing information.
Generating the source observability information is only the beginning of the effort. You need a way to collect, analyze and act on that information. The good news is that OpenShift includes built-in capabilities that can help you with that task. Check out these three blog posts on how to leverage the logging, metrics and distributed tracing backends available in OpenShift:
- Consume Pino logs from Node.js applications
- Monitor Node.js applications on Red Hat OpenShift with Prometheus
- How to use OpenTelemetry to trace Node.js applications
We hope this information helps you simplify how you develop, deploy and manage your Node.js applications in production.
If you want to learn more about what Red Hat is up to on the Node.js front, check out our Node.js landing page.
