[dev.icinga.com #10026] Provide more intuitive input methos for time based filter elements

[icinga-migration]

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

Created by mjentsch on 2015-08-28 08:14:23 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2016-05-06 15:39:20 +00:00 (in Redmine)

---

Right now, you can either specify a unix timestamp or a human-readable relative time period like "-1 days". None
of this is really obvious to the user, since there aren't any hints besides an empty text field.

We need to find a way to communicate what kind of input is expected to the user, either in the form of a
Combobox that offers autocompletion or presets, or at least some "help" icon that explains the possible inputs.

---

Relations:

• relates #8937
• relates #10026
• duplicates #10026
• duplicates #10026
• duplicates #10026

[icinga-migration]

Updated by elippmann on 2016-02-15 22:46:54 +00:00

• Subject changed from Provide more intuitive input methos for Time-based filter elements to Provide more intuitive input methos for time based filter elements
• Category set to Framework
• Target Version set to Backlog

[icinga-migration]

Updated by elippmann on 2016-02-18 11:39:25 +00:00

• Duplicated set to 11089

[icinga-migration]

Updated by elippmann on 2016-02-18 11:40:08 +00:00

• Relates set to 8937

[icinga-migration]

Updated by elippmann on 2016-02-19 09:20:33 +00:00

• Relates set to 10849

[icinga-migration]

Updated by jmeyer on 2016-04-21 07:47:15 +00:00

• Duplicated set to 11629

[icinga-migration]

Updated by ClemensBW on 2016-05-06 15:39:20 +00:00

+1 ;o)

A option to select "service is more as 5 Minutes in state xyz" (if you dont have a escalation or notification for this)

We use now as workaround [service=ping4&service_current_check_attempt>=3&service_attempt>=3] that you don't see in icingaweb2 all pings they are only a few seconds in bad state.

[icinga-migration]

Updated by jmeyer on 2016-10-04 11:26:25 +00:00

• Duplicated set to 12734

[nilmerg]

We should think of this as part of #4094.