Hi All,
We've got a large number of templated trapper type items. The item delay value in the database, although not used for polling, is scewing the QPS dashboard value. Can I suggest that the QPS calculation take this into account and ignore trapper items?
SELECT sum(qps) AS qps FROM ( SELECT count(*),count(*)/i.delay as qps FROM items i,hosts h WHERE i.status=0 AND i.hostid=h.hostid AND h.status=0 and i.type!=2 GROUP BY i.type,i.delay ORDER BY i.type, i.delay ) as data;'
+---------+
| qps |
+---------+
| 59.0551 |
+---------+
versus
SELECT sum(qps) AS qps FROM ( SELECT count(*),count(*)/i.delay as qps FROM items i,hosts h WHERE i.status=0 AND i.hostid=h.hostid AND h.status=0 GROUP BY i.type,i.delay ORDER BY i.type, i.delay ) as data;'
+----------+
| qps |
+----------+
| 406.7296 |
+----------+
temporary 'workaround' is 'update items set delay=99999 where type=2;'
-Cheers Max.
We've got a large number of templated trapper type items. The item delay value in the database, although not used for polling, is scewing the QPS dashboard value. Can I suggest that the QPS calculation take this into account and ignore trapper items?
SELECT sum(qps) AS qps FROM ( SELECT count(*),count(*)/i.delay as qps FROM items i,hosts h WHERE i.status=0 AND i.hostid=h.hostid AND h.status=0 and i.type!=2 GROUP BY i.type,i.delay ORDER BY i.type, i.delay ) as data;'
+---------+
| qps |
+---------+
| 59.0551 |
+---------+
versus
SELECT sum(qps) AS qps FROM ( SELECT count(*),count(*)/i.delay as qps FROM items i,hosts h WHERE i.status=0 AND i.hostid=h.hostid AND h.status=0 GROUP BY i.type,i.delay ORDER BY i.type, i.delay ) as data;'
+----------+
| qps |
+----------+
| 406.7296 |
+----------+
temporary 'workaround' is 'update items set delay=99999 where type=2;'
-Cheers Max.