Previously, command forms were responsible for this. But they
don't have any notion of fallback handling and are unable to
ensure proper re-submission of failed batches.
Reduces risk of timeouts in case Icinga takes its time to respond.
The timeout of 15 seconds introduced earlier has been kept.
Chunk sizes were chosen as follows:
- 1000: Cheap calculations (object features, check scheduling)
- 500: Expected disk writes (comments)
- 250: Process check result, Downtimes, Acks
I propose to add a new option for setting a default comment for
acknowledging problems (`acknowledge_comment_text`), similar to the
existing `hostdowntime_comment_text` and `servicedowntime_comment_text`
options.
This originally was a pull request for Icinga Web 2
(https://github.com/Icinga/icingaweb2/pull/5365). I was asked to
implement this in Icinga DB Web as well. *However, since I'm not using
Icinga DB Web myself, this is untested.*
Beside adding the new feature, I also fixed a copy-and-paste error for
the `servicedowntime_comment_text` option.
* Command forms: Use strict interfaces to construct ipl\Html objects
* BaseTableRowItem: Use strict interfaces to create ipl\Html objects
* ObjectInspectionDetail: Use strict interfaces..
..to create ipl\Html objects
* Setup/*Step: Use strict interfaces to create ipl\Html objects
* ObjectSuggestions: Use strict interfaces to create ipl\Html objects
* Widget: Use strict interfaces to create ipl\Html objects
* Widget\Detail: Use strict interfaces to create ipl\Html objects
* Widget\ItemList: Use strict interfaces to create ipl\Html objects
* ServiceLink: Don't return an array
