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 #10818] Use NodeName in null and random checks #3765

Closed
icinga-migration opened this issue Dec 10, 2015 · 2 comments
Closed

[dev.icinga.com #10818] Use NodeName in null and random checks #3765

icinga-migration opened this issue Dec 10, 2015 · 2 comments
Labels
bug
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Dec 10, 2015

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10818

Created by mfriedrich on 2015-12-10 14:14:00 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2015-12-10 14:30:03 +00:00)
Target Version: 2.4.2
Last Update: 2015-12-10 14:30:03 +00:00 (in Redmine)

Icinga Version: 2.4.1
Backport?: Already backported
Include in Changelog: 1

Utility::GetFqdn() is pretty expensive.

Changesets

2015-12-10 14:27:49 +00:00 by mfriedrich dc85b1c

Use NodeName instead of GetFQDN() in embedded checks

fixes #10818

2015-12-10 14:28:48 +00:00 by mfriedrich e623394

Use NodeName instead of GetFQDN() in embedded checks

fixes #10818
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Dec 10, 2015

Updated by mfriedrich on 2015-12-10 14:28:57 +00:00

  • Target Version changed from 2.5.0 to 2.4.2
  • Backport? changed from Not yet backported to Already backported
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Dec 10, 2015

Updated by mfriedrich on 2015-12-10 14:30:03 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset dc85b1c.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.