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

Improve orchestrator info status #225

Open
evaline-ju opened this issue Oct 8, 2024 · 0 comments
Open

Improve orchestrator info status #225

evaline-ju opened this issue Oct 8, 2024 · 0 comments
Assignees
@pscoro
Labels
bug Something isn't working

Comments

@evaline-ju
Copy link
Collaborator

evaline-ju commented Oct 8, 2024 •
edited
Loading

Describe the bug

The /info endpoint for orchestrator sometimes returns unknown status for clients when they are independently healthy. The may occur when /health is potentially served on a different port, hostnames use service names instead of full routes/hosts, etc.

Expected behavior

/info can more reliably reflect health status of downstream clients

Observed behavior

Multiple client not founds
@evaline-ju evaline-ju added the bug Something isn't working label Oct 8, 2024
@evaline-ju evaline-ju linked a pull request Oct 8, 2024 that will close this issue
Client optional health port configuration #224
Closed
@evaline-ju evaline-ju mentioned this issue Oct 8, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pscoro pscoro

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Client optional health port configuration pscoro/fms-guardrails-orchestrator
2 participants
@evaline-ju @pscoro