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

Proxy has an API for determining its health #125

Open
samsp-msft opened this issue Apr 28, 2020 · 2 comments
Open

Proxy has an API for determining its health #125

samsp-msft opened this issue Apr 28, 2020 · 2 comments
Labels
Type: Enhancement New feature or request User Story Used for divisional .NET planning
Milestone
Backlog

Comments

@samsp-msft
Copy link
Member

samsp-msft commented Apr 28, 2020 •
edited
Loading

What should we add or change to make your life better?

Add an API that can be used to collect statistics and state of the proxy. This would also have events for lifetime so that app code can know when the proxy is shutting down.

Why is this important to you?

It provides a foundational piece of infrastructure for solving:
#23 part c - API for app code to shutdown the proxy
#124 - REST or gRPC API for remote access to proxy status
#123 - Dashboard for proxy config & status
@samsp-msft samsp-msft added the Type: Idea This issue is a high-level idea for discussion. label Apr 28, 2020
This was referenced Apr 28, 2020
Open
Closed
@karelz karelz added this to the 1.0.0 milestone May 12, 2020
@karelz karelz added Type: Enhancement New feature or request and removed Type: Idea This issue is a high-level idea for discussion. labels May 12, 2020
@karelz karelz mentioned this issue May 14, 2020
Closed
@karelz
Copy link
Member

karelz commented May 14, 2020

See detailed discussion in #127 (comment)

@samsp-msft samsp-msft mentioned this issue May 15, 2020
Open
@samsp-msft samsp-msft mentioned this issue Oct 21, 2020
Closed
37 tasks
@samsp-msft samsp-msft changed the title API for Proxy status Proxy has an API for determining its health Oct 21, 2020
@samsp-msft samsp-msft added the User Story Used for divisional .NET planning label Oct 21, 2020
@alnikola alnikola mentioned this issue Oct 27, 2020
Merged
@Tratcher Tratcher mentioned this issue Dec 11, 2020
Closed
@samsp-msft samsp-msft added the Priority:1 Used for divisional .NET planning label Jan 20, 2021
@karelz karelz mentioned this issue Feb 11, 2021
Closed
@karelz karelz modified the milestones: YARP 1.0.0, Backlog Mar 24, 2021
@karelz
Copy link
Member

karelz commented Mar 24, 2021

Triage: Unclear what kind of data we should expose, let's move post 1.0 when we get more clarity from customers.

@amweiss amweiss mentioned this issue Jun 24, 2021
Closed
@Tratcher Tratcher removed the Priority:1 Used for divisional .NET planning label Jul 13, 2021
@Tratcher Tratcher mentioned this issue Jul 13, 2021
Closed
@adityamandaleeka adityamandaleeka mentioned this issue Jan 27, 2022
Closed
@adityamandaleeka adityamandaleeka modified the milestones: Backlog, YARP 2.0.0 May 19, 2022
@samsp-msft samsp-msft moved this to 📋 Backlog in YARP 2.x Jun 9, 2022
@talha-sayed talha-sayed mentioned this issue Aug 6, 2022
Open
@karelz karelz modified the milestones: YARP 2.0.0, Backlog Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Enhancement New feature or request User Story Used for divisional .NET planning
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@adityamandaleeka @Tratcher @karelz @samsp-msft