observability-features

Configure Edgion access logs, protocol-specific SSL/TCP/TLS/UDP logs, and Prometheus metrics endpoints.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pandaala/Edgion --skill observability-features
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: observability-features
Source: https://github.com/Pandaala/Edgion/tree/main/skills/02-features/04-observability
Command: npx skills add https://github.com/Pandaala/Edgion --skill observability-features

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure Edgion’s observability outputs so you can quickly understand request behavior, TLS/session issues, and operational health without guesswork.

Core Features & Use Cases

  • Access log for every request: generates one JSON-formatted entry containing request identifiers, routing results, status, duration, upstream address, and compact per-plugin stage logs.
  • Protocol-specific logs: separate configuration for SSL, TCP, TLS, and UDP logs using a shared schema to isolate problems by transport.
  • Prometheus metrics endpoints: exposes Gateway/Controller/Center metrics with clear conventions and label-cardinality guardrails to support safe alerting and troubleshooting.

Quick Start

Use the observability-features Skill to set up Access Log and Prometheus metrics for Edgion Gateway, then enable the protocol logs you need to diagnose issues for SSL/TCP/TLS/UDP traffic.

Frequently Asked Questions about observability-features

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

FAQPage Schema
How do I configure structured access logs for Edgion gateway requests?▼

Edgion access logs are configured to generate one JSON-formatted entry per request containing request identifiers, routing results, status, duration, upstream address, and compact per-plugin stage logs for debugging.

Can I capture protocol-specific logs for SSL, TCP, and UDP traffic in Edgion?▼

Yes, Edgion uses separate configuration for SSL, TCP, TLS, and UDP logs with a shared schema, allowing you to isolate problems by transport protocol during gateway debugging.

How do I expose Prometheus metrics endpoints for Edgion control-plane components?▼

Edgion exposes Gateway, Controller, and Center metrics endpoints with clear conventions and label-cardinality guardrails to support safe alerting and troubleshooting in Kubernetes or standalone deployments.

What is the best way to debug TLS session issues in an Edgion gateway?▼

Enable protocol-specific TLS logging in Edgion to capture session details using a shared schema, which isolates transport-level problems without guessing at request behavior.

Does Edgion observability configuration support both Kubernetes and standalone deployments?▼

Yes, Edgion observability features apply to both Kubernetes and standalone deployments, allowing you to configure access logs, protocol logs, and Prometheus metrics consistently across environments.

What should I use to investigate capacity and latency issues across HTTP and gRPC traffic in Edgion?▼

Use Edgion's Prometheus metrics endpoints with deterministic conventions and data-plane histogram restrictions to investigate capacity and latency across HTTP, gRPC, and stream protocols.