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

Filter in tactical view gives different results for Icing IDO Web and Icinga DB Web #1092

Open
johannesst opened this issue Nov 13, 2024 · 0 comments

Comments

@johannesst
Copy link

Describe the bug

Using the same filter conditions in the tactical overview yield different results in the IDO-based IcingaWeb and IcingaDB Web frontends.

To Reproduce

  1. Open IcingaIDO tactical overview and specify a filter:
    image
  2. Open IcingaDB tactical overview and enter the same conditions:
    image
  3. Open IcingaDB tactical overview and specify a filter with !~ instead of !=;
    image
    As you can see the tactical overview in IcingaDB gives different service and hosts counts compared to IcingaIDO.

Expected behavior

One of the filters should return the same amount of hosts and services like with Icigna IDO.

Your Environment

image

  • Icinga DB Web version (System - About): 1.1.3

  • Icinga Web 2 version (System - About): 2.12.1

  • Web browser: Google Chrome Version 130.0.6723.117 (Offizieller Build) (64-Bit) Windows 10 22H2 Build 19045.5011

  • Icinga 2 version (icinga2 --version): r2.14.3-1

  • Icinga DB version (icingadb --version): Icinga DB version: v1.2.0

  • Icinga Redis (icinga-redis-server --version): icingadb-redis-server --version
    Redis server v=7.2.6 sha=4e7416a9:0 malloc=jemalloc-5.3.0 bits=64 build=fec6fb8a9e0b305c

  • PHP version used (php --version): PHP 8.1.2-1ubuntu2.19 (cli) (built: Sep 30 2024 16:25:25) (NTS)

  • Server operating system and version: Ubuntu 22.04.5 LTS, 5.15.0-125-generic Comment/Downtime List: Remove object names in detail view #135-Ubuntu SMP Fri Sep 27 13:53:58 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Additional context

The Icinga cluster was initially set up with two master nodes and one mariadb database five years ago. I added IcingaDB yesterday, both frontends are now running parallel.
Following modules are used at the moment:
image
And following feature are used:
sudo icinga2 feature list
Disabled features: compatlog debuglog elasticsearch gelf graphite influxdb2 journald livestatus opentsdb perfdata statusdata syslog
Enabled features: api checker command icingadb ido-mysql influxdb mainlog notification

Remarks

Maybe I'm missing something is there any documentation of the new filter format? I tried to look it up in the docs or with googling but to no avail. If there is anything I can do to help with debugging or testing I'm happy to help

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

No branches or pull requests

1 participant