Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recently Recovered Services in dashboard "Current Incidents" seems out of order #3931

Closed
mtdeguzis opened this issue Aug 26, 2019 · 4 comments · Fixed by #3946
Closed

Recently Recovered Services in dashboard "Current Incidents" seems out of order #3931

mtdeguzis opened this issue Aug 26, 2019 · 4 comments · Fixed by #3946
Assignees
Labels
area/dashboard Affects the dashboard bug Something isn't working
Milestone

Comments

@mtdeguzis
Copy link

mtdeguzis commented Aug 26, 2019

Describe the bug

Clicking on a service in the main built-in "Current Incidents" dashboard orders "Recovered Services" above. This makes parsing difficult when things get busy, as it pushes the actual service issues further down. I don't believe this was the behavior prior to Icingaweb2 2.7.0

Screen Shot 2019-08-26 at 10 58 50 AM

Screen Shot 2019-08-26 at 11 03 03 AM

To Reproduce

Provide a link to a live example, or an unambiguous set of steps to reproduce this issue. Include configuration, logs, etc. to reproduce, if relevant.

  1. Install Icinagweb 2.7.0+

Expected behavior

The host/service problems should be presented first for the "Current Incidents" dashboard.

Your Environment

Include as many relevant details about the environment you experienced the problem in

  • Icinga Web 2 version and modules (System - About):
Icinga Web 2 Version
2.7.1
Git commit
b0bf9c4b0637f6113adb788e78c2bcf619225dd8
PHP Version
7.1.30
Git commit date
2019-08-14
  • Web browser used: Chrome/Firefox
  • Icinga 2 version used (icinga2 --version): r2.10.5-1
  • PHP version used (php --version):
/opt/rh/rh-php71/root/usr/sbin/php-fpm --version | head -n 1 | awk '{print $2}'
7.1.30
  • Server operating system and version:
# cat /etc/os-release 
NAME="Red Hat Enterprise Linux Server"
VERSION="7.7 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.7"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.7 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.7:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.7
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.7"
@log1-c
Copy link
Contributor

log1-c commented Aug 27, 2019

Can confirm, that when having English selected as language, the Recently Recovered Services list will be placed above the Service Problems list, after clicking on on of the recently recovered checks.
image

With a dashboard set to German language this does not happen.
image

@nilmerg nilmerg added area/dashboard Affects the dashboard bug Something isn't working labels Sep 9, 2019
@nilmerg nilmerg added this to the 2.7.2 milestone Sep 9, 2019
@nilmerg nilmerg self-assigned this Sep 9, 2019
nilmerg added a commit that referenced this issue Sep 9, 2019
@mtdeguzis
Copy link
Author

mtdeguzis commented Oct 17, 2019

The default order now in 2.11.0-1 appears to be

  1. service problems
  2. Recently recovered services
  3. Host problems

Should this order always be:

  1. service problems
  2. host problems
  3. Recently recovered 1 or 2

OR (per the German lang screenshot above)

  1. host problems
  2. service problems
  3. Recently recovered 1 or 2

?

image

# icinga2 --version
icinga2 - The Icinga 2 network monitoring daemon (version: 2.11.0-1)

Am I incorrect here, or should I open a new issue?

@nilmerg
Copy link
Member

nilmerg commented Oct 17, 2019

Nope. The order with v2.6.3 is:

  1. service problems
  2. Recently recovered services
  3. Host problems

And that's what it is for me with v2.7.2.

@mtdeguzis
Copy link
Author

Got it @nilmerg , thanks for confirming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard Affects the dashboard bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants