Configuration
You can configure for SigNoz with different options.
If no configuration for an option is set, then the default value as described is applied.
Environment variables​
When using SigNoz, there are various environment variables you can set to configure your SigNoz cluster.
Here is a comprehensive list of all of them. However, for general use, you most likely do not have to worry about most of these.
Query Service​
| Environment Variable | Description | Default Value |
|---|---|---|
STORAGE | Database for the storage (one of clickhouse or druid(deprecated) | clickhouse |
GODEBUG | Go runtime name resolver (one of netdns=go or netdns=cgo). More info. | netdns=go |
ALERTMANAGER_API_PREFIX | Endpoint of alertmanager with API prefix. | http://alertmanager:9093/api/ |
ClickHouseUrl | ClickHouse database endpoint with TCP port | tcp://localhost:9000 |
Otel Collector​
Otel Collector supports multiple combination of options.
Using the configuration file, you can pass receivers, processors, extensions, exporters and service as per your requirements.
You can find the complete otel collector configuration in the OpenTelemetry documentation.
By default, SigNoz runs with this default Otel Collector configuration.
For any configuration changes in Docker, you would have to update /deploy/docker/clickhouse-setup/otel-collector-config.yaml and bring up Otel Collector.
Otel Collector Metrics​
Otel Collector Metrics uses same image and binary as that of the Otel Collector. Hence, you will find the configuration similarities of that of Otel Collector.
By default, SigNoz runs with this default Otel Collector Metrics configuration.
For any configuration changes in Docker, you would have to update /deploy/docker/clickhouse-setup/otel-collector-metrics-config.yaml and bring up Otel Collector.
Â
Kubernetes Configuration​
The latest helm chart configuration settings can be found at: