Clean up config values

[srikanthccv]

Summary by CodeRabbit

• New Features
  • Streamlined metrics collection approach with a focus on specific endpoints and protocols.
• Bug Fixes
  • Removed deprecated configurations for improved performance and reliability.
• Documentation
  • Updated configuration details to reflect the simplified structure and focus on key metrics receivers.

[coderabbitai]

Walkthrough

The changes in this pull request involve significant modifications to the charts/signoz/values.yaml configuration file. Key alterations include the removal of configurations related to the OpenTelemetry Collector, particularly the Prometheus receiver and various metrics handling components. This includes the elimination of specific processors and receivers, streamlining the configuration to focus on the otlp receiver and its protocols. The overall structure has been simplified, reflecting a shift towards a more efficient metrics collection approach.

Changes

File	Change Summary
charts/signoz/values.yaml	Removed configurations for Prometheus receiver, hostmetrics and resourcedetection processors, metrics/internal receiver, and signozspanmetrics/cumulative processor. Updated otelCollector and otelCollectorMetrics sections to streamline metrics collection.

Poem

In the meadow, metrics play,
With processors gone, they dance away.
The Prometheus song, no longer sung,
A simpler path, for the metrics run.
Hops of change, a joyful cheer,
In the fields of data, we hold dear! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 154f6e0 and ec81b6a.

📒 Files selected for processing (1)

• charts/signoz/values.yaml (1 hunks)

🔇 Additional comments (1)

charts/signoz/values.yaml (1)

1900-1900: LGTM! Configuration cleanup improves consistency.

The removal of 'signozspanmetrics/cumulative' from the traces pipeline processors aligns with the configuration cleanup objective. The change maintains only the delta processor which matches the defined processor configuration using AGGREGATION_TEMPORALITY_DELTA.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.