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.

Sign up for GitHub

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

Jump to bottom

Move avg_request_time_to_error to the backend context #12556

Open
Tracked by #12214
akolson opened this issue Aug 13, 2024 · 1 comment
Open
Tracked by #12214

Move avg_request_time_to_error to the backend context #12556

akolson opened this issue Aug 13, 2024 · 1 comment
Assignees
@thesujai
Labels
DEV: backend Python, databases, networking, filesystem... gsoc A GSoC project task

Comments

@akolson
Copy link
Member

akolson commented Aug 13, 2024 •
edited
Loading

Overview

The avg_request_time_to_error property is more suited for the backend context and should be move there instead. Its currently part of errorreport.

Description and outcomes

  • Move avg_request_time_to_error to the backend context

Acceptance Criteria

  • avg_request_time_to_error is part of the backend context

Assumptions and Dependencies

  • NA

Scope

  • Moving the avg_request_time_to_error

Accessibility Requirements

NA

Resources
@akolson akolson mentioned this issue Aug 13, 2024
Open
@akolson akolson changed the title Move avg_request_time_to_error to the backend context Move avg_request_time_to_error to the backend context Aug 13, 2024
@akolson akolson added DEV: backend Python, databases, networking, filesystem... gsoc A GSoC project task labels Aug 13, 2024
@thesujai
Copy link
Contributor

I can pick this up @akolson

@thesujai thesujai mentioned this issue Sep 14, 2024
Open
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thesujai thesujai

Labels
DEV: backend Python, databases, networking, filesystem... gsoc A GSoC project task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@akolson @thesujai