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: cmd/opampsupervisor/README.md
+46-33Lines changed: 46 additions & 33 deletions
Original file line number
Diff line number
Diff line change
@@ -4,36 +4,50 @@ This is an implementation of an OpAMP Supervisor that runs a Collector instance
4
4
is following a design specified [here](./specification/README.md).
5
5
The design is still undergoing changes, and as such this implementation may change as well.
6
6
7
-
## Experimenting with the supervisor
7
+
Binary and container images for the Supervisor are available under tags starting with `cmd/opampsupervisor`[here](https://github.com/open-telemetry/opentelemetry-collector-releases/tags).
8
8
9
-
The supervisor is currently undergoing heavy development and is not ready for any serious use. However, if you would like to test it, you can follow the steps below:
9
+
## More information.
10
10
11
-
1. Download the [opamp-go](https://github.com/open-telemetry/opamp-go) repository, and run the OpAMP example server in the `internal/examples/server` directory.
3. Run the supervisor in the `cmd/opampsupervisor` directory of Collector contrib repository, substituting `<OS>` for your operating system (`darwin` for MacOS, `linux` or `windows`):
31
+
1. A Supervisor binary, which can be obtained through the link above.
32
+
2. A Collector binary that you would like to control through the Supervisor.
33
+
3. A Supervisor config file. See examples [here](./examples/).
34
+
4. A running OpAMP server.
35
+
36
+
To test the Supervisor with an example server, download the
37
+
[opamp-go](https://github.com/open-telemetry/opamp-go) repository, and run the
38
+
OpAMP example server in the `internal/examples/server` directory.
4. The supervisor should connect to the OpAMP server and start a Collector instance.
46
+
Visit [localhost:4321](http://localhost:4321) to verify that the server is running.
47
+
35
48
36
49
## Persistent data storage
50
+
37
51
The supervisor persists some data to disk in order to mantain state between restarts. The directory where this data is stored may be specified via the supervisor configuration:
38
52
```yaml
39
53
storage:
@@ -59,34 +73,33 @@ For a list of open issues related to the Supervisor, see [these issues](https://
| Offers Supervisor configuration including configuring capabilities | ✅ |
87
-
| Starts and stops a Collector using remote configuration | ⚠️ |
88
-
| Communicates with OpAMP extension running in the Collector | <https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/21071> |
89
-
| Updates the Collector binary | 📅 |
90
-
| Configures the Collector to report it's own metrics over OTLP | 📅 |
91
-
| Configures the Collector to report it's own logs over OTLP | 📅 |
100
+
| Starts and stops a Collector using remote configuration | ✅ |
101
+
| Communicates with OpAMP extension running in the Collector | ✅ |
102
+
| Updates the Collector binary | <https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/33947> |
103
+
| Configures the Collector to report it's own metrics over OTLP | ✅ |
104
+
| Configures the Collector to report it's own logs over OTLP | ✅ |
92
105
| Sanitization or restriction of Collector config | <https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/24310> |
Copy file name to clipboardExpand all lines: extension/azureauthextension/README.md
+1-8Lines changed: 1 addition & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@
11
11
<!-- end autogenerated section -->
12
12
13
13
This extension implements both `extensionauth.HTTPClient` and `extensionauth.Server`, so it can be used in both exporters and receivers.
14
+
**Currently, this part is still not implemented.**
14
15
15
16
Additionally, the extension also implements `azcore.TokenCredential` so that Azure components can get the token by running the function `GetToken`. If the component supports HTTP client, then this should not be necessary, as the token will be placed in the authorization header.
16
17
@@ -20,8 +21,6 @@ It supports 4 different types of authentication:
20
21
- Service principal with either a client secret or client certificate path for non Azure.
21
22
- And the default credentials. This is not recommended for production.
22
23
23
-
Each type of authentication requires the [scope of the permissions](https://learn.microsoft.com/en-us/entra/identity-platform/scopes-oidc) for the token.
24
-
25
24
## Examples
26
25
27
26
### Managed identity
@@ -30,7 +29,6 @@ User based:
30
29
```yaml
31
30
extensions:
32
31
azureauth:
33
-
scope: https://management.azure.com/.default
34
32
managed_identity:
35
33
client_id: ${CLIENT_ID}
36
34
```
@@ -39,7 +37,6 @@ System based (leave `client_id` field empty):
0 commit comments