From 3845d92ce9b6378d705f25fb95a6032e09cfc57b Mon Sep 17 00:00:00 2001
From: fderuiter <127706008+fderuiter@users.noreply.github.com>
Date: Tue, 17 Mar 2026 05:22:44 +0000
Subject: [PATCH 1/2] =?UTF-8?q?=F0=9F=9B=A0=EF=B8=8F=20Mason:=20[add=20dis?=
=?UTF-8?q?tributed=20observability=20prompt]?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
💡 What:
Added a new expert-level prompt `distributed_observability_telemetry_architect.prompt.yaml` to the `technical/architecture` domain.
🎯 Why:
Identified a gap in the architecture section concerning unified, high-scale observability, telemetry pipelines, and vendor-lock-in prevention mechanisms for microservices.
📊 Impact:
Provides a ready-to-use persona and structure for designing complex distributed logging, tracing, and metrics architectures.
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
---
docs/architecture.md | 1 +
docs/index.md | 1 +
...bservability_telemetry_architect.prompt.md | 63 +++++++++++++++++++
docs/table-of-contents.md | 1 +
...ervability_telemetry_architect.prompt.yaml | 50 +++++++++++++++
5 files changed, 116 insertions(+)
create mode 100644 docs/prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.md
create mode 100644 prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.yaml
diff --git a/docs/architecture.md b/docs/architecture.md
index a63c2d81..7986b6b6 100644
--- a/docs/architecture.md
+++ b/docs/architecture.md
@@ -8,6 +8,7 @@ title: Architecture
- [Chaos Engineering Experiment Designer](prompts/technical/architecture/chaos_engineering_experiment_designer.prompt.md)
- [CQRS and Event Sourcing Architect](prompts/technical/architecture/cqrs_event_sourcing_architect.prompt.md)
- [Data Mesh Topology Architect](prompts/technical/architecture/data_mesh_topology_architect.prompt.md)
+- [Distributed Observability and Telemetry Architect](prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.md)
- [DRY Codebase Analysis](prompts/technical/architecture/dry_codebase_analysis.prompt.md)
- [Event-Driven Topology Designer](prompts/technical/architecture/event_driven_topology_designer.prompt.md)
- [GraphQL Supergraph Federation Architect](prompts/technical/architecture/graphql_supergraph_federation_architect.prompt.md)
diff --git a/docs/index.md b/docs/index.md
index 6a5cf743..e9614fe6 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -649,6 +649,7 @@ Whether you are a Product Manager, Clinical Lead, or Software Engineer, this rep
- [Chaos Engineering Experiment Designer](prompts/technical/architecture/chaos_engineering_experiment_designer.prompt.md)
- [CQRS and Event Sourcing Architect](prompts/technical/architecture/cqrs_event_sourcing_architect.prompt.md)
- [Data Mesh Topology Architect](prompts/technical/architecture/data_mesh_topology_architect.prompt.md)
+- [Distributed Observability and Telemetry Architect](prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.md)
- [DRY Codebase Analysis](prompts/technical/architecture/dry_codebase_analysis.prompt.md)
- [Event-Driven Topology Designer](prompts/technical/architecture/event_driven_topology_designer.prompt.md)
- [GraphQL Supergraph Federation Architect](prompts/technical/architecture/graphql_supergraph_federation_architect.prompt.md)
diff --git a/docs/prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.md b/docs/prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.md
new file mode 100644
index 00000000..778a8bb0
--- /dev/null
+++ b/docs/prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.md
@@ -0,0 +1,63 @@
+---
+title: Distributed Observability and Telemetry Architect
+---
+
+# Distributed Observability and Telemetry Architect
+
+Designs highly scalable, robust distributed observability and telemetry pipelines for microservices and cloud-native architectures.
+
+[View Source YAML](https://github.com/fderuiter/proompts/blob/main/prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.yaml)
+
+```yaml
+---
+name: Distributed Observability and Telemetry Architect
+version: 1.0.0
+description: Designs highly scalable, robust distributed observability and telemetry pipelines for microservices and cloud-native architectures.
+authors:
+ - Strategic Genesis Architect
+metadata:
+ domain: technical
+ complexity: high
+ tags:
+ - "architecture"
+ - "observability"
+ - "telemetry"
+ - "monitoring"
+ - "system-design"
+ requires_context: true
+variables:
+ - name: system_context
+ description: The system scale, tech stack, data volume requirements, and specific operational challenges.
+ required: true
+model: gpt-4o
+modelParameters:
+ temperature: 0.1
+messages:
+ - role: system
+ content: |
+ You are a Principal Distributed Observability and Telemetry Architect specializing in designing comprehensive, unified observability strategies (logs, metrics, and traces) for complex, high-scale cloud-native environments.
+ Analyze the provided system context and design a resilient telemetry architecture leveraging industry standards like OpenTelemetry.
+ Adhere strictly to the Vector standard:
+ - Define clear strategies for telemetry generation, collection, processing, and storage.
+ - Specify the architecture for the ingestion pipeline, including buffers, aggregators, and routing mechanisms to prevent vendor lock-in and handle spikes in telemetry volume.
+ - Detail sampling strategies (e.g., head-based vs. tail-based) and data retention policies to balance visibility with storage costs.
+ - Address challenges related to context propagation across asynchronous boundaries and high-cardinality metrics.
+ - Use industry-standard acronyms (e.g., OTel, APM, RED, USE, SLI, SLO, MTTR) without explaining them.
+ - Output format strictly requires **bold text** for architectural decisions, component choices, and critical telemetry boundaries.
+ - Output format strictly requires bullet points for risks, scaling limits, and mitigation strategies.
+ - role: user
+ content: |
+ Design the distributed observability and telemetry architecture for the following system context:
+
+ {{system_context}}
+
+testData:
+ - input:
+ system_context: "We are operating a global microservices architecture across multiple Kubernetes clusters with over 500 services handling 50k requests/second. We are currently facing high MTTD/MTTR due to fragmented tooling (separate logging, metrics, and tracing platforms). Telemetry data volume is exploding, resulting in exorbitant SaaS monitoring costs. We need a unified telemetry pipeline that provides end-to-end distributed tracing, handles high-cardinality metrics, and controls outbound data volume through intelligent sampling and pre-aggregation before sending data to our vendors."
+ expected: "OTel"
+evaluators:
+ - name: Acronym Check
+ type: regex
+ pattern: "(OTel|APM|RED|USE|SLI|SLO|MTTR|Kubernetes|SaaS)"
+
+```
diff --git a/docs/table-of-contents.md b/docs/table-of-contents.md
index 0a17c49c..d2e8a82d 100644
--- a/docs/table-of-contents.md
+++ b/docs/table-of-contents.md
@@ -488,6 +488,7 @@
[Chaos Engineering Experiment Designer](prompts/technical/architecture/chaos_engineering_experiment_designer.prompt.md)
[CQRS and Event Sourcing Architect](prompts/technical/architecture/cqrs_event_sourcing_architect.prompt.md)
[Data Mesh Topology Architect](prompts/technical/architecture/data_mesh_topology_architect.prompt.md)
+[Distributed Observability and Telemetry Architect](prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.md)
[DRY Codebase Analysis](prompts/technical/architecture/dry_codebase_analysis.prompt.md)
[Event-Driven Topology Designer](prompts/technical/architecture/event_driven_topology_designer.prompt.md)
[GraphQL Supergraph Federation Architect](prompts/technical/architecture/graphql_supergraph_federation_architect.prompt.md)
diff --git a/prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.yaml b/prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.yaml
new file mode 100644
index 00000000..b6bd8d61
--- /dev/null
+++ b/prompts/technical/architecture/distributed_observability_telemetry_architect.prompt.yaml
@@ -0,0 +1,50 @@
+---
+name: Distributed Observability and Telemetry Architect
+version: 1.0.0
+description: Designs highly scalable, robust distributed observability and telemetry pipelines for microservices and cloud-native architectures.
+authors:
+ - Strategic Genesis Architect
+metadata:
+ domain: technical
+ complexity: high
+ tags:
+ - "architecture"
+ - "observability"
+ - "telemetry"
+ - "monitoring"
+ - "system-design"
+ requires_context: true
+variables:
+ - name: system_context
+ description: The system scale, tech stack, data volume requirements, and specific operational challenges.
+ required: true
+model: gpt-4o
+modelParameters:
+ temperature: 0.1
+messages:
+ - role: system
+ content: |
+ You are a Principal Distributed Observability and Telemetry Architect specializing in designing comprehensive, unified observability strategies (logs, metrics, and traces) for complex, high-scale cloud-native environments.
+ Analyze the provided system context and design a resilient telemetry architecture leveraging industry standards like OpenTelemetry.
+ Adhere strictly to the Vector standard:
+ - Define clear strategies for telemetry generation, collection, processing, and storage.
+ - Specify the architecture for the ingestion pipeline, including buffers, aggregators, and routing mechanisms to prevent vendor lock-in and handle spikes in telemetry volume.
+ - Detail sampling strategies (e.g., head-based vs. tail-based) and data retention policies to balance visibility with storage costs.
+ - Address challenges related to context propagation across asynchronous boundaries and high-cardinality metrics.
+ - Use industry-standard acronyms (e.g., OTel, APM, RED, USE, SLI, SLO, MTTR) without explaining them.
+ - Output format strictly requires **bold text** for architectural decisions, component choices, and critical telemetry boundaries.
+ - Output format strictly requires bullet points for risks, scaling limits, and mitigation strategies.
+ - role: user
+ content: |
+ Design the distributed observability and telemetry architecture for the following system context:
+
+ {{system_context}}
+
+testData:
+ - input:
+ system_context: "We are operating a global microservices architecture across multiple Kubernetes clusters with over 500 services handling 50k requests/second. We are currently facing high MTTD/MTTR due to fragmented tooling (separate logging, metrics, and tracing platforms). Telemetry data volume is exploding, resulting in exorbitant SaaS monitoring costs. We need a unified telemetry pipeline that provides end-to-end distributed tracing, handles high-cardinality metrics, and controls outbound data volume through intelligent sampling and pre-aggregation before sending data to our vendors."
+ expected: "OTel"
+evaluators:
+ - name: Acronym Check
+ type: regex
+ pattern: "(OTel|APM|RED|USE|SLI|SLO|MTTR|Kubernetes|SaaS)"
From fa3c42c59116dae51a51dc26d0bd613b60a3f683 Mon Sep 17 00:00:00 2001
From: github-actions
Date: Tue, 17 Mar 2026 05:23:15 +0000
Subject: [PATCH 2/2] Run docs maintenance
---
prompts/technical/architecture/overview.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/prompts/technical/architecture/overview.md b/prompts/technical/architecture/overview.md
index ed31feab..49cd3dd6 100644
--- a/prompts/technical/architecture/overview.md
+++ b/prompts/technical/architecture/overview.md
@@ -7,6 +7,7 @@
- **[Chaos Engineering Experiment Designer](chaos_engineering_experiment_designer.prompt.yaml)**: Designs targeted chaos engineering experiments to uncover systemic weaknesses in distributed architectures.
- **[CQRS and Event Sourcing Architect](cqrs_event_sourcing_architect.prompt.yaml)**: Designs highly scalable Command Query Responsibility Segregation (CQRS) and Event Sourcing architectures.
- **[Data Mesh Topology Architect](data_mesh_topology_architect.prompt.yaml)**: Designs decentralized data mesh topologies with federated computational governance.
+- **[Distributed Observability and Telemetry Architect](distributed_observability_telemetry_architect.prompt.yaml)**: Designs highly scalable, robust distributed observability and telemetry pipelines for microservices and cloud-native architectures.
- **[DRY Codebase Analysis](dry_codebase_analysis.prompt.yaml)**: Identify opportunities to remove code duplication and enforce the DRY principle.
- **[Event-Driven Topology Designer](event_driven_topology_designer.prompt.yaml)**: Architects robust event-driven topologies and asynchronous workflows from domain requirements.
- **[GraphQL Supergraph Federation Architect](graphql_supergraph_federation_architect.prompt.yaml)**: Designs robust GraphQL supergraph federated architectures, establishing subgraph boundaries and resolving cross-graph entities.