GitHub - rrohitramsen/AgentTel: Agent-ready telemetry — enriches OpenTelemetry spans across backend (JVM) and frontend (TypeScript) with the context AI agents need to autonomously diagnose and resolve production incidents

AgentTel
Agent-Ready Telemetry

AgentTel enriches OpenTelemetry telemetry with the structured context AI agents need to autonomously diagnose, reason about, and resolve production incidents — without human interpretation of dashboards. Works across the full stack: JVM backends (Java, Kotlin, Scala) and browser frontends (TypeScript/JavaScript).

Standard observability answers "What happened?" AgentTel adds "What does an AI agent need to know to act on this?"

The Problem

Modern observability tools generate massive volumes of telemetry — traces, metrics, logs — optimized for human consumption through dashboards and alert rules. AI agents tasked with autonomous incident response face critical gaps:

No behavioral context — Spans lack baselines, so agents can't distinguish normal from anomalous
No topology awareness — Agents don't know which services are critical, who owns them, or what depends on what
No decision metadata — Is this operation retryable? Is there a fallback? What's the runbook?
No actionable interface — Agents can read telemetry but can't query live system state or execute remediation

AgentTel closes these gaps at the instrumentation layer.

Design Philosophy

Core principle: telemetry should carry enough context for AI agents to reason and act autonomously.

AgentTel enriches telemetry at three levels — all configurable via YAML, no code changes required:

Level	Where	What	Example
Topology	OTel Resource (once per service)	Service identity, ownership, dependencies	team, tier, on-call channel
Baselines	Span attributes (per operation)	What "normal" looks like	P50/P99 latency, error rate
Decisions	Span attributes (per operation)	What an agent is allowed to do	retryable, runbook URL, escalation level

Topology is set once on the OTel Resource and automatically associated with all telemetry by the SDK. Baselines and decision metadata are attached per-operation on spans. This avoids redundant data on every span while ensuring agents always have the full context.

Quick Demo

Try AgentTel in one command — starts a demo payment service with OTel Collector and Jaeger:

cd examples/spring-boot-example
docker compose -f docker/docker-compose.yml up --build

Then open Jaeger to see enriched traces, Swagger UI for the API, and MCP Tool Docs for the agent interface.

What AgentTel Provides

Enriched Telemetry (agenttel-core)

Every span is automatically enriched with agent-actionable attributes:

Category	Attributes	Purpose
Topology	`agenttel.topology.team`, `tier`, `domain`, `dependencies`	Service identity and dependency graph
Baselines	`agenttel.baseline.latency_p50_ms`, `error_rate`, `source`	What "normal" looks like for each operation
Decisions	`agenttel.decision.retryable`, `idempotent`, `runbook_url`, `escalation_level`	What an agent is allowed to do
Anomalies	`agenttel.anomaly.detected`, `pattern`, `score`	Real-time deviation detection
SLOs	`agenttel.slo.budget_remaining`, `burn_rate`	Error budget consumption tracking

Agent Interface Layer (agenttel-agent)

A complete toolkit for AI agent interaction with production systems:

Component	Description
MCP Server	JSON-RPC server implementing the Model Context Protocol — exposes telemetry as tools AI agents can call
Health Aggregation	Real-time service health from span data with operation-level and dependency-level metrics
Incident Context	Structured incident packages: what's happening, what changed, what's affected, what to do
Remediation Framework	Registry of executable remediation actions with approval workflows
Action Tracking	Every agent decision and action recorded as OTel spans for full auditability
Context Formatters	Prompt-optimized output formats (compact, full, JSON) tuned for LLM context windows

Frontend Telemetry (agenttel-web)

Browser SDK for agent-ready frontend observability:

Feature	Description
Auto-Instrumentation	Page loads (Navigation Timing API), SPA navigation, `fetch`/`XMLHttpRequest` interception, click/submit interactions, JavaScript errors
Journey Tracking	Multi-step user funnel tracking with completion rates, abandonment detection, and duration baselines
Anomaly Detection	Client-side pattern detection — rage clicks, API failure cascades, slow page loads, error loops, funnel drop-offs
Cross-Stack Correlation	W3C Trace Context injection on all outgoing requests; backend trace ID extraction from responses
Route Baselines	Per-route configuration of expected page load times, API response times, error rates, and business criticality
Decision Metadata	Escalation levels, runbook URLs, retry policies, and fallback pages per route

Instrumentation Agent (agenttel-instrument)

IDE-integrated MCP server for automated instrumentation setup:

Tool	Description
`analyze_codebase`	Scans Java/Spring Boot source code — detects endpoints, dependencies, and framework
`instrument_backend`	Generates backend config — Gradle/Maven dependencies, annotations, agenttel.yml
`instrument_frontend`	Generates frontend config — React route detection, criticality inference, SDK initialization
`validate_instrumentation`	Validates agenttel.yml completeness against source code
`suggest_improvements`	Analyzes config and suggests fixes — missing baselines, uncovered endpoints, stale thresholds
`apply_improvements`	Auto-applies low-risk improvements using live health data; flags high-risk items for review

GenAI Instrumentation (agenttel-genai)

Full observability for AI/ML workloads on the JVM:

Framework	Approach	Coverage
Spring AI	SpanProcessor enrichment of existing Micrometer spans	Framework tag, cost calculation
LangChain4j	Decorator-based full instrumentation	Chat, embeddings, RAG retrieval
Anthropic SDK	Client wrapper	Messages API with token/cost tracking
OpenAI SDK	Client wrapper	Chat completions with token/cost tracking
AWS Bedrock	Client wrapper	Converse API with token/cost tracking

Quick Start

AgentTel supports multiple integration paths — pick what fits your stack:

Path	Best For	Effort
Spring Boot Starter	Spring Boot applications	Add dependency + YAML config
JavaAgent Extension	Any JVM app (no code changes)	JVM flag + YAML config
Web SDK	Browser/SPA applications	`npm install` + init call
Instrument Agent	IDE-assisted setup	Run MCP server in IDE

Backend: Spring Boot

1. Add Dependencies

Maven:

<dependencies>
    <!-- Core: span enrichment, baselines, anomaly detection, SLO tracking -->
    <dependency>
        <groupId>io.agenttel</groupId>
        <artifactId>agenttel-spring-boot-starter</artifactId>
        <version>0.1.0-alpha</version>
    </dependency>

    <!-- Optional: GenAI instrumentation -->
    <dependency>
        <groupId>io.agenttel</groupId>
        <artifactId>agenttel-genai</artifactId>
        <version>0.1.0-alpha</version>
    </dependency>

    <!-- Optional: Agent interface layer (MCP server, incident context, remediation) -->
    <dependency>
        <groupId>io.agenttel</groupId>
        <artifactId>agenttel-agent</artifactId>
        <version>0.1.0-alpha</version>
    </dependency>
</dependencies>

Gradle:

// build.gradle.kts
dependencies {
    // Core: span enrichment, baselines, anomaly detection, SLO tracking
    implementation("io.agenttel:agenttel-spring-boot-starter:0.1.0-alpha")

    // Optional: GenAI instrumentation
    implementation("io.agenttel:agenttel-genai:0.1.0-alpha")

    // Optional: Agent interface layer (MCP server, incident context, remediation)
    implementation("io.agenttel:agenttel-agent:0.1.0-alpha")
}

2. Configure Your Service

All enrichment is driven by YAML configuration -- no code changes needed:

# application.yml
agenttel:
  # Topology: set once on the OTel Resource, associated with all telemetry
  topology:
    team: payments-platform
    tier: critical
    domain: commerce
    on-call-channel: "#payments-oncall"
  dependencies:
    - name: postgres
      type: database
      criticality: required
      timeout-ms: 5000
      circuit-breaker: true
    - name: stripe-api
      type: rest_api
      criticality: required
      fallback: "Return cached pricing"

  # Reusable operational profiles — reduce repetition across operations
  profiles:
    critical-write:
      retryable: false
      escalation-level: page_oncall
      safe-to-restart: false
    read-only:
      retryable: true
      idempotent: true
      escalation-level: notify_team

  # Per-operation baselines and decision metadata
  # Use bracket notation [key] for operation names with special characters
  operations:
    "[POST /api/payments]":
      profile: critical-write
      expected-latency-p50: "45ms"
      expected-latency-p99: "200ms"
      expected-error-rate: 0.001
      retryable: true               # overrides profile default
      idempotent: true
      runbook-url: "https://wiki/runbooks/process-payment"
    "[GET /api/payments/{id}]":
      profile: read-only
      expected-latency-p50: "15ms"
      expected-latency-p99: "80ms"

  baselines:
    rolling-window-size: 1000
    rolling-min-samples: 10
  anomaly-detection:
    z-score-threshold: 3.0

3. Optional: Annotate for IDE Support

Annotations are optional -- YAML config above is sufficient. Use @AgentOperation when you want IDE autocomplete and compile-time validation. Reference profiles to avoid repeating values:

@AgentOperation(profile = "critical-write")
@PostMapping("/api/payments")
public ResponseEntity<PaymentResult> processPayment(@RequestBody PaymentRequest req) {
    // Your business logic — spans are enriched automatically
}

When both YAML config and annotations define the same operation, YAML config takes priority. Per-operation values override profile defaults.

4. Start the MCP Server (Optional)

// Expose telemetry to AI agents via MCP
McpServer mcp = new AgentTelMcpServerBuilder()
    .port(8081)
    .contextProvider(agentContextProvider)
    .remediationExecutor(remediationExecutor)
    .build();
mcp.start();

AI agents can now call tools like get_service_health, get_incident_context, list_remediation_actions, and execute_remediation over JSON-RPC.

5. What You Get

Resource attributes (set once per service, associated with all telemetry):

agenttel.topology.team         = "payments-platform"
agenttel.topology.tier         = "critical"
agenttel.topology.domain       = "commerce"
agenttel.topology.on_call_channel = "#payments-oncall"
agenttel.topology.dependencies = [{"name":"postgres","type":"database",...}]

Span attributes (per operation, only on operations with registered metadata):

agenttel.baseline.latency_p50_ms = 45.0
agenttel.baseline.latency_p99_ms = 200.0
agenttel.baseline.error_rate     = 0.001
agenttel.baseline.source         = "static"
agenttel.decision.retryable      = true
agenttel.decision.runbook_url    = "https://wiki/runbooks/process-payment"
agenttel.decision.escalation_level = "page_oncall"
agenttel.anomaly.detected        = false
agenttel.slo.budget_remaining    = 0.85

When an incident occurs, agents get structured context via MCP:

=== INCIDENT inc-a3f2b1c4 ===
SEVERITY: HIGH
SUMMARY: POST /api/payments experiencing elevated error rate (5.2%)

## WHAT IS HAPPENING
Error Rate: 5.2% (baseline: 0.1%)
Latency P50: 312ms (baseline: 45ms)
Patterns: ERROR_RATE_SPIKE

## WHAT CHANGED
Last Deploy: v2.1.0 at 2025-01-15T14:30:00Z

## WHAT IS AFFECTED
Scope: operation_specific
User-Facing: YES
Affected Deps: stripe-api

## SUGGESTED ACTIONS
  - [HIGH] rollback_deployment: Rollback to previous version (NEEDS APPROVAL)
  - [MEDIUM] enable_circuit_breakers: Circuit break stripe-api

Frontend: Browser SDK

npm install @agenttel/web

import { AgentTelWeb } from '@agenttel/web';

AgentTelWeb.init({
  appName: 'checkout-web',
  appVersion: '1.0.0',
  environment: 'production',
  collectorEndpoint: '/otlp',

  routes: {
    '/checkout/:step': {
      businessCriticality: 'revenue',
      baseline: { pageLoadP50Ms: 800, apiCallP50Ms: 300 },
      decision: { escalationLevel: 'page_oncall', runbookUrl: 'https://wiki/runbooks/checkout' },
    },
  },

  journeys: {
    checkout: {
      steps: ['/products', '/cart', '/checkout/shipping', '/checkout/payment', '/confirmation'],
      baseline: { completionRate: 0.65, avgDurationS: 300 },
    },
  },

  anomalyDetection: {
    rageClickThreshold: 3,
    apiFailureCascadeThreshold: 3,
    errorLoopThreshold: 5,
  },
});

The SDK automatically instruments page loads, SPA navigation, API calls, clicks, and errors — with cross-stack correlation via W3C Trace Context headers.

IDE: Instrument Agent

Run the instrument agent as an MCP server in your IDE (Cursor, VS Code, etc.):

pip install agenttel-instrument
agenttel-instrument --config instrument.yml

Then ask your IDE agent: "Analyze my codebase and generate AgentTel configuration" — it will scan your endpoints, detect dependencies, and generate a complete agenttel.yml.

Module Overview

┌─────────────────────────────────────────────────────────────────────┐
│                         Your Application                            │
│    Backend: application.yml + @AgentOperation                       │
│    Frontend: AgentTelWeb.init(config)                               │
├──────────────────────────┬──────────────────┬───────────────────────┤
│  agenttel-spring-boot-   │  agenttel-       │  agenttel-web         │
│  starter                 │  javaagent-      │  (@agenttel/web)      │
│  Auto-config · BPP · AOP │  extension       │  Browser SDK          │
│  (Spring Boot apps)      │  (any JVM app)   │  (TypeScript/JS)      │
├──────────────┬───────────┴──┬───────────────┴───────────────────────┤
│agenttel-core │agenttel-genai│     agenttel-agent                    │
│              │              │                                       │
│ SpanProcessor│ LangChain4j  │ MCP Server (JSON-RPC)                 │
│ Baselines    │ Spring AI    │ Health Aggregation                    │
│ Anomaly      │ Anthropic SDK│ Incident Context + Reporting          │
│  Detection   │ OpenAI SDK   │ Remediation Framework                 │
│ SLO Tracking │ Bedrock SDK  │ Trend Analysis · SLO Reports          │
│ Pattern      │ Cost Calc    │ Executive Summaries                   │
│  Matching    │              │ Cross-Stack Context                   │
├──────────────┴──────────────┴───────────────────────────────────────┤
│                          agenttel-api                                │
│       @AgentOperation · AgentTelAttributes · Data Models            │
├─────────────────────────────────────────────────────────────────────┤
│                      OpenTelemetry SDK                               │
└─────────────────────────────────────────────────────────────────────┘

  agenttel-instrument (IDE MCP Server — Python)
  Codebase analysis · Config generation · Validation · Auto-improvements

Module	Artifact	Description
`agenttel-api`	`io.agenttel:agenttel-api`	Annotations, attribute constants, enums, data models. Zero runtime dependencies.
`agenttel-core`	`io.agenttel:agenttel-core`	Runtime engine — span enrichment, static + rolling baselines, z-score anomaly detection, pattern matching, SLO tracking, structured events.
`agenttel-genai`	`io.agenttel:agenttel-genai`	GenAI instrumentation — LangChain4j wrappers, Spring AI enrichment, Anthropic/OpenAI/Bedrock SDK instrumentation, cost calculation.
`agenttel-agent`	`io.agenttel:agenttel-agent`	Agent interface layer — MCP server, health aggregation, incident context, remediation, trend analysis, SLO reports, executive summaries, cross-stack context.
`agenttel-javaagent-extension`	`io.agenttel:agenttel-javaagent-extension`	Zero-code OTel javaagent extension. Drop-in enrichment for any JVM app — no Spring dependency.
`agenttel-spring-boot-starter`	`io.agenttel:agenttel-spring-boot-starter`	Spring Boot auto-configuration. Single dependency for Spring Boot apps.
`agenttel-web`	`@agenttel/web` (npm)	Browser telemetry SDK — auto-instrumentation of page loads, navigation, API calls, errors, Web Vitals, journey tracking, anomaly detection, W3C trace propagation.
`agenttel-instrument`	`agenttel-instrument` (pip)	IDE MCP server — codebase analysis, config generation, validation, improvement suggestions, and auto-apply for both backend and frontend instrumentation.
`agenttel-testing`	`io.agenttel:agenttel-testing`	Test utilities for verifying span enrichment.

Documentation

Full documentation site: rrohitramsen.github.io/AgentTel

Document	Description
Project Overview	Vision, motivation, and design philosophy
Semantic Conventions	Complete attribute and event schema reference
Architecture	Technical architecture, data flow, and extension points
Agent Layer	MCP server, incident context, remediation, and agent interaction
GenAI Instrumentation	LLM framework instrumentation and cost tracking
API Reference	Annotations, programmatic API, and configuration reference
Roadmap	Implementation phases and release plan
Design Considerations	Trade-offs, evolution path, and future direction
API Documentation	Swagger UI, MCP tool docs, and aggregated Javadoc

Examples

Working examples to get you started quickly:

Example	Description	Run Command
Spring Boot Example	Payment service with span enrichment, topology, baselines, anomaly detection, and MCP server	`./gradlew :examples:spring-boot-example:bootRun`
LangChain4j Example	GenAI tracing with LangChain4j — chat spans, token tracking, and cost calculation	`./gradlew :examples:langchain4j-example:run`
React Checkout Example	React SPA with frontend telemetry — journey tracking, anomaly detection, cross-stack correlation	`cd agenttel-web/examples/react-checkout && npm start`

Each example includes a README with step-by-step instructions and curl commands to exercise the instrumentation.

Compatibility

Backend (JVM)

Component	Supported Versions
Java	17, 21
OpenTelemetry SDK	1.59.0+
Spring Boot	3.4.x
Spring AI	1.0.0+ (optional)
LangChain4j	1.0.0+ (optional)
Anthropic Java SDK	2.0.0+ (optional)
OpenAI Java SDK	4.0.0+ (optional)
AWS Bedrock SDK	2.30.0+ (optional)

Frontend (Browser)

Component	Supported Versions
TypeScript	4.7+
Modern browsers	Chrome, Firefox, Safari, Edge (ES2020+)
React (example)	18+

Tooling

Component	Supported Versions
Python (instrument agent)	3.11+

Build Tool Support

AgentTel publishes standard Maven artifacts to Maven Central. Your application can use any build tool — Maven, Gradle, sbt, Bazel, or anything that resolves Maven dependencies.

Maven

<dependency>
    <groupId>io.agenttel</groupId>
    <artifactId>agenttel-spring-boot-starter</artifactId>
    <version>0.1.0-alpha</version>
</dependency>

Gradle (Kotlin DSL)

implementation("io.agenttel:agenttel-spring-boot-starter:0.1.0-alpha")

Gradle (Groovy DSL)

implementation 'io.agenttel:agenttel-spring-boot-starter:0.1.0-alpha'

All Available Artifacts

Maven/Gradle (JVM):

Group ID	Artifact ID	Description
`io.agenttel`	`agenttel-api`	Annotations and constants (zero dependencies)
`io.agenttel`	`agenttel-core`	Runtime engine
`io.agenttel`	`agenttel-genai`	GenAI instrumentation
`io.agenttel`	`agenttel-agent`	Agent interface layer (MCP, health, incidents, reporting)
`io.agenttel`	`agenttel-javaagent-extension`	Zero-code OTel javaagent extension
`io.agenttel`	`agenttel-spring-boot-starter`	Spring Boot auto-configuration
`io.agenttel`	`agenttel-testing`	Test utilities

npm (Browser):

Package	Description
`@agenttel/web`	Browser telemetry SDK with auto-instrumentation

pip (Tooling):

Package	Description
`agenttel-instrument`	IDE MCP server for instrumentation automation

Zero-Code Mode (JavaAgent Extension)

For applications where you cannot add a library dependency, use the javaagent extension. No code changes, no Spring dependency:

java -javaagent:opentelemetry-javaagent.jar \
     -Dotel.javaagent.extensions=agenttel-javaagent-extension.jar \
     -Dagenttel.config.file=agenttel.yml \
     -jar myapp.jar

The extension reads configuration from agenttel.yml (same YAML format as above), system properties (-Dagenttel.topology.team=payments), or environment variables (AGENTTEL_TOPOLOGY_TEAM=payments). It registers as an OTel AutoConfigurationCustomizerProvider via SPI, adding topology to the Resource and enriching spans with baselines and decisions.

FAQ

See FAQ.md for frequently asked questions about code changes, performance, telemetry size, compatibility, and more.

Building from Source

# Requires JDK 17+
./gradlew clean build

# Run tests only
./gradlew test

# Build a specific module
./gradlew :agenttel-agent:build

Contributing

Contributions are welcome. Please read the Contributing Guide for build instructions, PR guidelines, and code style conventions. See the Architecture document for design guidance.

For security issues, please see our Security Policy.

License

AgentTel is released under the Apache License 2.0.

Name		Name	Last commit message	Last commit date
Latest commit History 43 Commits
.github		.github
agenttel-agent		agenttel-agent
agenttel-api		agenttel-api
agenttel-core		agenttel-core
agenttel-genai		agenttel-genai
agenttel-instrument		agenttel-instrument
agenttel-javaagent-extension		agenttel-javaagent-extension
agenttel-spring-boot-starter		agenttel-spring-boot-starter
agenttel-testing		agenttel-testing
agenttel-web		agenttel-web
dashboards		dashboards
docs		docs
examples		examples
gradle		gradle
src/javadoc		src/javadoc
.dockerignore		.dockerignore
.gitignore		.gitignore
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
FAQ.md		FAQ.md
LICENSE		LICENSE
README.md		README.md
SECURITY.md		SECURITY.md
build.gradle.kts		build.gradle.kts
gradlew		gradlew
gradlew.bat		gradlew.bat
mkdocs.yml		mkdocs.yml
settings.gradle.kts		settings.gradle.kts

License

rrohitramsen/AgentTel

Folders and files

Latest commit

History

Repository files navigation

The Problem

Design Philosophy

Quick Demo

What AgentTel Provides

Enriched Telemetry (agenttel-core)

Agent Interface Layer (agenttel-agent)

Frontend Telemetry (agenttel-web)

Instrumentation Agent (agenttel-instrument)

GenAI Instrumentation (agenttel-genai)

Quick Start

Backend: Spring Boot

1. Add Dependencies

2. Configure Your Service

3. Optional: Annotate for IDE Support

4. Start the MCP Server (Optional)

5. What You Get

Frontend: Browser SDK

IDE: Instrument Agent

Module Overview

Documentation

Examples

Compatibility

Backend (JVM)

Frontend (Browser)

Tooling

Build Tool Support

Maven

Gradle (Kotlin DSL)

Gradle (Groovy DSL)

All Available Artifacts

Zero-Code Mode (JavaAgent Extension)

FAQ

Building from Source

Contributing

License

About

Topics

Resources

License

Contributing

Security policy

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors 2

Languages

Packages