The ServiceNow Cloud Observability platform combines tracing, metric and log data to gain full observability into your system in one tool. Your dashboards and alerts will not only show you when there’s a problem, they become actionable tools that find the source of that problem for you. Changes in system behavior are mapped automatically to changes across service boundaries. You don’t need to know the dependencies in your system, Cloud Observability understands them and can find the issues deep in your stack.
Before we start instrumenting code and sending data to Cloud Observability, we must ensure a few prerequisites are met:
You will need a Cloud Observability account to send OpenTelemetry data to for this workshop. Cloud Observability offers a free Community Tier account. If you don’t already have an account, you can sign up here.
If you don’t get the confirmation email after signing up for an account, please check your Spam folders
You can use any IDE or editor that your prefer. If you don’t have one yet, we recommend using Visual Studio Code
We have created a simple JavaScript application that you will instrument with OpenTelemetry. This workshop builds off of the distributed tracing workshop from the Observing Node.js Microservices series. If you have completed that workshop you can continue from that source code. Otherwise use the tracing-complete
branch as the starting point for this workshop. Clone the git repo or download the files here.
git clone https://github.com/lightstep/nodejs-microservices-example-app.git
git checkout tracing-complete
You can view the completed workshop files by changing to the metrics-complete
branch. Use this as a reference if you get stuck anywhere during the workshop.
This workshop uses Docker to run the microservices on your machine. Click here to download and install Docker Desktop if you have not already done so.
When you’re all setup, let’s start by collecting metrics from Docker!
next: Docker Metrics