Skip to content

Added kafkaQueueProblems scenarios#267402

Merged
yuliia-fryshko merged 4 commits intoelastic:mainfrom
yuliia-fryshko:add-evals-kafka-scenarios-554
May 5, 2026
Merged

Added kafkaQueueProblems scenarios#267402
yuliia-fryshko merged 4 commits intoelastic:mainfrom
yuliia-fryshko:add-evals-kafka-scenarios-554

Conversation

@yuliia-fryshko
Copy link
Copy Markdown
Contributor

@yuliia-fryshko yuliia-fryshko commented May 4, 2026

Closes https://github.com/elastic/obs-ai-team/issues/554

Add observability AI eval tests covering the Kafka queue problems flow.

@yuliia-fryshko yuliia-fryshko self-assigned this May 4, 2026
@yuliia-fryshko yuliia-fryshko added the release_note:skip Skip the PR/issue when compiling release notes label May 4, 2026
@yuliia-fryshko yuliia-fryshko requested a review from a team as a code owner May 4, 2026 08:13
@yuliia-fryshko yuliia-fryshko added backport:version Backport to applied version labels v9.4.0 Team:obs-ai-team labels May 4, 2026
@yuliia-fryshko yuliia-fryshko added evals:observability-ai Run the observability-ai evals @kbn/evals models:judge:eis/google-gemini-3.1-pro Override LLM-as-a-judge connector for evals: eis/google-gemini-3.1-pro models:weekly-eis-models Run evals against the weekly EIS model set (see eval_pipeline.ts) labels May 4, 2026
Copy link
Copy Markdown
Contributor

@SrdjanLL SrdjanLL left a comment

Choose a reason for hiding this comment

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

LGTM (code review only)!

Before merging, is there anything worth noting about evals results? Are all criteria consistently satisfied and right tools/skill invoked?

Asking because the related issue mentions:

Make improvements to the skill if necessary.

@kibanamachine

This comment was marked as outdated.

@yuliia-fryshko
Copy link
Copy Markdown
Contributor Author

LGTM (code review only)!

Before merging, is there anything worth noting about evals results? Are all criteria consistently satisfied and right tools/skill invoked?

Asking because the related issue mentions:

Make improvements to the skill if necessary.

Thank you, @SrdjanLL !
I post the results here.
As you can see, the Criteria results are low, and the explanation indicates that it couldn’t identify the issue in the upstream service. This should be addressed in this issue https://github.com/elastic/obs-ai-team/issues/569.

The output correctly identifies that the slowness is due to an artificial sleep in the fraud-detection service (the consumer) rather than a real Kafka delay, attributing the issue to the consumer side. "mjhq": The output does not identify the upstream producer (checkout) or mention it at all. "zudi": The output does not identify a throughput mismatch between checkout and fraud-detection. "exlp": The output does not mention checkout logs or excessive Kafka messages per order. "fuvk": The output only suggests actions for the fraud-detection service and does not mention investigating the checkout service for excessive duplicate messages.

Screenshot 2026-05-05 at 16 01 00

@yuliia-fryshko yuliia-fryshko merged commit b5db3b5 into elastic:main May 5, 2026
24 checks passed
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 9.4

https://github.com/elastic/kibana/actions/runs/25381379199

@kibanamachine
Copy link
Copy Markdown
Contributor

💔 All backports failed

Status Branch Result
9.4 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 267402

Questions ?

Please refer to the Backport tool documentation

@viduni94 viduni94 added backport:skip This PR does not require backporting backport:version Backport to applied version labels v9.4.0 and removed backport:version Backport to applied version labels v9.4.0 backport:skip This PR does not require backporting labels May 5, 2026
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 9.4

https://github.com/elastic/kibana/actions/runs/25386121464

@kibanamachine
Copy link
Copy Markdown
Contributor

💔 All backports failed

Status Branch Result
9.4 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 267402

Questions ?

Please refer to the Backport tool documentation

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label May 7, 2026
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 267402 locally
cc: @yuliia-fryshko

1 similar comment
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 267402 locally
cc: @yuliia-fryshko

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport missing Added to PRs automatically when the are determined to be missing a backport. backport:version Backport to applied version labels evals:observability-ai Run the observability-ai evals @kbn/evals models:judge:eis/google-gemini-3.1-pro Override LLM-as-a-judge connector for evals: eis/google-gemini-3.1-pro models:weekly-eis-models Run evals against the weekly EIS model set (see eval_pipeline.ts) release_note:skip Skip the PR/issue when compiling release notes Team:obs-ai-team v9.4.0 v9.5.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants