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

CLI check command: WARNING in output displayed above CRITICAL #126

Closed
log1-c opened this issue Oct 15, 2019 · 1 comment
Closed

CLI check command: WARNING in output displayed above CRITICAL #126

log1-c opened this issue Oct 15, 2019 · 1 comment
Assignees
Milestone

Comments

@log1-c
Copy link

log1-c commented Oct 15, 2019

Expected Behavior

When using the integrated check command (e.g for checking datastores) and there are WARNING and CRITICAL problems the critical problems should be displayed on top, so they are seen in the overview.

Current Behavior

WARNING tags are displayed above the CRITICAL tags, thus having a check that is in CRITICAL state with a [WARNING] output:
image

image

Could be confusing

Steps to Reproduce (for bugs)

Not sure if this is always the case, I just noticed it today.

Your Environment

  • VMware vCenter®/ESXi™-Version: 6.7
  • Version/GIT-Hash of this module: e1ff220
  • Icinga Web 2 version: 2.7.1
  • Operating System and version: Ubuntu 18.04
  • Webserver, PHP versions:7.2.19-0ubuntu0.18.04.2, Apache 2
@Thomas-Gelf Thomas-Gelf self-assigned this Sep 14, 2020
@Thomas-Gelf Thomas-Gelf added this to the v1.2.0 milestone Sep 14, 2020
@Thomas-Gelf
Copy link
Contributor

It's not always the case, depends on involved object names too. However, this absolutely makes sense to me - will be implemented!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants