Adding deployment resources for the guides on the Autometrics doc page including:

- Docker deployment resources for Prometheus and OTel Collector

Author: Nele Lea Uhlemann

deployment-guides-ressources/README.md

@@ -0,0 +1,5 @@
+# Ressources for deployment guides
+
+This folder contains deployment resources for the various components of the Autometrics microframework designed for different cloud environments and platforms.
+
+For comprehensive deployment guides, please refer to our [documentation page](https://docs.autometrics.dev/).

deployment-guides-ressources/otel-collector/Dockerfile

@@ -0,0 +1,2 @@
+FROM otel/opentelemetry-collector:latest
+ADD otel-collector-config.yaml /etc/otelcol/config.yaml

deployment-guides-ressources/otel-collector/README.md

@@ -0,0 +1,10 @@
+# OpenTelemetry (OTel) Collector deployment ressources
+
+The detailed guides for the different platforms can be found [here](https://docs.autometrics.dev/deploying-otel-collector)
+
+## Using Docker with OTel Collector for:
+- Local setup
+- Northflank
+- Railway 
+
+The OTel Collector provides a [Docker image](https://hub.docker.com/r/prom/prometheus) for easy deployment. To customize it, we use a **Dockerfile** with the image and a **otel-collector-config.yml** file for configuration.

deployment-guides-ressources/otel-collector/otel-collector-config.yaml

@@ -0,0 +1,23 @@
+receivers:
+  otlp:
+    protocols:
+      http:
+        endpoint: 0.0.0.0:4318
+# Example to push metrics towards Prometheus (not recommended by Prometheus). 
+# Refer to the endpoint you have Prometheus running in your private network.
+# Include /api/v1/write to the endpoint
+# 
+exporters:
+  prometheusremotewrite:
+    endpoint: http://prometheus:9090/api/v1/write
+    resource_to_telemetry_conversion:
+      enabled: true # Convert resource attributes to metric labels
+
+service:
+  telemetry:
+    logs:
+      level: "debug"
+  pipelines:
+    metrics:
+      receivers: [otlp]
+      exporters: [prometheusremotewrite]

deployment-guides-ressources/prometheus/Dockerfile

@@ -0,0 +1,13 @@
+FROM prom/prometheus
+
+USER root
+RUN mkdir -p /etc/config
+USER nobody
+
+ADD prometheus.yml /etc/prometheus/
+ADD autometrics-rules.yml /etc/config/
+
+# Options:
+# Enable the remote write endpoint, if you want to push metrics via the Otel-collector
+# Change log level if you need to debug
+# CMD ["--web.enable-remote-write-receiver", "--log.level=debug"]

deployment-guides-ressources/prometheus/README.md

@@ -0,0 +1,13 @@
+# Prometheus deployment ressources
+
+The detailed guides for the different platforms can be found [here](https://docs.autometrics.dev/deploying-prometheus)
+
+## Using Docker with Prometheus for:
+- Local setup
+- Northflank
+- Railway 
+
+Prometheus provides a [Docker image](https://hub.docker.com/r/prom/prometheus) for easy deployment. To customize it, we use a **Dockerfile** with the image and a **prometheus.yml** file for configuration. In our configuration, we refer to our **autometrics-rules.yml**. 
+
+### Platform-Specific Networking:
+The main difference comes in setting up networking on these platforms. We've detailed the steps in [our guides](https://docs.autometrics.dev/deploying-prometheus), so check them out for specific instructions tailored to each cloud platform.

deployment-guides-ressources/prometheus/autometrics-rules.yml

@@ -0,0 +1,28 @@
+global:
+  evaluation_interval: 15s
+  scrape_interval: 15s
+  scrape_timeout: 10s
+rule_files:
+  - /etc/config/autometrics-rules.yml
+# Prometheus polling metrics from itself
+scrape_configs:
+  - job_name: prometheus
+    static_configs:
+      - targets:
+          - localhost:9090
+# Prometheus polling metrics from your application running in the same network
+scrape_configs:
+  - job_name: internal-endpoint2
+    metrics_path: /metrics
+    static_configs:
+      # Within a private network over http. 
+      # For Northflank and Railway you can find the private network reference in the service settings
+      # It will be something like this "service-name:PORT"
+      - targets: ['example-service:8000'] 
+    # For a real deployment, you would want the scrape interval to be
+    # longer but for testing, you want the data to show up quickly
+    scrape_interval: 120s
+
+# Note: if you want to push your metrics towards Prometheus for example with the Otel collecor,
+# you don't need to define a scrape endpoint.
+# just make sure in the Dockerfile to enable the remote write endpoint