hasura / hasura/graphql-engine

console: filter traces on executing user

Open
#10,392 0 comments 0 reactions 0 assignees View on GitHub
c/v3-trace-api ddnbugbounty-2024 k/enhancement
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

On projects with high volume of traffic, it will be helpful to filter traces based on the user who executed it. Currently there is no way to distinguish the same. There is no easy way to find traces for queries I just executed on the traces view page for debugging (https://console.hasura.io/project//build//insights/traces).

Contributor guide

Open the contributing guide

Research direction

Start at the traces view page linked in the issue and trace how trace results are presented and filtered. Define the user-filter behavior and verify that traces can be narrowed to the executing user on high-volume projects; the issue names no files or tests, so repository exploration is required.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.