[dev.icinga.com #9059] Can't initiate an ascending sort by host or service severity

[icinga-migration]

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

Created by jmeyer on 2015-04-14 11:19:14 +00:00

Assignee: elippmann
Status: Resolved (closed on 2015-05-21 10:25:04 +00:00)
Target Version: 2.0.0-rc1
Last Update: 2015-05-21 10:25:04 +00:00 (in Redmine)

---

Descending is hardcoded in DataView\HostStatus and DataView\ServiceStatus.

Changesets

2015-05-13 15:48:34 +00:00 by aklimov 7e1f9f6

Make ascending sort by host or service severity initiatable

fixes #9059

2015-05-15 09:19:52 +00:00 by aklimov 386d4db

Make ascending sort by host or service severity initiatable

fixes #9059

2015-05-21 10:20:18 +00:00 by elippmann 82f9425

Revert "Make ascending sort by host or service severity initiatable"

This reverts commit 386d4db851aed056652d892d539de35b403c5062.

The commit introduced the bug that changing the sort direction no longer changed the sort direction :)

refs #9059

2015-05-21 10:20:18 +00:00 by elippmann 195275a

monitoring: Don't hardcode sort direction of the severity columns

fixes #9059

---

Relations:

• duplicates #9059

[icinga-migration]

Updated by aklimov on 2015-05-13 15:41:57 +00:00

• Status changed from New to Assigned
• Assigned to set to aklimov

[icinga-migration]

Updated by aklimov on 2015-05-13 15:50:03 +00:00

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

Applied in changeset 7e1f9f6.

[icinga-migration]

Updated by jmeyer on 2015-05-15 08:55:36 +00:00

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

Please fix this as we've discussed it just now :)

[icinga-migration]

Updated by aklimov on 2015-05-15 09:25:04 +00:00

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

Applied in changeset 386d4db.

[icinga-migration]

Updated by elippmann on 2015-05-21 10:10:40 +00:00

• Status changed from Resolved to Assigned
• Assigned to changed from aklimov to elippmann

After the last change changing the sort direction no longer has an effect.

[icinga-migration]

Updated by elippmann on 2015-05-21 10:18:12 +00:00

• Duplicated set to 8780

[icinga-migration]

Updated by icinga-kanban on 2015-05-21 10:22:37 +00:00

Build !#766 triggered by the commits 195275a, 82f9425 passed successfully.

Branch: origin/master
Author: Eric Lippmann

[icinga-migration]

Updated by elippmann on 2015-05-21 10:25:04 +00:00

• Status changed from Assigned to Resolved

Applied in changeset 195275a.

[gogowitsch]

I have a general usage question: where does one set the severity of a service?

[lazyfrosch]

@fonata please do not comment to a very old issue.

Severity is calculated from Icinga Status information in the IDO, so that we can sort criticality.

It is inside a SQL query currently:

icingaweb2/modules/monitoring/library/Monitoring/Backend/Ido/Query/ServicestatusQuery.php

Line 104 in c547f4c

'host_severity' => 'CASE WHEN hs.current_state = 0

Please open a new issue if you have problems or further questions