This message was deleted.
# supports
Slackbot
02/01/2023, 9:01 PMThis message was deleted.
v
Vishal Sharma
02/02/2023, 3:35 AM@nitya-signoz Can you please help him here?
🙏 1
n
nitya-signoz
02/02/2023, 4:36 AMNot an expert in openshift here, but seems like the default filelog receiver we use for other k8s platforms won’t work with openshift here.
You will need to use a log collector like this https://docs.openshift.com/container-platform/4.8/logging/config/cluster-logging-collector.html and forward logs to otel-collector. ( you will have to use the fluent receiver in otel collector https://signoz.io/docs/userguide/logs/#log-receivers)
https://docs.openshift.com/container-platform/4.10/logging/cluster-logging-loki.html#logging-feature-ref_cluster-logging-loki
@Prashant Shahi please add if you have more idea here.
p
Prashant Shahi
02/02/2023, 6:23 AM@Andrew Seif any otel-collector logs or events would be helpful to figure it out.
TBH, we are yet to make changes to be support running all signoz components in non-root user permissions to adhere with OpenShift's stronger security policies. We will resume it sometime in future.
https://github.com/SigNoz/charts/pull/4
Prashant Shahi
02/02/2023, 6:31 AMthey are all detected and are sending traces, we used Sidecars to enable that, but they are not sending logsLogs from SDK could be sent via sidecar, if configured. But I am not sure if sidecars would be able to scrape container logs using filelog receiver correctly.
Prashant Shahi
02/02/2023, 6:32 AMContainer logs scraping is recommended to be done via daemonset / OtelAgent.
Prashant Shahi
02/02/2023, 6:33 AMcc @Srikanth Chekuri
51 Views