From cefabdb4284c2528ddb465e73a23713c13dc99d2 Mon Sep 17 00:00:00 2001 From: Paul Toffoloni Date: Mon, 16 Dec 2024 13:41:57 +0100 Subject: [PATCH] Add image --- Content/posts/otel-integration.md | 13 ++++++++++--- .../static/images/posts/otel-integration-arch.svg | 1 + 2 files changed, 11 insertions(+), 3 deletions(-) create mode 100644 Resources/static/images/posts/otel-integration-arch.svg diff --git a/Content/posts/otel-integration.md b/Content/posts/otel-integration.md index 7b1dbe4..5dd0d99 100644 --- a/Content/posts/otel-integration.md +++ b/Content/posts/otel-integration.md @@ -1,3 +1,12 @@ +--- +date: 2024-12-16 14:00 +description: Getting started with Vapor 4 and OpenTelemetry +tags: vapor, otel, prometheus, grafana +image: /static/images/posts/otel-integration.svg +author: Paul +authorImageURL: /author-images/paul.jpg +--- + # Instrumenting Vapor 4 with Swift OTel ## Observability @@ -14,9 +23,7 @@ In more practical terms, observability is made up of Before starting, let's give a small overview of our end goal. In Vapor 4, logging is automatic, and this post's aim is to add metrics collection to our system, but collecting tracing data is not much different. -![Blank diagram](/Users/pt/Downloads/Blank diagram.svg) - - +![Vapor OTel Architecture](/static/images/posts/otel-integration.svg) As you can see here there's a bunch of things going on, but we'll get into each of them. diff --git a/Resources/static/images/posts/otel-integration-arch.svg b/Resources/static/images/posts/otel-integration-arch.svg new file mode 100644 index 0000000..f68773d --- /dev/null +++ b/Resources/static/images/posts/otel-integration-arch.svg @@ -0,0 +1 @@ + \ No newline at end of file