Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #5630] Report is showing 100% down, if no state change occurs in selected timeframe #68

Open
icinga-migration opened this issue Feb 10, 2014 · 5 comments
Labels
Milestone

Comments

@icinga-migration
Copy link

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

Created by wolle on 2014-02-10 14:27:43 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:17:56 +00:00 (in Redmine)

Icinga Version: 1.10.2
DB Type: MySQL
DB Version: Ver 14.14 Distrib 5.1.71, for redhat-linux-gnu (x86_64) using readline 5.1
Jasper Version: 5.5.0

Hi,

Reporting is showing me 100% outage for a selected timeframe, if no state change has happened for this period. Maybe this bug is related to #4511 and #4152.

mysql> select * from icinga_statehistory where icinga_statehistory.object_id=3215 and state_time >'2013-10-01 00:00:00';
+-----------------+-------------+---------------------+-----------------+-----------+--------------+-------+------------+----+
| statehistory_id | instance_id | state_time          | state_time_usec | object_id | state_change | state | state_type | cur|
+-----------------+-------------+---------------------+-----------------+-----------+--------------+-------+------------+----+
|          446632 |           1 | 2013-10-03 07:31:02 |          253414 |      3215 |            1 |     3 |          0 |    |
|          446633 |           1 | 2013-10-03 07:32:17 |          252440 |      3215 |            1 |     2 |          0 |    |
|          446640 |           1 | 2013-10-03 07:35:02 |           99212 |      3215 |            1 |     0 |          0 |    |
+-----------------+-------------+---------------------+-----------------+-----------+--------------+-------+------------+----+

Faulty Report - No State Change Events in Timeframe

reporting-error.PNG

OK Report - One State Change Event in Timeframe

reporting-ok.PNG

No downtime has been set in this period:

mysql> select * from icinga_downtimehistory where icinga_downtimehistory.object_id=390;
Empty set (0.01 sec)

Regards,
wolle

Attachments

@icinga-migration
Copy link
Author

Updated by wolle on 2014-02-10 14:31:10 +00:00

Sorry, wrong select Statement. This is right:

mysql> select * from icinga_statehistory where icinga_statehistory.object_id=390 and state_time >'2013-10-01 00:00:00';
+-----------------+-------------+---------------------+-----------------+-----------+--------------+-------+------------+-----------------------+--------------------+
| statehistory_id | instance_id | state_time          | state_time_usec | object_id | state_change | state | state_type | current_check_attempt | max_check_attempts |
+-----------------+-------------+---------------------+-----------------+-----------+--------------+-------+------------+-----------------------+--------------------+
|          526461 |           1 | 2013-12-06 14:12:28 |          754755 |       390 |            1 |     1 |          1 |                     1 |                  3 |
|          526474 |           1 | 2013-12-06 14:38:08 |          308590 |       390 |            1 |     0 |          1 |                     1 |                  3 |
|          526476 |           1 | 2013-12-06 14:40:23 |          273102 |       390 |            1 |     1 |          1 |                     1 |                  3 |
|          526477 |           1 | 2013-12-06 14:40:43 |          318458 |       390 |            1 |     0 |          1 |                     1 |                  3 |
|          526478 |           1 | 2013-12-06 14:41:03 |          802124 |       390 |            1 |     1 |          1 |                     1 |                  3 |
|          526481 |           1 | 2013-12-06 14:41:53 |          546174 |       390 |            1 |     0 |          1 |                     1 |                  3 |
|          526485 |           1 | 2013-12-06 14:46:53 |          994032 |       390 |            1 |     1 |          1 |                     1 |                  3 |
|          528475 |           1 | 2013-12-09 07:36:59 |          278991 |       390 |            1 |     0 |          1 |                     3 |                  3 |
+-----------------+-------------+---------------------+-----------------+-----------+--------------+-------+------------+-----------------------+--------------------+
8 rows in set (0.00 sec)

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-02-10 15:00:45 +00:00

  • Target Version deleted 1.10.2

@icinga-migration
Copy link
Author

Updated by berk on 2015-05-18 12:17:56 +00:00

  • Target Version set to Backlog

@icinga-migration icinga-migration added this to the Backlog milestone Jan 17, 2017
@choonming
Copy link

Any idea when this bug will be fixed?

@NeverUsedID
Copy link

I can reproduce this bug. No workaround found so far.

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

No branches or pull requests

3 participants