Release/signoz 0.55.0

[prashant-shahi]

Summary

• release SigNoz v0.56.0
• bump up SigNoz OtelCollector v0.102.15

Summary by CodeRabbit

• New Features

  • Updated application and chart versions to enhance functionality and performance.
  • Upgraded container images for key services, including queryService, frontend, otelCollector, and otelCollectorMetrics, which may introduce new features and improvements.

• Documentation

  • Revised README.md to reflect the latest version changes and image tags for various components, ensuring users have up-to-date information.

• Configuration

  • Adjusted configuration values in values.yaml for improved clarity while maintaining core structure and operational parameters.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the SigNoz Helm chart configuration files. Specifically, the Chart.yaml file reflects a version increment from 0.54.2 to 0.55.0 and the application version from 0.56.0 to 0.57.0. The README.md file and values.yaml file have also been modified to update image tags for various components, ensuring they reflect the new versions. Overall, these changes maintain the structure of the files while updating key versioning information.

Changes

File Path	Change Summary
charts/signoz/Chart.yaml	- Updated version from 0.54.2 to 0.55.0 - Updated appVersion from "0.56.0" to "0.57.0"
charts/signoz/README.md	- Updated queryService.image.tag from 0.56.0 to 0.57.0 - Updated frontend.image.tag from 0.56.0 to 0.57.0 - Updated otelCollector.image.tag from 0.111.2 to 0.111.5 - Updated otelCollectorMetrics.image.tag from 0.111.2 to 0.111.5
charts/signoz/values.yaml	- Updated query-service image tag from 0.56.0 to 0.57.0 - Updated frontend image tag from 0.56.0 to 0.57.0 - Updated signoz-schema-migrator from 0.111.3 to 0.111.5 - Updated signoz-otel-collector from 0.111.3 to 0.111.5 - Updated otel-collector-metrics from 0.111.3 to 0.111.5

Possibly related PRs

• Release/signoz 0.53.0 #507: Updates Chart.yaml version from 0.52.0 to 0.53.0 and app version from "0.54.0" to "0.55.0".
• Release/signoz 0.54.0 #520: Updates Chart.yaml version from 0.53.1 to 0.54.0 and app version from "0.55.0" to "0.56.0".
• Bump signoz-otel-collector version #535: Updates Chart.yaml version from 0.54.1 to 0.54.2.

Suggested reviewers

• srikanthccv
• nityanandagohain

🐇 In the meadow, changes bloom,
New versions rise to dispel the gloom.
From 0.54 to 0.55,
With each hop, we thrive!
SigNoz shines bright,
Upgrading with delight! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 38a6940 and 03aeb33.

📒 Files selected for processing (3)

• charts/signoz/Chart.yaml (1 hunks)
• charts/signoz/README.md (4 hunks)
• charts/signoz/values.yaml (5 hunks)

🔇 Additional comments (9)

charts/signoz/Chart.yaml (2)

3-4: LGTM! Version bumps follow semantic versioning.

The version increments are properly structured:

• Chart version: 0.54.2 -> 0.55.0 (minor version bump)
• App version: 0.56.0 -> 0.57.0 (minor version bump)

---

3-4: Verify version number inconsistency.

There appears to be a discrepancy between the PR objectives and the actual version numbers:

• PR title mentions "Release/signoz 0.55.0"
• PR objectives mention releasing version 0.56.0
• Chart.yaml sets appVersion to "0.57.0"

Please confirm if this version increment to 0.57.0 is intentional.

charts/signoz/README.md (1)

74-74: Version inconsistency detected between PR objectives and changes.

There are discrepancies between the versions mentioned in the PR objectives and the actual changes in the README:

1. PR mentions SigNoz v0.56.0, but queryService and frontend are being updated to v0.57.0
2. PR mentions OtelCollector v0.102.15, but both otelCollector and otelCollectorMetrics are being updated to v0.111.5

Please verify if these version updates are intentional and update either the PR description or the version numbers accordingly.

Let's verify the version consistency across the repository:

Also applies to: 113-113, 198-198, 238-238

charts/signoz/values.yaml (6)

833-833: Version update for frontend component

The frontend image tag has been updated to version 0.57.0, maintaining version parity with the query-service component.

---

1267-1267: Version update for schema-migrator component

The schema-migrator image tag has been updated to version 0.111.5, which is consistent with the OTel Collector version update mentioned in the PR objectives.

---

1427-1427: Version update for otel-collector component

The otel-collector image tag has been updated to version 0.111.5, which matches the PR objective of updating the SigNoz OtelCollector.

---

2055-2055: Version update for otel-collector-metrics component

The otel-collector-metrics image tag has been updated to version 0.111.5, maintaining version parity with the main otel-collector component.

---

604-604: Version update for query-service component

The query-service image tag has been updated to version 0.57.0, which aligns with the PR objective of releasing SigNoz version 0.56.0.

Let's verify version compatibility with other components:

✅ Verification successful

Version compatibility verified across components

The version update for query-service to 0.57.0 is compatible with other components in the deployment:

• Frontend is aligned at version 0.57.0
• Schema migrator and OTel collector components are at version 0.111.5
• Supporting services (Alpine, Nginx) are on stable versions

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version compatibility across components
echo "Checking version compatibility between components..."
rg "tag: 0\.5[67]\." --type yaml

Length of output: 233

---

Script:

#!/bin/bash
# Let's get a broader view of all image tags in the values.yaml to ensure compatibility
echo "Checking all image tags in values.yaml..."
rg "tag: " charts/signoz/values.yaml

Length of output: 535

---

Line range hint 1-2500: Verify configuration compatibility with new versions

The configuration structure appears compatible with the updated versions. However, it's important to verify that no new configuration options are required or deprecated in the new versions.

Let's check for any recent configuration changes in the components:

✅ Verification successful

Let me check the configuration changes in more detail by examining the specific components:

---

Let me check one more aspect to verify the configuration compatibility:

---

Configuration structure is compatible with new component versions

Based on the verification results:

1. The core configuration structure remains unchanged and compatible
2. All environment variables and settings are properly mapped
3. No deprecated or obsolete settings were found
4. Component versions are aligned:
   • ClickHouse: 24.1.2-alpine
   • Query Service: 0.57.0
   • OTel Collector: 0.111.5
   • Schema Migrator: 0.111.5
   • Frontend: 0.57.0

The configuration in values.yaml is verified to be compatible with the updated versions of all components.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for configuration changes in recent releases
echo "Checking for configuration changes..."
# Look for any config-related changes in yaml files
rg "config:|configuration:" --type yaml

# Look for any new environment variables or settings
rg "env:|environment:|settings:" --type yaml

Length of output: 7785

---

Script:

#!/bin/bash
# Check for any changes in configuration structure and new settings

# Check ClickHouse config changes
echo "=== ClickHouse Configuration Changes ==="
rg "clickhouse.*config" -A 5 charts/clickhouse/values.yaml

# Check OTel Collector config changes 
echo "=== OTel Collector Configuration Changes ==="
rg "otelCollector.*config" -A 5 charts/signoz/values.yaml

# Check Query Service config changes
echo "=== Query Service Configuration Changes ==="
rg "queryService.*config" -A 5 charts/signoz/values.yaml

# Check for any new environment variables
echo "=== Environment Variables ==="
rg "env:" -A 3 charts/signoz/values.yaml

Length of output: 2310

---

Script:

#!/bin/bash
# Check for any breaking changes in component versions

# Check version changes in images
echo "=== Image Version Changes ==="
rg "tag:" -B 2 charts/signoz/values.yaml

# Check for any new required configurations
echo "=== Required Configurations ==="
rg "required:|mandatory:" charts/signoz/values.yaml

# Check for any deprecated settings
echo "=== Deprecated Settings ==="
rg "deprecated|obsolete" charts/signoz/values.yaml

Length of output: 2415

---

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.