Release/v0.60.x

[prashant-shahi]

Summary

• release SigNoz v0.60.0
• bump up SigNoz OtelCollector v0.111.13

---

Important

Update SigNoz to v0.60.0 with new trace schema support, enhanced telemetry, and infrastructure monitoring features.

• Version Updates:
  • Update SigNoz to v0.60.0 and OtelCollector to v0.111.13 in docker-compose.yaml and other Docker setup files.
• API and Backend Changes:
  • Add UseTraceNewSchema flag in api.go, server.go, and reader.go to support new trace schema.
  • Modify SearchTraces in traces.go to handle new trace API.
  • Update GetServices and GetTopOperations in reader.go to support new schema.
• Telemetry Enhancements:
  • Add telemetry events for trace queries in telemetry.go.
  • Track dashboards and alerts with trace ClickHouse queries.
• Frontend Enhancements:
  • Add infrastructure monitoring features in AppRoutes and InfraMonitoring.json.
  • Implement new components for host metrics and logs in HostMetricsDetail.
• Miscellaneous:
  • Fix logging and error handling in logparsingpipeline/preview.go.
  • Update ValidateAndCastValue in format.go to handle string arrays.

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

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 7cd8442 in 3 minutes and 39 seconds

More details

• Looked at 9592 lines of code in 135 files
• Skipped 3 files when reviewing.
• Skipped posting 8 drafted comments based on config settings.

1. pkg/query-service/app/clickhouseReader/reader.go:1058

• Draft comment:
  Check for errors returned by r.db.QueryRow to ensure any issues are handled appropriately.
• Reason this comment was not posted:
  Comment did not seem useful.

2. pkg/query-service/app/inframetrics/hosts.go:373

• Draft comment:
  Check for errors returned by GetCountOfThings to ensure proper error handling.
• Reason this comment was not posted:
  Comment did not seem useful.

3. pkg/query-service/app/clickhouseReader/reader.go:708

• Draft comment:
  Consider using zap.L().Warn instead of zap.L().Error for non-critical issues to avoid alarming logs for expected conditions.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The code is using zap.L().Error to log errors, but it should use zap.L().Warn for non-critical issues. This is a common pattern in the codebase, so it should be addressed in multiple places.

4. frontend/src/components/HostMetricsDetail/HostMetricsDetail.styles.scss:1

• Draft comment:
  Avoid using inline styles in React components. Use external stylesheets or styled components instead. This is applicable in HostMetricsDetail.styles.scss and other similar files.
• Reason this comment was not posted:
  Comment was on unchanged code.

5. frontend/src/container/HostMetricsLoading/HostMetricsLoading.tsx:14

• Draft comment:
  Avoid using inline styles. Use external stylesheets or styled components instead.
• Reason this comment was not posted:
  Marked as duplicate.

6. frontend/src/container/HostMetricsLoading/HostMetricsLoading.tsx:15

• Draft comment:
  Avoid using inline styles. Use external stylesheets or styled components instead.
• Reason this comment was not posted:
  Marked as duplicate.

7. frontend/src/components/HostMetricsDetail/Containers/Containers.tsx:18

• Draft comment:
  Avoid using inline styles in React components. Use external stylesheets, CSS classes, or styled components instead. This is also applicable in Processes.tsx.
• Reason this comment was not posted:
  Marked as duplicate.

8. frontend/src/components/HostMetricsDetail/HostMetricsDetails.tsx:481

• Draft comment:
  Avoid using inline styles. Use external stylesheets or styled components instead.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_bgvtEcaa5gjyusvB

---

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.