Configure the Better Stack collector Helm chart with your values.yaml and Kubernetes annotations. For every chart option, see the values.yaml file.
Keep COLLECTOR_SECRET out of your values.yaml and version control. Store it in a Kubernetes Secret:
Reference the Secret in your values.yaml. Set other environment variables from a ConfigMap the same way:
Environment variables set explicitly in collector.env or ebpf.env will take precedence over variables sourced from envFrom.
Give the collector pods a PriorityClass so they are scheduled first and less likely to be evicted during resource shortages. Set priorityClassName in your values.yaml to a PriorityClass already defined in your cluster:
Learn more about Pod Priority and Preemption in Kubernetes documentation.
You can use Kubernetes pod and namespace annotations to control the sampling of logs and collection of traces. The annotations take precedence over the UI for annotated resources.
Services and namespaces annotated with exclude-from-services are not added to the Services list in Better Stack. Use this annotation for ephemeral pods to reduce noise.
Send any log files from the node's filesystem to Better Stack. For example, add the following configuration to your manual.vector.yaml file to send the logs from /var/www/custom.log and any file matching /var/www/**/service.*.log:
Any source with a name starting with better_stack_logs_ is forwarded to the logs sink.
Collector mounts the root filesystem read-only into the collector container by default. You can mount only select paths into the container:
Selected paths will be mounted read-only under the /host prefix, e.g. /host/var/www/custom.
The ebpf container requires privileged access as it runs the eBPF code responsible for generating traces. The collector container doesn't request privileged access.
Please let us know at hello@betterstack.com.
We're happy to help! ๐
We use cookies to authenticate users, improve the product user experience, and for personalized ads. Learn more.