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

establish linkerd "process path" ids #69

Closed
olix0r opened this issue Feb 3, 2016 · 1 comment
Closed

establish linkerd "process path" ids #69

olix0r opened this issue Feb 3, 2016 · 1 comment

Comments

@olix0r
Copy link
Member

olix0r commented Feb 3, 2016

For the purposes of debugging (and later, for control), we need a way to uniquely identify individual linkerd instances.

Process paths should be specified in the linkerd's runtime environment or generated by the linkerd instance at startup time. Process paths should provide debugging environment specific information (host names, namespaces, whatever is available). They may contain UUIDs if uniqueness cannot be guaranteed otherwise.
@olix0r olix0r added this to the 0.1.0 milestone Feb 3, 2016
@olix0r olix0r added the ready label Feb 3, 2016
@wmorgan wmorgan removed the ready label Feb 8, 2016
@gtcampbell gtcampbell removed this from the 0.1.0 milestone Feb 22, 2016
@olix0r
Copy link
Member Author

olix0r commented Sep 12, 2016

No pressing need for this.

@olix0r olix0r closed this as completed Sep 12, 2016
Tim-Brooks pushed a commit to Tim-Brooks/linkerd that referenced this issue Dec 20, 2018
@franziskagoltz
fix inconsistent deployment count on servicemesh page (linkerd#69)
3591936 
* fix inconsistent deployment count on servicemesh page.
* tests added for deploy count messaging on servicemesh page
* refactored code for Call To Action component to use 'instructions' in util
* refactored correlating css
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wmorgan @olix0r @gtcampbell