[dev.icinga.com #8765] Explain processing logic/order of apply rules with for loops

[icinga-migration]

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

Created by jmeyer on 2015-03-16 14:14:07 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2015-03-19 17:05:09 +00:00)
Target Version: 2.3.3
Last Update: 2015-03-19 17:05:09 +00:00 (in Redmine)

Icinga Version: v2.3.0-11-g8682c53
Backport?: Not yet backported
Include in Changelog: 1

---

Neither in Apply's reference manual nor in the section "Using Apply For Rules" as part of the chapter "Monitoring Basics" it is stated that the for loop is being evaluated for each host in a O (N2) manner. While that is obvious when taking a second look at the definition, users will benefit from a more detailed explanation though.

Changesets

2015-03-19 17:03:01 +00:00 by (unknown) 0c0bae2

Documentation: Revamp migration/object accessors, fix several items

fixes #8764
fixes #8771
fixes #8765
fixes #8686
fixes #8740

2015-03-19 17:03:48 +00:00 by (unknown) df99eab

Documentation: Revamp migration/object accessors, fix several items

fixes #8764
fixes #8771
fixes #8765
fixes #8686
fixes #8740

[icinga-migration]

Updated by mfriedrich on 2015-03-19 09:34:44 +00:00

• Status changed from New to Assigned
• Assigned to set to mfriedrich
• Target Version set to 2.3.3
• Estimated Hours set to 1

[icinga-migration]

Updated by mfriedrich on 2015-03-19 09:34:44 +00:00

• Status changed from New to Assigned
• Assigned to set to mfriedrich
• Target Version set to 2.3.3
• Estimated Hours set to 1

[icinga-migration]

Updated by Anonymous on 2015-03-19 17:05:09 +00:00

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

Applied in changeset 0c0bae2.

[icinga-migration]

Updated by Anonymous on 2015-03-19 17:05:09 +00:00

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

Applied in changeset 0c0bae2.