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/monitors/kubernetes_monitor.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,26 @@ fields behave differently when configured via k8s annotations:
30
30
* lineGroupers (not supported at all)
31
31
* path (the path is always fixed for k8s container logs)
32
32
33
+
### Configuring multiple accounts per container
34
+
35
+
Containers can be assigned one or more Scalyr API keys by specifying the `log.config.scalyr.com/{container_name}.teams.{team_number}.secret` annotation.
36
+
The `container_name` is the name of the container as specified in the pod spec, and the `team_number` is a unique number for each team.
37
+
The `secret` is the name of the secret holding the Scalyr API key for the team.
38
+
A default fallback api key can be specified by using the `log.config.scalyr.com/teams.{team_number}.secret` annotation.
39
+
The monitor first looks into the container specific annotation, and if not found, it falls back to the default annotation or the global configuration api key.
40
+
For example, if you had a pod with three containers `cont1`, `cont2` and `cont3` and you wanted to assign different Scalyr API keys to each container,
0 commit comments