Skip to content
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

[docs] Add status header for loadbalancing exporter #10323

Merged
merged 3 commits into from
Jun 9, 2022
Merged

[docs] Add status header for loadbalancing exporter #10323

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
11c3a11
Add status header for loadbalancing
Frapschen May 25, 2022
53020c3
Apply suggestions from code review
Frapschen May 25, 2022
fab79a2
update for reviewer's suggestion
Frapschen May 25, 2022
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
10 changes: 9 additions & 1 deletion exporter/loadbalancingexporter/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,10 @@
# Trace ID aware load-balancing exporter

Supported pipeline types: traces, logs
| Status | |
| ------------------------ |--------------|
| Stability | [beta] |
| Supported pipeline types | traces, logs |
| Distributions | [contrib] |

This is an exporter that will consistently export spans and logs belonging to the same trace to the same backend.

Expand Down Expand Up @@ -184,3 +188,7 @@ The following metrics are recorded by this processor:
* `otelcol_loadbalancer_num_backend_updates` records how many of the resolutions resulted in a new list of backends. Use this information to understand how frequent your backend updates are and how often the ring is rebalanced. If the DNS hostname is always returning the same list of IP addresses but this metric keeps increasing, it might indicate a bug in the load balancer.
* `otelcol_loadbalancer_backend_latency` measures the latency for each backend.
* `otelcol_loadbalancer_backend_outcome` counts what the outcomes were for each endpoint, `success=true|false`.


[beta]:https://github.com/open-telemetry/opentelemetry-collector#beta
[contrib]:https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib