You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: opentelemetry/README.md
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ The main terminologies used in this document can be found in [core-concepts](htt
10
10
11
11
OpenTelemetry is an observability framework and toolkit for creating and managing telemetry data such as metrics, logs and traces. Unlike other observability tools, OpenTelemetry is vendor and tool agnostic, meaning it can be used with a variety of observability backends, including open source tools such as _OpenSearch_ and _Prometheus_.
12
12
13
-
The focus of the plugin is to provide easy-to-use configurations for common use cases of receiving, processing and exporting telemetry data in Kubernetes. The storage and visualization of the same is intentionally left to other tools.
13
+
The focus of the Plugin is to provide easy-to-use configurations for common use cases of receiving, processing and exporting telemetry data in Kubernetes. The storage and visualization of the same is intentionally left to other tools.
14
14
15
15
Components included in this Plugin:
16
16
@@ -21,6 +21,7 @@ Components included in this Plugin:
@@ -45,7 +46,7 @@ This guide provides a quick and straightforward way to use **OpenTelemetry** as
45
46
**Step 1:**
46
47
47
48
You can install the `OpenTelemetry` package in your cluster by installing it with [Helm](https://helm.sh/docs/helm/helm_install) manually or let the Greenhouse platform lifecycle do it for you automatically. For the latter, you can either:
48
-
1. Go to Greenhouse dashboard and select the **OpenTelemetry**plugin from the catalog. Specify the cluster and required option values.
49
+
1. Go to Greenhouse dashboard and select the **OpenTelemetry**Plugin from the catalog. Specify the cluster and required option values.
49
50
2. Create and specify a `Plugin` resource in your Greenhouse central cluster according to the [examples](#examples).
50
51
51
52
**Step 2:**
@@ -70,6 +71,10 @@ Based on the backend selection the telemetry data will be exporter to the backen
70
71
71
72
Greenhouse regularly performs integration tests that are bundled with **OpenTelemetry**. These provide feedback on whether all the necessary resources are installed and continuously up and running. You will find messages about this in the plugin status and also in the Greenhouse dashboard.
72
73
74
+
## Failover Connector
75
+
76
+
The **OpenTelemetry** Plugin comes with a [Failover Connector](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/failoverconnector) for OpenSearch for two users. The connector will periodically try to establish a stable connection for the prefered user (`failover_username_a`) and in case of a failed try, the connector will try to establish a connection with the fallback user (`failover_username_b`). This feature can be used to secure the shipping of logs in case of expiring credentials or password rotation.
77
+
73
78
## Configuration
74
79
75
80
| Name | Description | Type | required |
@@ -78,9 +83,12 @@ Greenhouse regularly performs integration tests that are bundled with **OpenTele
78
83
`openTelemetry.logsCollector.kvmConfig.enabled` | Activates the configuration for KVM logs (requires logsCollector to be enabled) | bool | `false` |
79
84
`openTelemetry.logsCollector.cephConfig.enabled` | Activates the configuration for Ceph logs (requires logsCollector to be enabled) | bool | `false` |
80
85
`openTelemetry.metricsCollector.enabled` | Activates the standard configuration for metrics | bool | `false` |
0 commit comments