Wednesday, 2021-12-08

rsarto@mrunge: can you give more details on how that depends on my setup?12:10
mrungersarto: sorry, I do not remember your question12:11
rsartomrunge: no problem, this is my question: Now that Panko has been deprecated, where are the events stored?12:13
mrungeah!12:13
mrungeThey are not.12:13
mrungesome are still stored in gnocchi12:13
mrungeinserted as metric in gnocchi12:13
mrungethat does not really solve any problem12:13
mrungersarto: first of all, you are the first one to ask for panko in a couple of years12:14
mrungemy proposal would be to store events e.g in a elasticsearch instance12:15
mrungeor in loki, or else12:15
rsartomrunge: so we're just removing panko from the stack and/or trying to use gnocchi for some concepts...12:15
mrungeso, panko was not really used for years12:15
rsartohmmm... i did not know that.12:15
mrungebefore events were both inserted into panko and into gnocchi12:15
mrungethe issue with panko is, it does not scale12:16
mrungeif it worked for you: great!12:16
mrungehowever, you may run into load issues sooner or later12:16
rsartoso, let me ask you another question. We're currently using openstack Ussuri, in that case, can I just stop using panko?12:17
mrungeyes, in almost all cases: yes12:18
rsartounderstand that, in our case we just want to use default openstack telemetry metrics. Is that the case?12:19
mrungeyes12:19
mrungejust metrics: you don't need panko12:19
mrungejust remove the panko line from event_pipeline.yaml12:19
rsartoanother question if allow me... what is the evolution strategy for openstack telemetry?12:20
mrungewhat do you mean by that?12:21
rsartoare we going to keep the other components (ceilometer, gnocchi and aodh) as part of it?12:22
mrungeI'd keep ceilometer and aodh12:22
mrungewe have seen issues with gnocchi in the past, but are also struggling getting a replacement12:23
mrungegnocchi has many nice things you would want to have, and alternatives don't have12:23
mrungelike high availability and multi-tenancy12:23
rsartoI understand that.12:23
rsartowhat is a current list of data generated by core openstack services (nova, neutron, keystone, glance, cinder, heat, etc.) to ceilometer ?12:24
rsartoI've only found a from ocata in  https://docs.openstack.org/ocata/admin-guide/telemetry-data-collection.html12:25
mrungethat are event types12:26
mrungethe issue with events is: they are defined in the components, such as nova, neutron etc.12:26
mrungeyou have to go through the code there. unfortunately, they do not use the same methods to publish events.12:26
mrungeare you interested in how that looks like?12:27
mrungeotherwise I do not look for code locations and move on with my life12:27
rsartobesides the code, Is there any reference/documentation about the events defined in the components?12:28
mrungeno, there is not. Or at least I am not aware of12:28
mrungee.g here: 12:29
mrungehttps://review.opendev.org/c/openstack/cinder/+/796806/2/cinder/transfer/api.py12:29
mrungethis adds notifications in cinder when a volume snapshot gets transferred12:29
rsartodo you know if there is a way to customize in the components which event is generated?12:30
mrungethat is also incorporated in metrics (you want the owner getting updated in gnocchi)12:30
mrungeif you look at the review I linked, you see the event itself is hard-coded12:30
mrungeit doesn't make much sense to send out a different event instead of the one I linked, no?12:31
rsartook, I got it, they're always sent by the components.12:31
mrungeif you look at https://review.opendev.org/c/openstack/ceilometer/+/79894012:32
mrungeyou'll see how events are configured on the ceilometer side12:32
mrunge*that* is configurable12:33
mrungee.g you can configure what payload is sent, on which events it is sent etc.12:33
mrungeor when the data is updated12:34
rsartoso, Does ceilometer use this configuration to accept/reject the events?12:34
mrungeif you remove them from the config, they'll get ignored12:35
mrungethat does not events from being emitted12:35
rsartocool. Can you advise me any documentation/tutorial about the telemetry? I would like to get more knowledge about this stuff.12:36
mrungewhat do you want to learn?12:36
mrungeotherwise, there are a few talks on youtube from previous OpenStack summits12:36
rsartoas user perspective, I would like to understand the concepts and how to check the measurements for the metrics.12:37
mrungeand if you are struggling with telemetry, I have recently written some notes on how to debug it12:37
mrungehttp://matthias-runge.de/2021/12/06/debugging-openstack-metrics/12:37
mrunge^^ that one would be a first step12:37
rsartosuper cool mrunge!12:38
rsartodo you know any reference on how to use the openstack metric cli?12:39
rsartofor really beginners...12:39
mrungeuhm, not really. that's why I had that in the document12:40
mrunge... how to get metrics collected from a vm 12:40
mrungealso gnocchi has some concepts not really covered in their upstream docs12:40
mrunge... what is a archive policy, how does it play together with retrieving metrics, etc.12:41
rsartowe're currently using openstack-helm to run openstack in containers...12:42
mrungeand I'm pretty sure you've seen the component docs: https://docs.openstack.org/aodh/xena/admin/12:42
mrungeI can not comment on that, that's another installer project12:43
rsartoI'm supposing here that the ceilometer configuration could be addressed as helm overrides. Do you know something about this?12:43
mrungeI've never used openstack-helm12:43
rsartono problem, thank you!12:44
mrungeout of curiosity, if you are using somethign like a container platform: what is missing there for you?12:44
rsartoIt was really nice to talk to you, thank you for your time and support.12:44
mrunge... what does OpenStack give you, what you don't already have?12:45
rsartoI think we're in a step before... We're trying to understand what openstack offers us.12:46
mrungealso: we (with a different hat) are working on something named service telemetry framework, which then sends out metrics and events from OpenStack to prometheus12:46
mrungeah, okay. got you12:46
rsartoyes, can I have more information about the telemetry framework?12:47
mrungehttps://infrawatch.github.io/documentation12:47
rsartoIs it going to replace all the legacy components (ceilometer, aodh, gnocchi)?12:48
mrungeit depends12:50
mrungeat the moment: no12:50
mrungeceilometer is used in both12:50
mrunge(OpenStack Telemetry and Service Telemetry Framework)12:51
rsartoDoes the service telemetry framework have a stable release?12:52
mrungeyes12:52
rsartowhat openstack version is it compatible with?12:53
mrungeWe use it with Queens and later12:53
mrungenewer features are compatible with train12:54
mrungeif you look at the documentation, the necessary steps are documented for the case you are using tripleo12:55
rsartoi'm understanding that the Service Telemetry Framework is another option for telemetry, it won't replace the Openstack Telemetry at least for now. Am I right?12:55
rsartoi'm understanding that the Service Telemetry Framework is another option for telemetry, it won't replace the Openstack Telemetry at least for now. Am I right?12:56
*** outbrito_ is now known as outbrito13:02
mrungecorrect14:11
rsartomrunge do you know if is there any panel to show telemetry metrics in horizon dashboard?18:15
mrungersarto: none. iirc.19:02
mrungeThere was a panel inside the admin panel, but I believe we disabled it quite a while ago19:02
*** tobias-urdin3 is now known as tobias-urdin20:10

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!