-
Notifications
You must be signed in to change notification settings - Fork 578
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
Document how to enable/disable Debug Output on the fly #9981
Conversation
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.
Pls. rebase!
doc/15-troubleshooting.md
Outdated
* Hence, the debug log is enabled exactly as long as desired | ||
|
||
However, in case of [a HA zone](06-distributed-monitoring.md#distributed-monitoring-scenarios-ha-master-agents) | ||
the feature gets enabled/disabled on both nodes once they're connected. |
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.
⚠️ Thing to consider
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.
What did happen to this consideration? I mean it's clearly a bug, but I didn't get why posted such a prominent warning here and doing nothing about it.
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.
why posted such a prominent warning here
This PR (necessarily) "sells" the user a shiny HA feature which has a bug which may negatively affect what the user's doing inspired by this PR. Hence, you as reviewers may reconsider the PR as whole...
and doing nothing about it
... because, should we really make a disclaimer in the docs like, HA may be not reliable?
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.
... because, should we really make a disclaimer in the docs like, HA may be not reliable?
No, I wouldn't do it either, as the bug literally impacts every Icinga 2 object. I just didn't get the purpose of this comment with a prominent and eye catching warning sign.
4071e2f
to
a1825f0
Compare
a1825f0
to
9eff386
Compare
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 like this feature and think it might help users if we document it. Thus, unless there are technical limitations, I would like to see it in the manual.
doc/15-troubleshooting.md
Outdated
at runtime. This is a good alternative to `icinga2 feature enable debuglog`: | ||
|
||
* Object creation/deletion via API happens immediately and requires no restart | ||
* Hence, the debug log is enabled exactly as long as desired |
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.
at runtime. This is a good alternative to `icinga2 feature enable debuglog`: | |
* Object creation/deletion via API happens immediately and requires no restart | |
* Hence, the debug log is enabled exactly as long as desired | |
at runtime. | |
This is a good alternative to `icinga2 feature enable debuglog` as object | |
creation/deletion via API happens immediately and requires no restart. |
I would just continue with text, as the list makes it harder to read. Furthermore, the second bullet point adds no real value, imo.
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.
the second bullet point adds no real value, imo.
Well, if your reload takes 1/2h, your debug log is enabled for 1/2h longer than necessary, spamming the disk. And if your setup is that large, it will spam a lot.
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.
This totally makes sense. Could you then please add this information to the documentation, because for me this was not the obvious intent of the second sentence.
Btw, I am in favor of this PR and come back to it occasionally, for example, just this morning.
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.
As stated above, the bullet list is hard to read. The second point is obsolete with the just introduced paragraph below. Please remove it.
9eff386
to
4fea1ef
Compare
doc/15-troubleshooting.md
Outdated
at runtime. This is a good alternative to `icinga2 feature enable debuglog`: | ||
|
||
* Object creation/deletion via API happens immediately and requires no restart | ||
* Hence, the debug log is enabled exactly as long as desired |
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.
As stated above, the bullet list is hard to read. The second point is obsolete with the just introduced paragraph below. Please remove it.
b94eca4
to
593ddce
Compare
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.
Just this small nitpick of a double space, otherwise I am happy with it.
7fcfd4c
to
d2e20a6
Compare
This is a good alternative to `icinga2 feature enable debuglog`: * Object creation/deletion via API happens immediately and requires no restart * Hence, the debug log is enabled exactly as long as desired Co-authored-by: alvar <[email protected]>
675b3dc
to
e889528
Compare
This is a good alternative to
icinga2 feature enable debuglog
: