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.

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

Closed
icinga-migration opened this issue Nov 29, 2016 · 4 comments · Fixed by #6326
Closed
Assignees
Labels
enhancement New feature or request queue/wishlist
Milestone

Comments

@icinga-migration
Copy link

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)

Backport?: Not yet backported
Include in Changelog: 1

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

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-12-08 00:26:05 +00:00

  • Status changed from New to Feedback
  • Assigned to set to twidhalm

Propose an attribute name where you would store this information then please.

@icinga-migration icinga-migration added needs feedback We'll only proceed once we hear from you again Low enhancement New feature or request labels Jan 17, 2017
@dnsmichi
Copy link
Contributor

dnsmichi commented Mar 9, 2017

@widhalmt ping?

@dnsmichi dnsmichi added help wanted Extra attention is needed and removed needs feedback We'll only proceed once we hear from you again labels Sep 6, 2017
@dnsmichi
Copy link
Contributor

dnsmichi commented Sep 6, 2017

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.

@widhalmt
Copy link
Member

widhalmt commented Sep 6, 2017

  • scheduler
  • scheduling_endpoint
  • scheduling_node

Sorry I didn't give feedback. I might not be creative enough for creating new attributes.

mcktr added a commit that referenced this issue May 22, 2018
This implements the attribute `scheduling_endpoint` for hosts and services to show which endpoint is running the scheduler for the check.

refs #4814
mcktr added a commit that referenced this issue Aug 1, 2018
This implements the attribute `scheduling_endpoint` for hosts and services to show which endpoint is running the scheduler for the check.

refs #4814
@Al2Klimov Al2Klimov removed the help wanted Extra attention is needed label May 15, 2020
mcktr added a commit that referenced this issue Jul 18, 2021
This implements the attribute `scheduling_endpoint` for hosts and services to show which endpoint is running the scheduler for the check.

refs #4814
Al2Klimov pushed a commit that referenced this issue Jul 20, 2021
* 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
@icinga-probot icinga-probot bot added this to the 2.13.0 milestone Jul 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request queue/wishlist
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants