Skip to content

Commit 8151375

Browse files
out_stackdriver: fix resource labels validation URL (#873)
Signed-off-by: Youssef Rizkalla <[email protected]> Signed-off-by: Youssef Rizkalla <[email protected]>
1 parent 57ac8ff commit 8151375

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

pipeline/outputs/stackdriver.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,7 @@ For instance, for a K8s resource type, `resource_labels` can be used in tandem w
152152
Resource_Labels cluster_name=my-cluster,location=us-central1-c,container_name=$kubernetes['container_name'],namespace_name=$kubernetes['namespace_name'],pod_name=$kubernetes['pod_name']
153153
```
154154

155-
`resource_labels` also supports validation for required labels based on the input resource type. This allows fluent-bit to check if all specified labels are present for a given configuration before runtime. If validation is not currently supported for a resource type that you would like to use this API with, we encourage you to open a pull request for it. Adding validation for a new resource type is simple - all that is needed is to specify the resources associated with the type alongside the required labels [here](https://github.com/fluent/fluent-bit/blob/resource-labels/plugins/out_stackdriver/stackdriver_resource_types.h).
155+
`resource_labels` also supports validation for required labels based on the input resource type. This allows fluent-bit to check if all specified labels are present for a given configuration before runtime. If validation is not currently supported for a resource type that you would like to use this API with, we encourage you to open a pull request for it. Adding validation for a new resource type is simple - all that is needed is to specify the resources associated with the type alongside the required labels [here](https://github.com/fluent/fluent-bit/blob/master/plugins/out_stackdriver/stackdriver_resource_types.c#L27).
156156
## Troubleshooting Notes
157157

158158
### Upstream connection error

0 commit comments

Comments
 (0)