Skip to content

Commit a611f24

Browse files
Merge pull request #330 from Portkey-AI/otel
otel + small changes
2 parents 2d965c3 + 1d236a2 commit a611f24

File tree

3 files changed

+53
-2
lines changed

3 files changed

+53
-2
lines changed

docs.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -163,6 +163,7 @@
163163
"product/enterprise-offering/access-control-management",
164164
"product/enterprise-offering/budget-limits",
165165
"product/enterprise-offering/security-portkey",
166+
"product/enterprise-offering/analytics-logs-export",
166167
"product/enterprise-offering/logs-export",
167168
"/product/enterprise-offering/audit-logs",
168169
{
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
title: Analytics Logs Export
3+
---
4+
5+
Portkey supports exporting your Analytics data to OpenTelemetry (OTEL) compatible collectors, allowing you to integrate Portkey's analytics with your existing observability infrastructure.
6+
7+
## Overview
8+
9+
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.
10+
11+
## Configuration
12+
13+
Portkey supports pushing your analytics data to an OTEL compatible endpoint. The following environment variables are needed for pushing to OTEL:
14+
15+
```yaml
16+
OTEL_PUSH_ENABLED: true
17+
OTEL_ENDPOINT: http://localhost:4318
18+
```
19+
20+
Additionally, you can configure arbitrary resource attributes of the OTEL logs by setting a comma-separated value for `OTEL_RESOURCE_ATTRIBUTES`:
21+
22+
```
23+
OTEL_RESOURCE_ATTRIBUTES: ApplicationShortName=gateway,AssetId=12323,deployment.service=production
24+
```
25+
26+
## Integration Options
27+
28+
Enterprise customers commonly use these analytics exports with:
29+
30+
- **Datadog**: Monitor and analyze your AI operations alongside other application metrics
31+
- **AWS S3**: Store analytics data for long-term retention and analysis
32+
- **Other OTEL-compatible systems**: Any system that can ingest OpenTelemetry data can be used with this feature
33+
34+
## Use Cases
35+
36+
This feature enables:
37+
38+
- Centralized observability across your entire tech stack
39+
- Long-term storage of analytics data
40+
- Custom analytics dashboards in your preferred tools
41+
- Integration with existing alerting systems
42+
43+
## Getting Support
44+
45+
For additional assistance with setting up analytics data export:
46+
47+
- Join our [Discord community](https://portkey.sh/reddit-discord)
48+
- Email us at [email protected]
49+
50+
Our team can help you with best practices for configuring your OTEL collectors and integrating with your existing systems.

product/guardrails/creating-raw-guardrails-in-json.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ With the Raw Guardrails mode, you can achieve all this.
1414
### Example of a Raw Guardrail
1515

1616
```JSON
17-
"beforeRequestHooks": [{
17+
"before_request_hooks": [{
1818
"type": "guardrail",
1919
"id": "my_solid_guardrail",
2020
"checks": [{
@@ -35,7 +35,7 @@ In this example:
3535
### Configuring Guardrail Actions
3636

3737
```JSON
38-
"beforeRequestHooks": [{
38+
"before_request_hooks": [{
3939
"type": "guardrail",
4040
"id": "my_solid_guardrail",
4141
"checks": [{

0 commit comments

Comments
 (0)