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
[dev.icinga.com #13355] Show which host is running the scheduler for a check #4814
Comments
Updated by mfriedrich on 2016-12-08 00:26:05 +00:00
Propose an attribute name where you would store this information then please. |
@widhalmt ping? |
No feedback, I'm leaving this here for suggestions and PRs. Should be easy to implement inside the CheckResult class following check_source. Might need checks for older versions which do not provide the new attribute. |
Sorry I didn't give feedback. I might not be creative enough for creating new attributes. |
This implements the attribute `scheduling_endpoint` for hosts and services to show which endpoint is running the scheduler for the check. refs #4814
This implements the attribute `scheduling_endpoint` for hosts and services to show which endpoint is running the scheduler for the check. refs #4814
This implements the attribute `scheduling_endpoint` for hosts and services to show which endpoint is running the scheduler for the check. refs #4814
* Implement scheduling_source attribute This implements the attribute `scheduling_source` for hosts and services to show which endpoint is running the scheduler for the check. refs #4814
This issue has been migrated from Redmine: https://dev.icinga.com/issues/13355
Created by twidhalm on 2016-11-29 15:08:50 +00:00
Assignee: twidhalm
Status: Feedback
Target Version: (none)
Last Update: 2016-12-08 00:26:05 +00:00 (in Redmine)
Hi,
I'd really like to see which Icinga 2 instance scheduled a check I can see in Icinga Web 2. Since the behaviour of "check source" changed, I miss this information.
I spoke to Eric wether this is an issue for Icinga Web 2 or Icinga 2 and he told me, Icinga Web 2 has no access to this information.
Cheers,
Thomas
The text was updated successfully, but these errors were encountered: