Skip to content

Feat(OTEL): Cache hit behavior #3807

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
lmilan merged 2 commits into from
Jan 6, 2026
Merged

Feat(OTEL): Cache hit behavior #3807

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
965e013
Add FAQ
lmilan Jan 5, 2026
8a8b80b
Update app/_kong_plugins/opentelemetry/index.md
lmilan Jan 6, 2026
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
8 changes: 8 additions & 0 deletions app/_kong_plugins/opentelemetry/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,14 @@ related_resources:
url: /plugins/zipkin/
- text: "{{site.base_gateway}} monitoring and metrics"
url: /gateway/monitoring/

faqs:
- q: Why am I not getting traces for my request when it results in a cache hit?
a: |
Since the [Proxy Caching Advanced](/plugins/proxy-cache-advanced/) plugin runs before the OpenTelemetry plugin, when a response results in a cache hit, the process ends before the OpenTelemetry plugin can run. This means that no traces are produced for that request.

If needed, you can use [dynamic plugin ordering](/gateway/entities/plugin/#dynamic-plugin-ordering) to run the OpenTelemetry plugin first, but be aware that this could impact performance.

---

The OpenTelemetry plugin provides metrics, traces, and logs in the OpenTelemetry format and can be used with any OpenTelemetry compatible backend.
Expand Down
Loading