This ensures that exports to CSV/JSON contain results
for both host and service states as the default export
procedure only evaluates a single query.
fixes#1334
Previously `Url::setParams()` was used by `ServiceController::historyAction` to set `name` and `host.name`,
since the function overwrites all parameters the sort parameter was not included in the loadMoreUrl.
`UrlParams::addValues` fixes this problem sicne is keeps the existing parameters.
For consistency `HostController::historyAction` is also adjusted to match this implementation.
Adjust HostsController and ServicesController to use the new
ColumnChooser form and the TabularViewModeSwitcher.
The Controller class is adjusted to work with the TabularViewModeSwitcher
The HostGroupsController and ServiceGroupsController are adjusted,
to ensure they use with the GridViewModeSwitcher.
Since PHP 8.4 implicitly nullable parameter types are deprecated.
Normalize scoped PHPDoc for nullable-parameter updates: use `?Type` instead of
`Type|null` and remove column alignment.
Co-authored-by: "Eric Lippmann <eric.lippmann@icinga.com>"
Some versions of these RDBMS perform poorly with history queries, particularly
when the optimizer changes join order or uses block nested loop joins. Ideally,
testing across all RDBMS versions to identify when the optimizer fails and
adjusting queries or using optimizer switches would be preferable, but this
level of effort is not justified at the moment.
Optimizer is disabled via config:
`/etc/icingaweb2/modules/icingadb/config.ini`:
```
[icingadb]
...
disable_optimizer_for_history_queries=1
```
If saving the Redis settings fails due to a write error, the desired
configuration file content is now displayed so that the user can deploy
it manually (Same behavior as with database configuration).
For that a catch block is introduced on the `NotWritableError` that is
added to `IniWriter::write()` in
https://github.com/Icinga/icingaweb2/pull/5404.
Refs https://github.com/Icinga/icingaweb2/pull/5404Resolves#1269
This PR improves the UX in the IcingaDB Web interface by:
- Enhancing the page opening behavior in column views for smoother
navigation.
- Adding a search bar to the tabs Host Services, Host History and
Service History
## Resolves
- #981
- #1288
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.
If the problem toggle is created after the params are shifted, it
redirects to the page without them. To solve this I simply moved
the problem toggle before shifting the params.
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.
