| *** ivve has quit IRC | 00:16 | |
| openstackgerrit | Merged openstack/ceilometer stable/stein: Fix samples with dots in sample name https://review.opendev.org/692927 | 02:00 |
|---|---|---|
| openstackgerrit | Merged openstack/ceilometer stable/rocky: Fix samples with dots in sample name https://review.opendev.org/692928 | 02:03 |
| *** joadavis has quit IRC | 04:07 | |
| *** joadavis has joined #openstack-telemetry | 04:07 | |
| *** tkajinam has quit IRC | 05:02 | |
| *** tkajinam has joined #openstack-telemetry | 05:33 | |
| *** tkajinam_ has joined #openstack-telemetry | 07:18 | |
| *** tkajinam_ has quit IRC | 07:19 | |
| *** tkajinam_ has joined #openstack-telemetry | 07:20 | |
| *** tkajinam has quit IRC | 07:21 | |
| *** witek_ has joined #openstack-telemetry | 07:36 | |
| *** tesseract has joined #openstack-telemetry | 08:16 | |
| *** bengates has joined #openstack-telemetry | 08:22 | |
| *** mrunge_ is now known as mrunge | 08:41 | |
| *** ivve has joined #openstack-telemetry | 08:51 | |
| *** tkajinam_ has quit IRC | 09:20 | |
| *** dasp has quit IRC | 09:42 | |
| *** dasp has joined #openstack-telemetry | 09:43 | |
| *** rcernin has quit IRC | 10:06 | |
| *** pcaruana has joined #openstack-telemetry | 10:08 | |
| *** intmc has joined #openstack-telemetry | 10:10 | |
| intmc | Hi folks, I have a question on aodh. I'm trying to understand how the evaluator works when using granularity 1 and evaluation period 1. | 10:13 |
| intmc | The main doubt is around the evaluator running every X seconds instead, so what will the evaluator do in this case, will it look back at the datapoints for the last X seconds and match the condition if one sample over the timespan is matching? | 10:14 |
| intmc | Or will it just look at the last sample when running every X seconds? | 10:14 |
| intmc | from the logs it seems it just reads one sample... so if the sampling is finer than the evaluation period it will only read one sample, the one loaded at the evaluation cycle... is that right? | 10:21 |
| *** lpetrut has joined #openstack-telemetry | 10:34 | |
| *** witek_ has quit IRC | 10:41 | |
| intmc | I am afraid aodh is bugged, it doesn't always trigger the alarm | 11:18 |
| intmc | if I look at the output of gnocchi from 'openstack metric measures show' I can clearly see values that should trigger the alarm, but it doesn't always do so | 11:19 |
| *** bengates has quit IRC | 11:33 | |
| *** bengates has joined #openstack-telemetry | 11:33 | |
| *** lpetrut has quit IRC | 11:53 | |
| *** bengates has quit IRC | 11:55 | |
| *** bengates has joined #openstack-telemetry | 11:56 | |
| *** witek has joined #openstack-telemetry | 12:06 | |
| *** bengates has quit IRC | 12:15 | |
| *** bengates has joined #openstack-telemetry | 12:16 | |
| *** monitornoob has joined #openstack-telemetry | 12:30 | |
| monitornoob | Hi all. I'm trying to wrap my head around telemetry in my deployed openstack. Seems that over the years things have changed considerably with gnocchi and ceilometer (and now aodh). | 12:32 |
| monitornoob | Are there any good tutorials about telemetry/monitoring to help me how best to apply monitoring to my stack - as the official documentation tends to lack in some capacities. | 12:34 |
| monitornoob | I think my deployment has some default metrics being monitored - but not sure if my gnocchi is broken. Redis and ceilometer suggest they are working fine, but Gnocchi reports "ERROR gnocchi.cli.metricd: Unexpected error updating the task partitioner: Unknown node `overcloud-controller-0.X.X.xxxxxx-xxxx-xxxxxx-xxxxx` for a few uuids | 12:40 |
| *** dasp has quit IRC | 13:12 | |
| *** dasp has joined #openstack-telemetry | 13:12 | |
| *** monitornoob has quit IRC | 13:34 | |
| *** lpetrut has joined #openstack-telemetry | 13:40 | |
| *** dave-mccowan has joined #openstack-telemetry | 14:02 | |
| *** pcaruana has quit IRC | 14:33 | |
| *** dave-mccowan has quit IRC | 14:42 | |
| *** pcaruana has joined #openstack-telemetry | 15:04 | |
| *** tesseract has quit IRC | 15:37 | |
| *** tesseract has joined #openstack-telemetry | 15:48 | |
| intmc | ok, so if the granularity is lower than the evaluation period aodh won't work. I see from the log it looks +/-1 granularity period, not the the whole series from the last scan. I think this is a design error | 15:50 |
| intmc | it also seems to be unreliable in certain cases when the close to the evaluation period | 15:50 |
| *** jmlowe has quit IRC | 15:52 | |
| *** jmlowe has joined #openstack-telemetry | 16:09 | |
| *** ivve has quit IRC | 16:15 | |
| *** dave-mccowan has joined #openstack-telemetry | 16:19 | |
| *** lpetrut has quit IRC | 16:38 | |
| *** bengates has quit IRC | 16:43 | |
| *** tesseract has quit IRC | 17:03 | |
| *** witek has quit IRC | 17:18 | |
| *** jmlowe has quit IRC | 18:15 | |
| *** jmlowe has joined #openstack-telemetry | 18:15 | |
| *** jmlowe has quit IRC | 18:24 | |
| *** jmlowe has joined #openstack-telemetry | 18:39 | |
| *** gmann is now known as gmann_afk | 19:00 | |
| *** ivve has joined #openstack-telemetry | 19:28 | |
| *** gmann_afk is now known as gmann | 20:25 | |
| *** pcaruana has quit IRC | 22:06 | |
| *** tkajinam has joined #openstack-telemetry | 22:56 | |
| *** rcernin has joined #openstack-telemetry | 22:57 | |
| *** ivve has quit IRC | 23:47 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!