-
Notifications
You must be signed in to change notification settings - Fork 181
Description
Describe the bug A clear and concise description of what the bug is.
helm install the chart 4.11.1 version. enabled log, and trace.
image tag: 0.108.0-sumo-0
i can see
the collector statefulset logs exposed the sumo receiver url.
2025-02-11T20:12:36.279Z info sumologicexporter@v0.108.0/exporter.go:282 setting data urls {"kind": "exporter", "data_type": "logs", "name": "sumologic", "logs_url": "https://collectors.au.sumologic.com/receiver/v1/otlp/xxxxx/v1/logs", "metrics_url": "https://collectors.au.sumologic.com/receiver/v1/otlp/xxxx==/v1/metrics", "traces_url": "https://collectors.au.sumologic.com/receiver/v1/otlp/xxxx==/v1/traces"}
i redact the sumo url with xxxxx
Logs Logs which can be helpful in investigating the issue.
Command used to install/upgrade Collection Direct command which you used to install/upgrade collection.
Configuration Configuration used for Collection e.g. user-values.yaml for helm.
To Reproduce Steps to reproduce the behavior.
Expected behavior A clear and concise description of what you expected to happen.
Environment (please complete the following information):
- Collection version (e.g.
helm ls -n sumologic
): - Kubernetes version (e.g.
kubectl version
): - Cloud provider:
- Others:
Anything else do we need to know Add any other context about the problem here, e.g. issue happens only occasionally.