chore: otel docs

Author: sk-portkey

changelog/2025/apr.mdx

@@ -40,7 +40,7 @@ Read more about this [here](https://portkey.ai/docs/api-reference/admin-api/cont
 
 **Export logs to your internal stack**
 
-Enterprises can now push analytics logs to any OTEL-compliant store through Portkey to centralize monitoring, maintain compliance, and ensure efficient operations.
+Enterprises can now push analytics logs to any OTel-compliant store through Portkey to centralize monitoring, maintain compliance, and ensure efficient operations.
 See how it's done [here](https://portkey.ai/docs/product/enterprise-offering/components#analytics-store)
 
 **Budget limits and rate limts on workspace**

changelog/2025/august.mdx

@@ -7,15 +7,15 @@ Princeton and NYU shared how they're deploying Portkey across their institutions
 
 **Future of AI Platforms** brought together industry leaders from Doordash, Postman, Qure.ai and more for honest conversations about challenges and opportunities.
 
-Meanwhile, we shipped what you asked for: multiple workspace guardrails, OTEL instrumentation, and day-zero support for the latest models.
+Meanwhile, we shipped what you asked for: multiple workspace guardrails, OTel instrumentation, and day-zero support for the latest models.
 
 Here's what's new this month:
 ## Summary
 
 | Area | Key Highlights |
 | :--- | :------------ |
 | **Highlights** | • Making GenAI rollout easy with Princeton, NYU and Internet2 <br/> • Upcoming Palo Alto Networks webinar <br/> • New `/models` endpoint |
-| **Platform** | • Unified + Portkey batching <br/> • OTEL-based auto-instrumentation <br/> • Multiple guardrails at workspace level <br/> • CRUD Guardrails API |
+| **Platform** | • Unified + Portkey batching <br/> • OTel-based auto-instrumentation <br/> • Multiple guardrails at workspace level <br/> • CRUD Guardrails API |
 | **Gateway & Providers** | • Featherless.ai integration <br/> • GPT-OSS models support <br/> • Claude Opus 4.1 support <br/> • Custom models and pricing |
 
 ## Highlights
@@ -50,11 +50,11 @@ This reduces per-request overhead while providing automatic batch size optimizat
 
 See how you can get started [here](http://localhost:3000/product/ai-gateway/batches).
 
-### **OTEL-based autoinstrumentation**
+### **OTel-based autoinstrumentation**
 <video
     src="https://cfassets.portkey.ai/WEBSITE%2FPRODUCT%20PAGES%2FOVSERVABILITY%2FObservibility_point_3.mp4"
     controls
-    title="OTEL-based Autoinstrumentation Demo"
+    title="OTel-based Autoinstrumentation Demo"
     style={{ width: "100%", borderRadius: "8px", margin: "24px 0" }}
 />
 Portkey now works as an OTel endpoint. Send telemetry from any OTel-compatible source into Portkey and view it alongside LLM call logs. End-to-end observability for performance, cost, and compliance. Super powerful for agent workflows. 

changelog/2025/november.mdx

@@ -17,7 +17,7 @@ We’re closing the year with conversations and gatherings across the community!
 |---|---|
 | **Models & Providers** | • GPT-5.1 <br />• Gemini 3.0<br />• Claude Opus 4.5 <br />• New providers: Z-AI, MatterAI, CometAPI, Modal Labs |
 | **Platform** | • Conditioner Router now supports URL-based conditions<br />• Usage limits & rate-limit policies for org-wide control |
-| **Observability** | • Trace visibility by category<br />• Guardrail checks highlighted in logs<br />• OTEL log export |
+| **Observability** | • Trace visibility by category<br />• Guardrail checks highlighted in logs<br />• OTel log export |
 | **Guardrails** | • F5 Guardrail added<br />• Javelin Guardrails added <br /> • Guardrails for streaming responses|
 
 ## How Snorkel AI runs multi-agents evals for frontier models
@@ -66,7 +66,7 @@ See guardrail-flagged events more prominently in logs, simplifying debugging of
 
 <img src="/images/changelog/guardrails-logs.png" alt="guardrails-checks-in-logs" style={{maxWidth: "80%", borderRadius: "8px", margin: "24px 0"}} />
 
-### OTEL Log Export [Experimental]
+### OTel Log Export [Experimental]
 
 You can now export Gateway logs to an OpenTelemetry-compatible endpoint, aligned to experimental GenAI semantic conventions, allowing external systems to ingest AI activity traces. Read more about this [here](https://portkey.ai/docs/product/observability/opentelemetry#experimental-features).
 

changelog/2025/september.mdx

@@ -155,7 +155,7 @@ New provider focused on efficient inference for specialized workloads
 * **Azure Foundry** → You can now enable multiple models in a single Azure Foundry integration. This simplifies management and makes it easier to experiment with different models under the same integration, without repetitive setup.
 
 * Support custom scope for entra auth to use with deprecated azure serverless models
-* Custom Header support for OTEL Export of analytics data
+* Custom Header support for OTel Export of analytics data
 
 
 🚨 **Vertex AI deprecation** → Llama 3.1 + 3.2 models will be retired on Jan 15, 2026. Recommended migration: Llama 3.3 or Llama 4.

changelog/enterprise.mdx

@@ -413,7 +413,7 @@ Discuss how Portkey's AI Gateway can enhance your organization's AI infrastructu
 
 ### Fixes and Improvements
 - Enhancements for token rate limiter to handle small limit values
-- Fixed status code and timestamp handling for OTEL `http/protobuf` transport protocol
+- Fixed status code and timestamp handling for OTel `http/protobuf` transport protocol
 - Fixed an issue with `multipart/form-data` requests when the data contained a `model` field
 - Added support for multiple checks of same type under a single guardrail
 
@@ -468,7 +468,7 @@ Discuss how Portkey's AI Gateway can enhance your organization's AI infrastructu
 ## v1.15.5
 ---
 
-### OTEL Exporter Enhancements
+### OTel Exporter Enhancements
 - Added support for `http/protobuf` transport protocol.
 - Set `OTEL_EXPORTER_OTLP_PROTOCOL` environment variable to `http/protobuf` to use this.
 
@@ -512,7 +512,7 @@ Discuss how Portkey's AI Gateway can enhance your organization's AI infrastructu
 ### New Features
 - KMS Support for file uploads to bedrock/AWS.
 - Support custom scope for entra auth to use with deprecated azure serverless models.
-- Custom Header support for OTEL Export of analytics data
+- Custom Header support for OTel Export of analytics data
 
 
 ### Improvements and Fixes
@@ -894,8 +894,8 @@ Discuss how Portkey's AI Gateway can enhance your organization's AI infrastructu
 - **Azure**: Added support for custom hosts and private links for Azure Plugins
 - **Bedrock**: Added native support for `inference profiles` [Ref](https://docs.aws.amazon.com/bedrock/latest/userguide/inference-profiles-use.html)
 
-### OTEL Traces Collector endpoints
-- Added new endpoint `/v1/otel/v1/traces` to collect any OTEL traces as Portkey traces
+### OTel Traces Collector endpoints
+- Added new endpoint `/v1/otel/v1/traces` to collect any OTel traces as Portkey traces
 
 ### Log Exports available on Data Plane
 - Log exports are now available on Data Plane
@@ -944,7 +944,7 @@ Discuss how Portkey's AI Gateway can enhance your organization's AI infrastructu
 - Applicable for Anthropic, Bedrock-Anthropic and VertexAI-Anthropic models.
 - [Docs](/integrations/llms/anthropic#processing-pdfs-with-claude)
 
-### OTEL Configurations
+### OTel Configurations
 - Added two new environment variables:
     - `OTEL_SERVICE_NAME`: Sets the `service.name` resource attribute value.
     - `OTEL_RESOURCE_ATTRIBUTES`: Comma-separated `key=value` pairs which will be sent as individual resource attributes.
@@ -1023,9 +1023,9 @@ Discuss how Portkey's AI Gateway can enhance your organization's AI infrastructu
 ## v1.10.19
 ---
 
-### OTEL Metrics Push
-- Added support for pushing Portkey Clickhouse analytics (traces and spans) to OTEL collector.
-- The following environment variables will be used to configure OTEL collector:
+### OTel Metrics Push
+- Added support for pushing Portkey Clickhouse analytics (traces and spans) to OTel collector.
+- The following environment variables will be used to configure OTel collector:
     - `OTEL_PUSH_ENABLED`
     - `OTEL_ENDPOINT`
 
@@ -1065,9 +1065,9 @@ We are redacting this release and will be releasing a patch with out Workspace B
 - Organisations can now enforce usage limits for each workspace
 - Organisations can now enforce rate limits for each workspace
 
-### OTEL Metrics Push
-- Added support for pushing Portkey Clickhouse analytics (traces and spans) to OTEL collector.
-- The following environment variables will be used to configure OTEL collector:
+### OTel Metrics Push
+- Added support for pushing Portkey Clickhouse analytics (traces and spans) to OTel collector.
+- The following environment variables will be used to configure OTel collector:
     - `OTEL_PUSH_ENABLED`
     - `OTEL_ENDPOINT`
 

docs.json

@@ -194,7 +194,14 @@
                       "product/enterprise-offering/access-control-management",
                       "product/enterprise-offering/budget-limits",
                       "product/enterprise-offering/security-portkey",
-                      "product/enterprise-offering/analytics-logs-export",
+                      {
+                        "group": "OpenTelemetry(OTel)",
+                        "pages": [
+                          "product/enterprise-offering/otel/otel",
+                          "product/enterprise-offering/otel/analytics",
+                          "product/enterprise-offering/otel/complete-logs"
+                        ]
+                      },
                       "product/enterprise-offering/logs-export",
                       "/product/enterprise-offering/audit-logs",
                       "product/enterprise-offering/budget-policies",

integrations/agents/pydantic-ai.mdx

@@ -563,7 +563,7 @@ For comprehensive monitoring and observability, Portkey supports OpenTelemetry i
 ```python
 import openlit
 
-# Initialize OpenLit with Portkey's OTEL endpoint
+# Initialize OpenLit with Portkey's OTel endpoint
 openlit.init(
     otlp_endpoint="https://api.portkey.ai/v1/otel",
     otlp_headers={

product/enterprise-offering/analytics-logs-export.mdx

@@ -15,7 +15,7 @@ Portkey leverages Clickhouse as the primary Analytics Store for the Control Pane
 </CardGroup>
 
 <Note>
-  Portkey supports exporting your Clickhouse analytics data to OpenTelemetry (OTEL) compatible collectors, allowing you to integrate Portkey's analytics with your existing observability infrastructure.
+  Portkey supports exporting your Clickhouse analytics data to OpenTelemetry (OTel) compatible collectors, allowing you to integrate Portkey's analytics with your existing observability infrastructure.
 </Note>
 
 

product/enterprise-offering/components.mdx

@@ -0,0 +1,84 @@
+---
+title: Analytics Export
+sidebarTitle: Analytics
+description: Export Portkey analytics data to OpenTelemetry-compatible collectors for centralized observability
+---
+
+Portkey supports sending your Analytics data to OpenTelemetry (OTel) compatible collectors, allowing you to integrate Portkey's analytics with your existing observability infrastructure.
+
+## Overview
+
+While Portkey leverages Clickhouse as the primary Analytics Store for the Control Panel by default, enterprise customers can integrate Portkey's analytics data with their existing data infrastructure through OpenTelemetry.
+
+This export focuses on **aggregated metrics and analytics data** such as:
+
+- Request counts and latency metrics
+- Token usage statistics
+- Cost tracking data
+- Error rates and status codes
+
+<Note>
+  For exporting complete request/response logs with full prompt and completion content, see [Complete Logs Export](/product/enterprise-offering/otel/complete-logs).
+</Note>
+
+## Configuration
+
+Portkey supports pushing your analytics data to an OTel compatible endpoint. The following environment variables are needed for pushing to OTel:
+
+```yaml
+OTEL_PUSH_ENABLED: true
+OTEL_ENDPOINT: http://localhost:4318
+OTEL_EXPORTER_OTLP_HEADERS: x-api-key=my-api-key,x-another-header=value
+```
+
+### Environment Variables
+
+| Variable | Required | Description |
+|----------|----------|-------------|
+| `OTEL_PUSH_ENABLED` | Yes | Set to `true` to enable analytics export |
+| `OTEL_ENDPOINT` | Yes | The OTLP endpoint URL |
+| `OTEL_EXPORTER_OTLP_HEADERS` | No | Comma-separated headers in `key=value` format |
+
+### Resource Attributes
+
+You can configure arbitrary resource attributes of the OTel logs by setting a comma-separated value for `OTEL_RESOURCE_ATTRIBUTES`:
+
+```yaml
+OTEL_SERVICE_NAME: portkey-gateway
+OTEL_RESOURCE_ATTRIBUTES: ApplicationShortName=gateway,AssetId=12323,deployment.service=production
+```
+
+| Variable | Description |
+|----------|-------------|
+| `OTEL_SERVICE_NAME` | Service name for the telemetry data |
+| `OTEL_RESOURCE_ATTRIBUTES` | Comma-separated key=value pairs for additional resource attributes |
+
+## Integration Options
+
+Enterprise customers commonly use these analytics exports with:
+
+- **Datadog**: Monitor and analyze your AI operations alongside other application metrics
+- **AWS S3**: Store analytics data for long-term retention and analysis
+- **Prometheus/Grafana**: Build custom dashboards and alerting
+- **Splunk**: Integrate with existing SIEM infrastructure
+- **Other OTel-compatible systems**: Any system that can ingest OpenTelemetry data
+
+## Use Cases
+
+This feature enables:
+
+- Centralized observability across your entire tech stack
+- Long-term storage of analytics data
+- Custom analytics dashboards in your preferred tools
+- Integration with existing alerting systems
+- Compliance and audit trail requirements
+
+## Getting Support
+
+For additional assistance with setting up analytics data export:
+
+- Join our [Discord community](https://portkey.sh/reddit-discord)
+- Email us at support@portkey.ai
+
+Our team can help you with best practices for configuring your OTel collectors and integrating with your existing systems.
+