Opentelemetry exporter prometheus install#

Add it to a new project by following the install steps.Ĭreate an app.js file and create the basic skeleton for the application: const express = require('express') Ĭonsole.log(`Listening for requests on }) Install and setup ExpressJSĮxpressJS provides a lot of boilerplate for creating a JavaScript application that serves HTTP endpoints, so is a great start point. You can find the full and final code on GitHub. The tutorial starts by adding basic instrumentation and sending metrics to a Prometheus backend, then adds more, and adds the Chronosphere collector. The example for this post is an ExpressJS application that serves API endpoints and exports Prometheus-compatible metrics. This blog series will use the OpenTelemetry specification and SDKs, but collect and export a variety of the formats it handles. The key project is OpenTelemetry from the Cloud Native Computing Foundation (CNCF). While this remains true, there are increased efforts to create portable standards that everyone can use and add their features on top of but retain interoperability. An introduction to metrics dataĭifferent vendors and open source projects created their own ways to represent the event data they collect. Later posts will take these concepts further. This post focuses on introductory concepts, setting up the dependencies needed, and generating some basic metrics. There are of course dozens of methods, frameworks, and tools to help you collect the events that are important to you, and this post begins a series looking at some of those.

This process is called “instrumentation” and broadly involves collecting events in infrastructure and code that include metrics, logs, and traces. A lot of what you read around the topic of Observability mentions the benefits and potential of analyzing data, but little about how you collect it.

Opentelemetry exporter prometheus