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

ECS: Missing link to task on container details panel #2040

Closed
2opremio opened this issue Nov 29, 2016 · 2 comments
Closed

ECS: Missing link to task on container details panel #2040

2opremio opened this issue Nov 29, 2016 · 2 comments
Assignees
@ekimekim
Labels
bug Broken end user or developer functionality; not working as the developers intended it ecs Pertains to integration with Amazon Elastic Container Service
Milestone
EOY 2016

Comments

@2opremio
Copy link
Contributor

2opremio commented Nov 29, 2016 •
edited
Loading

Leftover from #2026

Here's an example: In the Socks shop demo, the rabbitmq container links to its host and its container by image but not to its ECS task.

screen shot 2016-11-29 at 7 11 37 am
@2opremio 2opremio added the bug Broken end user or developer functionality; not working as the developers intended it label Nov 29, 2016
@2opremio 2opremio added this to the November2016 milestone Nov 29, 2016
@2opremio 2opremio modified the milestones: December2016, Backlog Dec 5, 2016
@2opremio 2opremio added the ecs Pertains to integration with Amazon Elastic Container Service label Dec 12, 2016
@2opremio 2opremio modified the milestones: December2016, EOY 2016 Dec 13, 2016
@ekimekim
Copy link
Contributor

I'm looking through the report, but I don't understand what field causes that top link to appear?

@2opremio 2opremio mentioned this issue Dec 14, 2016
Closed
@ekimekim
Copy link
Contributor

for posterity: that top link is populated from the parents field of the returned node in detail view, which is a render.detailed.Node, NOT a report.Node, the conversion between the two for the parents field explicitly describes behaviour for each topology type, and didn't list ECS topologies, so they were ignored despite being in the report's parent field.

@ekimekim ekimekim mentioned this issue Jan 21, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ekimekim ekimekim

Labels
bug Broken end user or developer functionality; not working as the developers intended it ecs Pertains to integration with Amazon Elastic Container Service
Projects
None yet
Milestone
EOY 2016
Development

No branches or pull requests
2 participants
@ekimekim @2opremio