Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Handle cases where services have the same application name with different service type. #611

Closed
Xylus opened this issue Jun 15, 2015 · 1 comment
Closed

Handle cases where services have the same application name with different service type. #611

Xylus opened this issue Jun 15, 2015 · 1 comment
Assignees
@Xylus
Labels
bug enhancement
Milestone
1.1.0

Comments

@Xylus
Copy link
Contributor

Xylus commented Jun 15, 2015

Backporting fixes to 1.1.0.

Issue resolves the following cases.

  1. Services with the same application name but different service types should be selectable separately - Same Application with different server type should be selectable separately. #214
  2. User nodes now take the destination's service type along with the application name when drawing the server map - User node pointing to a node with same application name but different service type throws an exception #254
@Xylus Xylus self-assigned this Jun 15, 2015
@Xylus Xylus added this to the 1.1.0 milestone Jun 15, 2015
Xylus added a commit to Xylus/pinpoint that referenced this issue Jun 15, 2015
@Xylus
pinpoint-apm#611 fix issues with applications having same name but di…
4fa9ef9 
…fferent types
@Xylus Xylus mentioned this issue Jun 15, 2015
Merged
@Xylus
Copy link
Contributor Author

Xylus commented Jun 17, 2015

fix applied to 1.1.x branch

@Xylus Xylus closed this as completed Jun 17, 2015
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@Xylus Xylus

Labels
bug enhancement
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
1 participant
@Xylus