Just wanted to flag that if you misconfigure the U...
# support
a
Just wanted to flag that if you misconfigure the URL for clickhouse in the collector you get this error:
Copy code
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x343dd12] goroutine 87 [running]: <http://github.com/SigNoz/signoz-otel-collector/exporter/clickhousemetricsexporter.(*PrwExporter).export.func1()|github.com/SigNoz/signoz-otel-collector/exporter/clickhousemetricsexporter.(*PrwExporter).export.func1()> /src/exporter/clickhousemetricsexporter/exporter.go:280 +0xf2 created by <http://github.com/SigNoz/signoz-otel-collector/exporter/clickhousemetricsexporter.(*PrwExporter).export|github.com/SigNoz/signoz-otel-collector/exporter/clickhousemetricsexporter.(*PrwExporter).export> /src/exporter/clickhousemetricsexporter/exporter.go:276 +0x256
This was my config:
Copy code
receivers:
  prometheus:
    config:
      scrape_configs:
        # SigNoz span metrics
        - job_name: "signozspanmetrics-collector"
          scrape_interval: 60s
          static_configs:
            - targets:
              - 127.0.0.1:8889

processors:
  batch:
    send_batch_size: 10000
    send_batch_max_size: 11000
    timeout: 10s

extensions:
  health_check:
    endpoint: 0.0.0.0:13134

exporters:
  clickhousemetricswrite:
    endpoint: tcp://${!CLICKHOUSE_HOST}:9000/?database=signoz_metrics&username=${!CLICKHOUSE_USER}&password=${!CLICKHOUSE_PWD}

service:
  telemetry:
    metrics:
      address: 0.0.0.0:8890
  extensions:
    - health_check
  pipelines:
    metrics:
      receivers: [prometheus]
      processors: [batch]
      exporters: [clickhousemetricswrite]
I was cleaning some things up and left the escape character for cloudformation in when I removed the
!Sub
function. took a while to understand why a segmentation fault was happening, no clear error message
Fix should be to not seg fault and catch this exception and report to user
p
thanks for reporting this @Alexei Zenin We will have a look at this cc @Prashant Shahi
a