LAYER_11_APM

Defines an OpenTelemetry-based APM layer for standardized tracing, metrics, and logging.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/tinkermonkey/documentation_robotics_viewer --skill layer-11-apm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: LAYER_11_APM
Source: https://github.com/tinkermonkey/documentation_robotics_viewer/tree/main/.claude/skills/dr_11_apm_layer
Command: npx skills add https://github.com/tinkermonkey/documentation_robotics_viewer --skill layer-11-apm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a standardized model for observability by defining an OpenTelemetry-based APM layer, enabling consistent traces, metrics, and logs across services.

Core Features & Use Cases

  • Traces, Metrics, and Logs: standard definitions for spans, metrics, and log records within a unified layer.
  • Instrumentation & Resources: guidance for instrumentation scope and resource attributes to ensure consistent data collection.
  • Cross-Layer Guidance: mappings and relationships to other system layers to align monitoring with service architecture.
  • Central Entity & Entities: centralizes on the Span unit and enumerates core APM entities to support comprehensive observability.

Quick Start

Ask the system to generate an APM layer model for a sample service, including span definitions, trace configurations, metric instruments, and log configuration.

Frequently Asked Questions about LAYER_11_APM

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize OpenTelemetry observability across multiple services?

To standardize OpenTelemetry observability across multiple services, you need to define an APM layer model that specifies consistent traces, metrics, logs, and instrumentation scope. This ensures unified data collection across your architecture.

What is an APM layer model for tracing and metrics?

An APM layer model for tracing and metrics is a standardized framework that defines spans, metric instruments, and log configurations. It centralizes observability entities to align monitoring with your service architecture.

How do I define instrumentation scope and resource attributes for consistent logging?

Defining instrumentation scope and resource attributes for consistent logging requires mapping relationships to other system layers. This guides data collection to ensure logs, traces, and metrics are captured uniformly across services.

Can I use this APM layer model for architectures requiring SLA considerations?

Yes, you can use this APM layer model for architectures requiring SLA considerations. It provides specific guidance on resource attributes and instrumentation scope to ensure your observability data supports comprehensive SLA monitoring.

What's the best way to generate span definitions and trace configurations for a service?

The best way to generate span definitions and trace configurations is to request an APM layer model for your sample service. This produces standard definitions for spans, metric instruments, and log records within a unified layer.