Skip to content

docs: add tencent apm as new integration #110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 11, 2025
Merged

docs: add tencent apm as new integration #110

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added img/integrations/tencent.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
22 changes: 22 additions & 0 deletions openllmetry/integrations/tencent.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
title: "LLM Observability with Tencent APM and OpenLLMetry"
sidebarTitle: "Tencent Cloud"
---

[Tencent APM](https://console.tencentcloud.com/apm) is a monitoring and observability platform that provides a comprehensive view of your application's performance and behavior.

Tencent APM(also known as `TAPM`) natively supports OpenTelemetry, so you can use OpenLLMetry to trace your applications on this platform.

<Frame>
<img src="/img/integrations/tencent.png" />
</Frame>

To integrate OpenLLMetry with Tencent APM, you'll need to configure your tracing endpoint and authentication:


```bash
TRACELOOP_BASE_URL="<TAPM_ENDPOINT>" # Use port `55681` rather than `4317` as the default port.
TRACELOOP_HEADERS="Authorization=Bearer%20<TAPM_TOKEN>" # header values in env variables must be URL‑encoded.
```
Comment on lines +18 to +20
Copy link
Contributor

@coderabbitai coderabbitai bot Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Incorrect OTLP HTTP port (55681 is legacy); use 4318 and include /v1/traces.

OTLP/HTTP’s default port is 4318 (not 55681). 55681 was used historically and is deprecated. Also, for OTLP/HTTP the traces path should be /v1/traces. Recommend updating the example and note accordingly. (opentelemetry.io)

Apply this diff:

-TRACELOOP_BASE_URL="<TAPM_ENDPOINT>" # Use port `55681` rather than `4317` as the default port.
-TRACELOOP_HEADERS="Authorization=Bearer%20<TAPM_TOKEN>" # header values in env variables must be URL‑encoded.
+TRACELOOP_BASE_URL="https://<TAPM_HOST>:4318/v1/traces" # OTLP/HTTP default port is 4318; include /v1/traces.
+TRACELOOP_HEADERS="Authorization=Bearer%20<TAPM_TOKEN>" # header values in env variables must be URL‑encoded.
-Tencent APM defaults to using port `4317` for the gRPC exporter; we recommend using port `55681` instead, which is the HTTP exporter port.
+Tencent APM defaults to using port `4317` for OTLP/gRPC. If you use OTLP/HTTP, use port `4318` (the OTLP/HTTP default) and include the `/v1/traces` path.

Also applies to: 22-22

🤖 Prompt for AI Agents 
In openllmetry/integrations/tencent.mdx around lines 18-20 (and also line 22),
update the OTLP/HTTP example to use the current default port 4318 instead of the
deprecated 55681 and ensure the endpoint includes the traces path /v1/traces
(e.g., TRACELOOP_BASE_URL should point to
http(s)://<TAPM_ENDPOINT>:4318/v1/traces); keep the URL-encoding note for
TRACELOOP_HEADERS but adjust the example values and any accompanying text to
reflect the correct port and path.


Tencent APM defaults to using port `4317` for the gRPC exporter; we recommend using port `55681` instead, which is the HTTP exporter port.