Closed dannycohen closed 10 years ago
Too much technical detail. Also OPS will be interacting with SP, so this requirement is really a SP one.
I've opened the issue in SP - https://github.com/Particular/ServicePulse/issues/94
@johnsimons - See requirement for technical detail in https://github.com/Particular/ServicePulse/issues/94#issuecomment-34537292
It can be added now or later, here or in SP repo, but we need the technical details well defined so we align SI (since this applies to SI as well as to SP, as specified above).
What's this "we"? We all the same people here, I'm capable of doing SP and SI changes given the requirements.
On Saturday, 8 February 2014, Danny Cohen notifications@github.com wrote:
@johnsimons https://github.com/johnsimons - See requirement for technical detail in Particular/ServicePulse#94 (comment)https://github.com/Particular/ServicePulse/issues/94#issuecomment-34537292
It can be added now or later, here or in SP repo, but we need the technical details well defined so we align SI (since this applies to SI as well as to SP, as specified above).
Reply to this email directly or view it on GitHubhttps://github.com/Particular/ServiceControl/issues/180#issuecomment-34537317 .
@johnsimons - "we", includes anyone who is interested in knowing what you are planning to do.
This may include but is not limited to:
In general, I am asking that whatever format you define - please describe it.
As Opie, I need to be able to uniquely identify the specific endpoint hosting process that sent a heartbeat. This is especially true when more than one instance of the endpoints is located in the same machine (AKA "side by side") It also applies when the endpoint is hosted in IIS or other custom hosting.
Visualization
Proposed Implementation