chore: add v2 metric writer to pipelines

[srikanthccv]

Summary

Part of #5975

---

Important

Add clickhousemetricswritev2 exporter to OpenTelemetry collector configurations and remove signozspanmetrics/cumulative processor.

• Exporters:
  • Add clickhousemetricswritev2 to otel-collector-config.yaml in both docker-swarm and docker setups.
• Processors:
  • Remove signozspanmetrics/cumulative processor from otel-collector-config.yaml in both docker-swarm and docker setups.
• Pipelines:
  • Update metrics, metrics/hostmetrics, and metrics/prometheus pipelines to include clickhousemetricswritev2 exporter in both docker-swarm and docker setups.

^{This description was created by for aef3916. It will automatically update as commits are pushed.}

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to aef3916 in 1 minute and 2 seconds

More details

• Looked at 144 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 5 drafted comments based on config settings.

1. deploy/docker-swarm/clickhouse-setup/otel-collector-config.yaml:149

• Draft comment:
  Ensure clickhousemetricswritev2 is compatible with existing data flow and does not introduce performance issues or data inconsistencies.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The clickhousemetricswritev2 exporter is added to multiple pipelines, which is correct as per the PR intent. However, it's important to ensure that the new exporter is compatible with the existing data flow and does not introduce any performance bottlenecks or data inconsistencies. This should be tested thoroughly.

2. deploy/docker/clickhouse-setup/otel-collector-config.yaml:154

• Draft comment:
  Ensure clickhousemetricswritev2 is compatible with existing data flow and does not introduce performance issues or data inconsistencies.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The clickhousemetricswritev2 exporter is added to multiple pipelines, which is correct as per the PR intent. However, it's important to ensure that the new exporter is compatible with the existing data flow and does not introduce any performance bottlenecks or data inconsistencies. This should be tested thoroughly.

3. deploy/docker-swarm/clickhouse-setup/otel-collector-config.yaml:116

• Draft comment:
  No issues found with the changes in this PR according to the specified rules.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The PR does not violate any of the specified rules. The changes are consistent with the existing structure and do not introduce any hardcoded colors, inline styles, or unrelated functions to the ClickHouseReader interface. The file structure is also appropriate for the context.

4. deploy/docker/clickhouse-setup/otel-collector-config.yaml:125

• Draft comment:
  No issues found with the changes in this PR according to the specified rules.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The PR does not violate any of the specified rules. The changes are consistent with the existing structure and do not introduce any hardcoded colors, inline styles, or unrelated functions to the ClickHouseReader interface. The file structure is also appropriate for the context.

5. deploy/docker/clickhouse-setup/otel-collector-config.yaml:128

• Draft comment:
  Duplicate configuration for clickhousemetricswritev2 exporter found in deploy/docker-swarm/clickhouse-setup/otel-collector-config.yaml. Consider reusing the existing configuration.

• clickhousemetricswritev2 exporter configuration (otel-collector-config.yaml)

• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_3NK5XjW1qIrKqxLD

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[srikanthccv]

@prashant-shahi please approve