Grafana Agent Community, 19 Apr 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Grafana Agent Community Call 2023-04-19

Description

April Grafana Agent Community call with discussion on flow and clustering. https://docs.google.com/document/d/1TqaZD1JPfNadZ4V81OCBPCG_TksDYGlNlGdMnTWUSpo/edit

A

Hello, everyone and welcome to the April grafana Asian Community call I'd like to welcome everybody here. We don't have a lot of topics, but we have a lot about the release to talk about. As always, if anyone has any questions or comments or really just any kind of feedback uh feel free to raise a hand type it in the chat.

A

Whatever you feel like you need to do to you know, get some attention, um I'll go ahead and kick us off with the uh the only real topic we have on the release or on the schedule and then we'll open it up to everybody. So we have our I.

A

Think 33 is that right, 33 release coming out next Tuesday on the 25th, we'll be cutting the um RC candidate tomorrow sometime, um it's a pretty big release, especially for float, so we have some of the concepts we talked about last week that are going out in this, such as modules which we've included to get. In addition to maybe what we talked about last month.

A

um Clustering should be shipping in that, or is it's checked in right, pascals yeah, so that'll be going out. uh We have a ton of explorers uh and Discovery components, that'll be going out, helping us bring that uh feature parody up so yeah. Does anybody have anything they want to talk about relief or new items that we're introducing.

A

All right cool I mean I, can give a little flavor here uh kind of. If you go through these Community calls you'll, probably see a progression of the float framework and kind of how we've been pushing it, but definitely it's it's something we are Marching towards.

A

um You know. A lot of the new development is in the flow, because it's a lot easier and we think it's the future of the agent um and we're making great strides and trying to create that feature parody. In addition to having additional features, you feel free to use the flow, we'll support it fully.

A

um It's you know uh has a whole. It's um you know uh stable um available for General use. There might be specific um some sections or new features that may not quite be uh fully ready.

A

um You know uh but feel free to try them out. You know something like module. There's a clustering is probably going to evolve a little bit over time, um but we're more than happy to help you out use them, because we want feedback from it so feel free to give us any feedback in the channel and issues uh pretty much any kind of way to get to us.

A

Hey I'm Jake Andrew Andre, apologies, um yeah, the so you're speaking with the uh overflowing. The limit that the the um a single a conviction be held in sounds like um yeah I think we have some ways around that 'll be coming out, maybe not particularly in the operator.

B

Yeah that um there was an issue, if you have like too many pod monitors in your cluster and you're using the operator, um the the config is too big for a single secret.

B

um There is a change in 33 where we just gzip if it gets above a certain size and that solves that problem at least kicks it down the road a little ways so that'll be there in 33., yeah yeah. Hopefully,.

A

It compresses really well so at least uh buys us a lot of time. um It's awesome, yeah and that'll be going out like I said on Tuesday.

A

um The release candidate will be going out um Thursday sometime, um so if you want to use that a little early um feel free to use the release candidate, um it's pretty rare that we have a lot of changes between the release candidate and the main release that are like issues we found. Folks should be relatively psychological, especially from the operator um so yeah all right. Does anyone have any topics they would like to bring up or could have questions? Or you know kind of anything uh we want to cover here.

B

A

Yeah go ahead and pascalf.

C

uh Could we quickly go through the module loaded implementations that we have right now, I think last time, America showed us a tour of how module work. uh We didn't have much going on there other than loading it from a restaurant and I think it was while uh explaining what we have now and what we plan for the future.

A

Sure, um more than happy to dig into some of that, um so we are going to be releasing with three ways to load modules. There is the module string, which is the most basic where you have to essentially load the string from an external Source via S3, the remote dot, F3 or local.file, and then load it, um which is not the most ideal way. But it is kind of foundationally the the base of other modules.

A

So it was the first one released and then Eric released the file module loader and essentially this wraps the local dot file component and basically smushes them into one uh and allows you to have less folder plate.

A

um I. Actually.

D

Have any flavor.

A

You want to add to that or anything I got wrong.

D

I think that makes sense um no in terms of the nothing nothing yet wrong and uh if you want I, can show a brief example of what each one looks like I think that would be yeah.

A

Let me let me finish up on get and then, if you've got something you can kind of show off more than happy to take a look at that and then the last one we just checked in yesterday is the um get loader, and this allows you to load modules from git, which we think is kind of probably.

D

A

Of unlocking the uh you know, really allow reuse of components and modules, um and we have plans at some point to kind of have our you know own blessed repository of common functionality, wrapped in that, so people can use that and kind of have a location for Best Practices, all right, Eric.

D

All right uh pop this back on.

D

Roll this up just for a sec, just I'm, not gonna, so I'm not gonna, go like way in depth here. um If you want kind of the full overview of this stuff I would you know, recommend you check out the last month's Community call where we kind of did a full presentation on it, yeah bigger text? Thank you is it.

A

Yeah there it is here, that's.

D

Good, thank you excellent, um so just to kind of show uh what what the three different types look like in practice. So here's the module uh string that was discussed um this module requires that you load in content from another source. So in this case it's a local file component defined here and I think Matt mentioned. There's. You can also use I think remote.s3 as an example in remote.http both return strings as well. That might be a reasonable use case for module.string.

D

So this is how you would use that, and this points to another River file, uh the file.river takes that concept and says well what? If we just do that right in the module uh component itself, instead of needing two components, so it's specifically designed to accept the a file path. So that's what we've got here and then get dot.

D

River will demonstrate the module.get which will point at a git Repository, a revision and a path to a module file and you this is just showing how you pass arguments to a module in general, so that that applies to all module loaders. But this will go out and grab this module uh from git and load. It that way so both uh file that River and get that River I believe we'll pull for changes and in the example I gave.

D

This will pull for changes because it's using a local file component, so the polling for module.string will depend on what the component that you're using to load the com, the content does. So that's what will drive that so I guess with module string, you can't necessarily guarantee there will be polling unless the the component uses. Does it so, but I think most do so.

D

That's uh I'll leave it at that. Let's say questions or anybody wants to expand on it.

C

So so the arguments are then available in the um when you evaluate the content of the module, the the content of the module will reference the arguments right.

D

Yes, so if I look at this, uh this is the Prometheus scrape module that I've got here. You define what are the arguments, whether they're, optional or required. You I you don't actually have to put the optional I think the default is false, but but uh you can also provide a default value and then I can refer to those with argument: dot, label, dot value, we'll grab the argument.

D

And since we've gone to this level, I should mention kind of the reverse case, where you have something in a module that you want the parent to be able to use and that's what we refer to as an export from a module.

D

So in this case we are defining this hotel processor- uh oh sorry, down here, I'm, so zoomed in I'm, used to seeing you know more of it, but for the uh for the YouTube, so, okay, so uh so in this case, we want to export the input export from this component. So we're able to do that and then up at the uh the parent level.

D

um This is in the tracing area. We can refer to that export um like so so. We've got this module, dot, file, dot, traces, Hotel input and we want the exports there and the specifically the input export. So that's that's how you do that in the other direction.

A

Great um any other questions.

D

Yeah I heard somebody say something that.

A

Was me if I had any other questions on modules or any of the other things in the release.

A

Or if anyone has any questions in general.

A

All right, oh pretty quiet, so I'll, give one last call for questions. Comments need some help with something uh kind of Open Mic. Here.

A

All right with that I'll appreciate everybody's time and uh we'll see you in right around among see everybody. Thank you.