Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for trace_v3 schema in messaging queues #6663

Merged
merged 3 commits into from
Dec 18, 2024

Conversation

shivanshuraj1333
Copy link
Member

@shivanshuraj1333 shivanshuraj1333 commented Dec 18, 2024

Supports trace_v3 now


Important

Update SQL queries to support trace_v3 schema and enable Kafka span evaluation by default.

  • Behavior:
    • Update SQL queries in sql.go to use signoz_traces.distributed_signoz_index_v3 instead of v2.
    • Replace serviceName with resource_string_service$$name and msgSystem with attribute_string_messaging$$system in SQL queries.
  • Constants:
    • Change KafkaSpanEval default value to true in constants.go.

This description was created by Ellipsis for 7460888. It will automatically update as commits are pushed.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ Changes requested. Reviewed everything up to 7460888 in 32 seconds

More details
  • Looked at 383 lines of code in 2 files
  • Skipped 0 files when reviewing.
  • Skipped posting 1 drafted comments based on config settings.
1. pkg/query-service/constants/constants.go:93
  • Draft comment:
    The environment variable KAFKA_SPAN_EVAL has been changed from false to true. This alters the default behavior of the application and should be documented or communicated to the team.
  • Reason this comment was not posted:
    Confidence changes required: 50%
    The PR changes the environment variable KAFKA_SPAN_EVAL from false to true. This change should be highlighted as it affects the default behavior of the application.

Workflow ID: wflow_HbsIa5fMPHIOmt9i


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.

@nityanandagohain nityanandagohain changed the title Add support for trace_ve schema in messaging queues Add support for trace_v3 schema in messaging queues Dec 18, 2024
Copy link
Member

@nityanandagohain nityanandagohain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall changes looks good, please test all the changes before merging

@@ -90,7 +90,7 @@ func EnableHostsInfraMonitoring() bool {
return GetOrDefaultEnv("ENABLE_INFRA_METRICS", "true") == "true"
}

var KafkaSpanEval = GetOrDefaultEnv("KAFKA_SPAN_EVAL", "false")
var KafkaSpanEval = GetOrDefaultEnv("KAFKA_SPAN_EVAL", "true")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

intended change ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am re-iterating my position on this as mentioned here #6661 (comment), this change should not be enabled by default. Please revert it.

@shivanshuraj1333 shivanshuraj1333 merged commit 83f6dea into SigNoz:develop Dec 18, 2024
13 of 15 checks passed
@srikanthccv
Copy link
Member

With the trace v3, the bucket filter must exist. Otherwise, they can be really slow (it would have been better if it was suggested during review) #6666, @shivanshuraj1333, please sync with @nityanandagohain if you need to understand the bucketing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants