homelab/traefik
1
0
Fork 0
Code Activity

Fix heading levels and add links

Browse source
This commit is contained in:
Simon A. Eugster 2025-10-03 10:52:04 +02:00 • committed by GitHub
parent 5f415615eb
commit 83b28270a4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 9 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/content/reference/routing-configuration/http/load-balancing/service.md
View file

@ -3,13 +3,16 @@ title: "Traefik HTTP Services Documentation"
description: "A service is in charge of connecting incoming requests to the Servers that can handle them. Read the technical documentation." description: "A service is in charge of connecting incoming requests to the Servers that can handle them. Read the technical documentation."
--- ---
Traefik services define how to distribute incoming traffic across your backend servers.
Each service implements one of the load balancing strategies detailed on this page to ensure optimal traffic distribution and high availability.
## Service Load Balancer ## Service Load Balancer
The load balancers are able to load balance the requests between multiple instances of your programs. The load balancers are able to load balance the requests between multiple instances of your programs.
Each service has a load-balancer, even if there is only one server to forward traffic to. Each service has a load-balancer, even if there is only one server to forward traffic to.
## Configuration Example ### Configuration Example
```yaml tab="Structured (YAML)" ```yaml tab="Structured (YAML)"
http: http:

7
docs/content/reference/routing-configuration/http/routing/observability.md
View file

@ -5,11 +5,14 @@ description: "You can disable access logs, metrics, and tracing for a specific e
Traefik's observability features include logs, access logs, metrics, and tracing. You can configure these options globally or at more specific levels, such as per router or per entry point. Traefik's observability features include logs, access logs, metrics, and tracing. You can configure these options globally or at more specific levels, such as per router or per entry point.
By default, the router observability configuration is inherited from the attached EntryPoints and can be configured with the observability [options](../../../install-configuration/entrypoints.md#configuration-options)). By default, the router observability configuration is inherited from the attached EntryPoints and can be configured with the observability [options](../../../install-configuration/entrypoints.md#configuration-options).
However, a router defining its own observability configuration will opt-out from these defaults. However, a router defining its own observability configuration will opt-out from these defaults.
!!! info !!! info
To enable router-level observability, you must first enable access-logs, tracing, and metrics. To enable router-level observability, you must first enable
[access-logs](../../../install-configuration/observability/logs-and-accesslogs.md#accesslogs),
[tracing](../../../install-configuration/observability/tracing.md),
and [metrics](../../../install-configuration/observability/metrics.md).
When metrics layers are not enabled with the `addEntryPointsLabels`, `addRoutersLabels` and/or `addServicesLabels` options, When metrics layers are not enabled with the `addEntryPointsLabels`, `addRoutersLabels` and/or `addServicesLabels` options,
enabling metrics for a router will not enable them. enabling metrics for a router will not enable them.