In this tutorial, we will go through a working example of a NestJS application auto-instrumented with OpenTelemetry. In our example we will use a simple application that outputs “Hello World!” when we call it in the browser. We will instrument this application with OpenTelemetry’s Node.js client library to generate trace data and send it to an OpenTelemetry Collector. The Collector will then export the trace data to an external distributed tracing analytics tool of our choice.
Amazon Kinesis is the real-time stream processing service of AWS. Whether you got video, audio, or IoT streaming data to handle, Kinesis is the way to go. Kinesis is a serverless managed service that integrates nicely with other services like Lambda or S3. Often, you will use it when SQS or SNS is too low-level. But as with all the other services on AWS, Kinesis is a professional tool that comes with its share of complications.
Eleven basic checks and one status page. That’s all you see when looking over the account usage of the Uptime.com account you are now managing for your company. When you logged in for the first time you saw a dashboard with cards and metrics, labeled with titles that don’t obviously connect to services you offer. Your first clicks were to navigate to view the subscription – maybe your plan details can give you some guidance. Does this sound like you?
The software is getting more and more complicated and so is the infrastructure behind it. It is no longer what it used to be with a single web or application server and a database backing it up. Throughout the years, the infrastructure has become more and more complicated. We have multiple databases, queues, datastores, search engines, and configurations. We want to incorporate continuous delivery and automated testing and deploy everything easily.