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: docs/send-data/opentelemetry-collector/remote-management/st-with-secrets.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,9 @@ Below are the steps to make things work for such source templates:
20
20
1. Set env variable in OpenTelemetry Collector process. For example: `SECRET_ENV_VAR=Welcome@123`, where `SECRET_ENV_VAR` is the variable name and `Welcome@123` is the password.
21
21
2. ST creation: While creating the source template you will need to provide the environment variable name instead of the actual password. In this case: `SECRET_ENV_VAR` and this will be part of the source template referring to the value of the environment variable like: `password: ${env:SECRET_ENV_VAR}`.
22
22
3. Once this source template gets pushed to the respective OpenTelemetry collector, the environment variable will get resolved at runtime and will be substituted with the actual password value to make the config work and pull the data to send it to Sumo Logic.
23
-
^[a-zA-Z_][a-zA-Z0-9_]*$
23
+
24
24
:::note
25
-
Environment variable can start with small or capital character or an underscore(_) followed by any letters(small or capital), numbers and underscore.
25
+
Environment variable should start with small or capital character or an underscore(_) followed by any letters(small or capital), numbers and underscore.
26
26
:::
27
27
28
28
This way, your secret data is not shared with Sumo Logic.
0 commit comments