Hi folks, Sorry for this stupid question but I'm e...
# general
s
Hi folks, Sorry for this stupid question but I'm evaluating signoz in our environment. However, from the document, I didn't see the definition for the components installed in Kubernetes. I would like to have a full understanding before going for production, here is the list of pods and their purpose as far as I understand, that are provisioned: • signoz-alertmanager: for alerting • signoz-clickhouse-operator: k8s operator for clickhouse • signoz-frontend: UI • signoz-k8s-infra-otel-agent: collect container log and node metric to send to Otel collector • signoz-k8s-infra-otel-deployment: ? • signoz-otel-collector: Otel Collector who receives the data from agents • signoz-otel-collector-metrics: ? • signoz-query-service: send query from UI to clickhouse via API • signoz-zookeeper: for clickhouse DB Could you guys please explain the purpose of signoz-k8s-infra-otel-deployment and signoz-otel-collector-metrics for me? I really appreciate any help you can provide.
p
You got the most of it right. • `otel-agent`: collects container logs, kubelet and node metrics, and acts as gateway collector to send any incoming OTLP data to SigNoz OtelCollector • `otel-deployment`: collects cluster-level metrics from the Kubernetes API server • `signoz-otel-collector`: SigNoz Distribution of OtelCollector - responsible for writing incoming data to ClickHouseDB • `signoz-otel-collector-metrics`: Prometheus metrics scraper - either static targets, or scrape metrics using pod annotation
<http://signoz.io/scrape|signoz.io/scrape>
s
Thank you very much for the useful information @Prashant Shahi For
signoz-otel-collector-metrics
, if I don't use Prometheus and don't need to scrape specific metrics from pod then can I disable it?
p
yes, you can disable it, if you do not need it. But do know that this will disable internal metrics collection like clickhouse and otel-collector(s) metrics.
p
Hello @Prashant Shahi, I want to disable logs and metrics which i am getting in signoz, i only want to enable traces, so how can i do that ?
p
Easy way to do would be disabling k8s infra.
If you have signoz running in same cluster as your application, you might want to disable log/infra metrics collection.
And still use the OTLP data forwarding. Application pod => Otel-agent (running in same node) => SigNoz OtelCollector
p
Means the pod which is running (signoz-k8s-infra-otel-deployment) should i just stop it?
p
yes, and disable presets for log collection and kubelet metrics.
p
And this will also stop the application logs ?
p
yes, it will.
you can include the following in your Helm override values:
Copy code
otelCollectorMetrics:
  enabled: false

presets:
  logsCollection:
    enabled: false
  hostMetrics:
    enabled: false
  kubeletMetrics:
    enabled: false
  clusterMetrics:
    enabled: false

k8s-infra:
  otelDeployment:
    enabled: false
@Chitransh Gupta we can have a docs section under Self-hosting (OSS) SigNoz mentioning how to disable the default infra metrics and log collection.
p
Thanks for your guidance @Prashant Shahi
c
@Prashant Shahi Can you make an issue for the same on signoz.io github repo and give a brief description for this.
p
Included section for disabling logs collection and metrics collections in K8s infra monitoring tutorial. https://github.com/SigNoz/signoz.io/pull/1737
^ @Chitransh Gupta