enable kafka_span_eval, enabling the feature to avoid 404 in the messaging queue tab

[shivanshuraj1333]

Enables the feature by default to avoid 404

---

Important

Enables KafkaSpanEval by default in constants.go to prevent 404 errors in the messaging queue tab.

• Behavior:
  • Enables KafkaSpanEval by default in constants.go to prevent 404 errors in the messaging queue tab.

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

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to cb87806 in 11 seconds

More details

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

1. pkg/query-service/constants/constants.go:93

• Draft comment:
  Ensure that enabling KAFKA_SPAN_EVAL by default does not have unintended side effects in production environments. Consider documenting this change in the release notes or configuration documentation.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The change in the PR is straightforward, changing the default value of an environment variable. This change is consistent with the PR description, which aims to enable a feature by default to avoid 404 errors. The change is safe and does not introduce any logical, performance, or security issues.

2. pkg/query-service/constants/constants.go:93

• Draft comment:
  No issues found with the change. It adheres to the specified rules.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The change in the PR is straightforward and does not violate any of the specified rules.

Workflow ID: wflow_ybTNxWGzGoXauBdu

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[shivanshuraj1333]

@prashant-shahi either let's merge this PR or have this flag enabled in all the environments used for demo.

[shivanshuraj1333]

@srikanthccv shall we merge this PR?
I don't see any issues so far with the inner join with ~1 month of data in demo environments, let's see how it plays out.

[srikanthccv]

No, I am strongly against this idea of joining the trace table with itself enabled everywhere by default. It's going to wreck the whole paid pool users node because it causes high CPU and OOMkill. How much data do you have in demo and what is the resource usage when the query is run in demo.