grafana/k6-studio

Warning when correlation rule extracts value from multiple requests

Open

#310 opened on Nov 10, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (27 forks)auto 404
good first issue

Repository metrics

Stars
 (510 stars)
PR merge metrics
 (PR metrics pending)

Description

When using the correlation rule with the current behaviour, it will extract the value defined in the selector only from the first request that matches. Following requests could be matched but are ignored by script generation, still they are displayed in the rule preview.

We should warn the user when a correlation rule matches multiple requests so that they can accept to use it as it is or fine tune the selection.

As a user when I use a correlation rule that matches multiple requests, I should be warned when that happens to not have surprises in behaviour.

Contributor guide

Research direction
Examine the correlation rule selector logic in the codebase to understand where matching occurs. Then implement a warning when multiple requests match and the user can accept or refine the rule.
Tech stack
typescript
Domain
desktoptesting
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70