Srikanth Chekuri

use goreleaser to manage builds

2

Find a unified and consistent way to manager binary and docker builds across the environments (which is not the case today)

Explore/Propose the possibility of reloading the partial changes/pipelines in collector service

1

Restarting the collector for config change, which sometimes can be minor, is costly and has downsides. In an ideal scenario, just the components/pipelines affected should just reload or dynamically change...

Revisit the batch processor settings. With a ingest rate of 10k records/s, writing each second means 10x parts as compared to 100k records write/s. 10k maybe fine but given the...

- Make sure when the exporter receives a batch of 100k records, it completes the work and returns in a second. - Eliminate the duplicate inserts - There is a...

There should be a set of benchmarking tests that can be run on demand for specific commits/PRs. When reviewing the PR, if the author or reviewer wants to see how...

- https://github.com/SigNoz/signoz-otel-collector/pull/111#discussion_r1132180989 - https://github.com/SigNoz/signoz-otel-collector/pull/111#discussion_r1132157577 - https://github.com/SigNoz/signoz-otel-collector/pull/111#discussion_r1132172477 - https://github.com/SigNoz/signoz-otel-collector/pull/111#discussion_r1131268800 - https://github.com/SigNoz/signoz-otel-collector/pull/111#discussion_r1129247799

- [ ] #96 - [x] #97 - [ ] #98 verify and close if already done

The collector may start up fine but immediately shut down with async errors. This can happen for any reason. Make the client handle this https://github.com/SigNoz/signoz-otel-collector/blob/main/signozcol/collector.go#L107.

(logs): store the resource attributes separately

1

I believe this is already done for logs. Verify once and close.