(Go: >> BACK << -|- >> HOME <<)

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.

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

Show health information for instances on load balancers #219

Merged
merged 4 commits into from
Mar 2, 2017

Conversation

PtrTeixeira
Copy link
Contributor

Show the health details for instances that are attached to our load balancers, without needing to go through the AWS console.

Show health details (eg, healthy, unhealthy, initial, ...) for instances
that are attached to an application load balancer. This was relatively
low-hanging fruit because I already had the information available but
was throwing it away on the backend. This includes both the change to
the resource to make this happen and the change to the front-end to
visualize it. Ideally.
Adds an additional endpoint to get the health status of instances which
are attached to a classic load balancer. We can probably just use this
request to list the instances in general, rather than trying to merge
the results of the list that we grab from the `/{elbName}` endpoint with
this one.
Add display of instance health status for instances which are listening
to classic load balancers.
@PtrTeixeira PtrTeixeira changed the title [WIP] Show health information for instances on load balancers Show health information for instances on load balancers Mar 1, 2017
@ssalinas
Copy link
Member
ssalinas commented Mar 2, 2017

👍 LGTM

@PtrTeixeira PtrTeixeira merged commit 0fe462a into alb_support Mar 2, 2017
@PtrTeixeira PtrTeixeira deleted the show-instance-health branch March 2, 2017 18:05
@ssalinas ssalinas modified the milestone: 0.5.0 May 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants