-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add '_monitoring' suffix to monitoring process names #27852
Conversation
Add '_monitoring' suffix to monitoring process names so that they can be distinguised from other processes. This is relevent for the status command where the beat instances appear the same in output. Changed the output format of the human readable option to better align text with the longer names.
Pinging @elastic/agent (Team:Agent) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change LGTM, left one question.
It would be nice to have tests in place for the different output formats. In case we could use golden files or similar it would make changes like this every easy to review on what the exact change is it has on the output.
} | ||
|
||
if p.ServicePort() == 0 { | ||
// Applications without service ports defined are ran as through the process application type. | ||
a, err = process.NewApplication( | ||
o.bgContext, | ||
p.ID(), | ||
p.BinaryName(), | ||
appName, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this has any effect in other places except the status output? Hopefully a positive impact but we should double check in case we do any comparison on appName.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I can see it should be safe to change it like this, the Application
that is returned exposes it for use by other processes with the Name
function
* Add '_monitoring' suffix to monitoring process names Add '_monitoring' suffix to monitoring process names so that they can be distinguished from other processes. This is relevant for the status command where the beat instances appear the same in output. Changed the output format of the human readable option to better align text with the longer names. (cherry picked from commit eb0a886)
* Add '_monitoring' suffix to monitoring process names Add '_monitoring' suffix to monitoring process names so that they can be distinguished from other processes. This is relevant for the status command where the beat instances appear the same in output. Changed the output format of the human readable option to better align text with the longer names. (cherry picked from commit eb0a886) Co-authored-by: Michel Laterman <[email protected]>
* Add '_monitoring' suffix to monitoring process names Add '_monitoring' suffix to monitoring process names so that they can be distinguished from other processes. This is relevant for the status command where the beat instances appear the same in output. Changed the output format of the human readable option to better align text with the longer names.
What does this PR do?
Add '_monitoring' suffix to monitoring process names so that they can be
distinguished from other processes. This is relevant for the status
command where the beat instances appear the same in output. Changed the
output format of the human readable option to better align text with the
longer names.
Why is it important?
Allows users to determine if the monitoring instances, or "regular" beats instances are healthy.
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
run
elastic-agent status
Related issues
Logs
Example of the new output: