Grafana Community, 18 Mar 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Grafana Community Call 2021-03-18

Description

Agenda for the Grafana Community Calls:
https://docs.google.com/document/d/1GpgvanMeNqf-CDegv6E0yAV1s2f7H2knUFuNouqwX3A/edit

A

All right welcome to the grafana community call for march 18th 2021. uh We are going to be talking about documentation, updates and more. I am diana payton, the grafana technical documentation lead. uh We also have gita, ursula and matthew, who will be introducing themselves as we get to their parts of this talk, so the usual disclaimer. This call will be recorded, in fact it's being recorded right now.

A

So if you do not want to be seen or heard, then you should turn off your camera and ask any questions that you might have in the chat and this alrighty.

A

So here is our agenda. We're going to talk about the documentation updates we made for grafana 7.5, some other recent updates. You might have missed ursula's, going to talk a bit about the grafana technical documentation, style, guide, uh codification that she's been working on you're, going to get an exciting preview about the explorers, exporters, sorry and then the usual hr join, join us uh we're cool and then we'll open for q. A all right. So gita, please introduce yourself and talk about the grafana 7.5 oss stock changes.

B

We don't see your screen.

A

Really, oh, my god, I mean I've been like doing this with. Okay, I'm sorry. I thought I was sharing my screen. Oh well, this is live stuff, so it makes it charming right. Okay, so here's what I thought I was showing you there. We go.

A

Here's the agenda, all right, gina! Please, please introduce yourself and uh tell us about uh what you've been up to with grafana 7.5 oss docs.

C

Thanks diana uh hi, everyone, I'm tita chatterjee, I live in boston massachusetts and I'm the lead uh graffana oss writer.

C

uh Today, I'm going to be talking to you about the latest uh grafana release, which is 7.5 some exciting news, uh beta 2 is scheduled for release tomorrow we already have beta 1 live, so if you're interested in checking out the new functionalities, um you can download the software and you know play with it.

C

You can also visit play.grafana.com, which has the latest version of grafana running, and you can check out the awesome new features in grafana 7.5, so uh moving on next slide, please I'm going to be um um thanks dana, so I'm going to be talking about a few of the new features in 7.5, um so I begin with alerting for loki. um What is this um alert all about so well? In grafana oss, we have had alerting for various data sources like prometheus and fluxdb etc available from the graph panel.

C

This was not available for the loki data source and in 7.5. We have added this new capability next slide. Please.

C

The next feature I'm going to be talking about is a loki label browser, and you know um in previous versions, we had a loki cascader button option available in the explorer view that has been replaced by this label browser and what it does is it allows you to quickly search for labels, for example, if you know the value but you're not sure you know what label to use this browser will allow you to quickly.

C

You know, search for it and find a match, and using this you can either show logs or show log rate, which creates the rate. Query thanks light and the last one that I'm going to be talking about is the pie chart panel.

C

um Some of you are familiar with the pie, chart plug-in that we have had in previous versions. You can think of this as the next generation of the pie chart panel.

C

But, unlike a plug-in, this is actually one of our core panels and what it does is it displays um reduced series or values in a series from one or more queries as they relate to each other and of course, you know display them in the form of slices of a pie.

C

We have comprehensive documentation written for this available. um You know um you can click on the link to view the documentation, and um you know I will just end by saying. If you have any questions about um uh you know all the other features that are available in 7.5 um do look at what's new in grafana 7.5.

C

It has all the new features, uh deprecation announcements and uh you know a links to appropriate documentation.

C

uh Lastly, if you have any uh questions on any of the new features- or you know just graffana docs or uh you know, graffana products in general uh feel free to you know, ask uh ivana, who is one of the uh engineers in this call, so she, uh you know, writes code in addition to um writing documentation, and we will be happy to answer any questions.

C

A

All right thanks, gita, all right, so I'm back to chat a little bit and so we've. So we update documentation when new features come up like for new releases, but we also update documentation just because we see areas that could be improved, which I have been doing for the manage user section preferences docs and permissions docs. So I'm going to since I'm not as good at making slides as jeeta is I'm going to just give you a quick tour all right. So look at that.

A

The manage users section is manchester's in grafana is a little bit complicated because you can do it. You can manage these as a server admin, an org admin. You can manage teams as a team admin or an organization admin, and then users can manage themselves a little bit.

A

So I broke down all of the tasks that each that apply to each of these levels and uh also added some kind of basic instructions for changing password explained all about your user account profile how to switch organizations, and hopefully this will make life a little bit easier for admins who are trying to manage users, organizations and teams.

A

So preferences in the administration, section, preference- is also a little bit complicated because you can do the same thing at four different levels at so I explained both about the four levels: server organization, team and user and about precedence uh short version is the lowest level, takes precedence over everything else, and so each of these sections, such as changing the ui theme, has instructions for how to do this at the various.

A

How to set the theme at various levels and permissions. I didn't make a whole lot of changes here. I clarified some content in the permissions. I broke out the section about restricting access that was part of dashboard and folder permissions and gave it its own section, because it really was separate from that and basically clarified a lot of content and added this handy dandy table so that people can quickly look to see what the different organization roles can do.

A

All right and now ursula. Please introduce yourself and tell us about what you've been doing, codifying the style guide, yeah a quick thing. I do see questions and we will answer them at the end.

D

Thanks diana hi, I'm ursula, and I am the lead writer on the grafana enterprise documentation and today I wanted to share some work that I've been doing. I've been pairing with an engineer on codifying the style guide and we're using veil for that, and basically this allows us to collaborate asynchronously more effectively. So what we writers would typically tell someone is something that we can. We can automate diana if you can share the next screen.

D

That would be great uh we're limiting on each pull request and that's a continuous integration pipeline that we're testing at the moment, and I wanted to highlight some of the invisible um work that goes on because we're working across about five different time zones, um at least in some of the stuff that I'm doing diana's utc minus seven matthew. Thank you, u2c minus five, cheetahs utc minus four, I'm plus one and the engineer that I'm pairing with is on utc.

D

So um I just think that's an important aspect of working together to get features developed across teams and in this case the engineers I said thanks to jack baldry on the bottom. Here you see him in the footer. If you have any questions after this, you can also ask him with veil. You can choose your style. There is a an option for google, for example, or microsoft, and there are just many many examples of suggestions that you don't have to write from scratch. This is an open source tool or um this functionality is open.

D

Source fails open source, and you can obviously add your own terms and suggestions, and I have been, I will be changing some of the suggestions from maybe a more negative tone to a positive tone, and so that's very very easy to do so. People when they're making prs they typically want to know what they want to do, rather than what they've done wrong and they're often short of time.

D

So if we can just get them the information as quickly as possible, that's that's super helpful and, of course, if you have a lender, you negotiate once or as as needed. Instead of negotiating on a per pr basis, depending on which developer engineer you might be have you might happen to be working with at a given time, we're planning on rolling this out gradually so that we can minimize any friction or eliminate it.

D

So what I mean by that is that if we have a bunch of changes from a style perspective, we don't want to have 70 messages going to an engineer because we're introducing something that's saying: let's get these phrases and sentences more uniform across our documentation set. So I'll probably do some of the heavy lifting in terms of the details that need to be changed. Maybe it's a mite made to a mite, for example, it could be changing over a c to a referred to, or things like that, um and then I thought well.

D

Maybe the next level would be potentially to generate a style guide from the linter source code. So if we have all of the rules that we want already in source, maybe we can just create a deliverable that contains that information. That's dvd, but uh it's something that came to mind and yeah. Just a shout out to jack baldry who's, the engineer that I'm pairing with on this and um there's another thing in in the pipeline, which I can reveal in another call.

D

But that's what I have for you today and if there's any questions, feel free to ask any one of us in the chat as well.

A

So ursula, how? How will this change my experience of uh putting in a pr with documentation? If I do something, that's a style guy disagrees with well.

D

You will have a suggestion that will either be a blocker, so maybe something we feel pretty strongly about uh could be a misspelled product name or uh something we want to be. You want to have spelled out. It could be a suggestion that doesn't block anything, so you'll see a um text when you look at the the pull request and it's might be tbds to who can see this at what level again. This is under development at the time at this time.

D

The result of this ultimately will be more consistencies, more consistency across the entire documentation set.

A

Yeah our goal here is, as I understand it, to try and help people both internally and in the community, to write better documentation with with as little effort as possible, so so yeah. I think this is really cool all right before I do the uh exporter preview, I just realized. I forgot to share something kind of important about this, so you see these uh edit. This page and request stock changes links in that we have in the grafana documentation soon.

A

These two links will be coming to all of the oss documentation- hopefully this week, but possibly next week, so that you will be able to more directly help improve documentation for loki and tempo and all of our other oss products, and there will be a feedback email link on the non-oss products.

A

If you want to tell us that there are typos or that we're missing something in there anyway, so matthew helmke, uh please introduce yourself and uh then and.

B

A

Project I'm a senior.

B

Technical content developer for self-service, for you know grafana cloud. So um what I do is I write a lot of different sorts of things today, I'm going to talk about a little microsite, we're building about exporters, but I also handle all the cloud documentation and some other stuff have you ever sat in front of grafana, whether it's grafana cloud or whether it's you know you hosting it and thought I have this data.

B

I have it going into prometheus. How do I export it from you know this app into prometheus so that I can have it either scraped or sent to grafana? Well, uh we lost the.

B

uh We lost the sharing um when you, uh when you share your screen again, you can go to the next image, so what we've done is we are creating a subsection of the grafana website that is collecting information about the various uh prometheus exporters that we know about that are popular, so we're looking at um usefulness, popularity and we're also trying to parallel all of the exporters that have been used to build integrations into grafana cloud so that you can see you can do it on oss.

B

Installing this way- and you can do it in grafana cloud this way, what we're doing is collecting all of the rules, all of the various metrics, that an exporter sends and we're showing you what they are in advance and then we are going around and uh finding dashboards that work well with each of the exporters, because exporters are shipped and created without a specific dashboard most of the time, so we're curating a set of dashboards that work well with the various exporters.

B

The first page is live, and if you go to the next slide, you'll discover that first, several pages are live. There's a lot more content coming by the end of the quarter, we're going to also create an index page for all the exporters, we're creating- and I think it's pretty cool, we're kind of in preview stealth mode right now. So everyone on this call gets to know first, because this has not been announced. This has not been shown to anyone except internally so far.

B

So what I'm going to do is in the meeting notes, I'm going to put links to the ones that exist right now, and I'm also going to put a note about how to give me feedback. Now, I'm not the one who's created. Most of this david dorman has kind of pushed the uh the project along.

B

We have a contractor hanif who is fantastic and he's doing a lot of the writing, um but we are trying to help both oss users and grafana cloud users to do things a little more easily, instead of having to search back and forth prometheus docs cloud docs, let's put a bunch of the stuff in one place, and especially you don't have to dig through code to find out what metrics are being sent and which, which dashboard is going to be the most useful. So there we are that's what we're doing.

B

I think it will be helpful both for everyone doing. Excuse me using exporters with the oss product, as well as with the grafana cloud hosted product. Send me questions. I will have details in the community call doc that I know is public um momentarily and that's all. I have to share today.

A

Thanks matthew, that is very cool.

B

Pretty pumped about it, it's uh I think it's going to be awesome.

A

All right and uh the slide to make the hr focus griffon is growing. We are hiring check out our grafana careers page uh for to see what positions we have open and shameless plug for our technical writing team. We are looking for a senior technical writer to work on loki oss, um but yeah. You can find the link to that at the grafana careers page dm me, gita or ursula. If you have more questions about that and speaking of questions, I saw one in the chat.

A

Is there any plan or road map to have a span panel instead of using explore for the tracing panel? um I have not heard of any of that. I've heard mostly about the node graph panel, which I guess is sort of a tracing thing, a bar chart panel and a which is currently an alpha and the xy scatter plot panel ivana. Do you have any information about that.

E

So there is actually a github issue for this and it's pretty popular. We have added it a priority of long-term importance. So we know it's important, it's something that our users want. We plan to work on it, but we don't have it scheduled yet so there is definitely a plan for it.

A

Well, anybody else have have questions comments.

F

I have a question regarding the radius caching, which is coming in 7.5. Can you share more information about it, because I saw your prs updates in grafana, but it's I mean it's very limited. This is radius. This is how you connect with that's. It.

A

uh Ivana, can you talk a bit more about the the reddish stuff? I know it exists and that's about all. I know.

E

I I think I I'm not the right person to to talk about this, because I'm not working with this uh plugin.

A

Yeah- and I thought there was some stuff in the backend enterprise uh ursula- is this ringing a bell for you.

D

It's ringing a a small bell for me um and I would have to do research to get back to this question.

A

Okay, so um fedjar in the chat said since loki is suitable for multi-tenant. So with the specific tracing span panel, it's possible to limit the view of the loki trace id to the specific span. I don't understand the question or the comment.

E

I think that the best place to ask this would be our community slag and we have their channel locky and there are actually lucky developers, so they would be definitely the best people to to answer this.

A

Actually, a better place to ask that would be community.grafana.com because we have a loki section there and, unlike the slack, those answers will persist and are searchable on google. So not only do the will people hopefully answer your question because loki developers are pretty active there as well, but then it will be there for future people who might have the same question or similar question yeah. That's true, okay, anybody else, any more questions.

A

We love questions.

F

Another question regarding the dashboards lifecycle: there are multiple panels which come and will be in seven five and eight, which is uh time series right. New pie chart panels. So when you create the dashboard and you're using graph panel in it, for example, right and you provide this dashboard, you put it on graphon.com and the dashboard repository.

F

Is it any way? I can uh provide grafana as a part of graph as a part of his dashboard for version lesson 7.5, when it's not available and have it as a time series per version. Seven, five four eight same with the pie chart or it has to be removed manually.

A

Not that I am aware of um ivana any ideas yeah, because usually it you have to have the panel in the in the version that it is introduced in or later so, because earlier one earlier versions of grafana wouldn't have any idea what to do with the new panels.

F

Right, my question is about as a plugin developer. How do you end especially the application plugin? I have some menus, which is pointed to the dashboard right, and I want to use the time series, for example, for seven five or eight and with a new version. How should I have like a couple of menus so version lesson? Seven, four and seven four uh other way, because I really like the new time series panel for the streaming it's great, because graph panel is kind of slow right.

F

The time series works great stills, how I can support users on the older version and the new newest version as well.

E

So I I know that for sure marcus olson would know about this, because uh on our internal meeting he was talking about um actually a problem that some uh people hide their version. So uh it's not shared with the plugin developers and he was discussing like what would be the best option how to fix this. So I don't have uh the answer for you, but I will definitely reach out to to marcus because he is the best person to ask.

A

Yeah, marcus olsen is also very active in the plug-in slack channel, uh so he might be able to to help you there and he he's usually in these community calls, but he had a conflict today. I think he also has office hours, which you could see on the grafana community calendar, which is public, and I believe it is also linked on the agenda document that you used to get here.

F

Okay, yeah might be off. Our is a good way.

A

Thank you, you're welcome, so uh any more questions. As I said, we love questions.

A

I have one more sure bring it on this. This call is for you guys, so we will hang out for as long as there are questions or until it hits the next hour. Whichever comes first.

F

Right uh it's regarding alerting, so I asked you in doc's slack channel that this alerting have to be updated for the community plugins right, I'm not sure if it's done or not, but my question is more about when you do alerting you kind of alert on all the fields returned by the data source right and it's happening on back end has understand not to the front end, so you cannot use transformations to choose specific field. I want to have alert on. Is there going to be an improvement for that?

F

I thought there is a lot new generation is working on right now.

E

Yeah, so there there is going to be improvement. uh It's going to be with graphene 8. We are. We are working on improving, alerting, uh but there what you said is correct. Like it's done on the back end, you cannot apply any transformation. So it's it's uh just like. What's the response from your query, I'm not sure if it's going to be like this specific possible um in like alerting the the newer version, um but I know that um it's it. It should be uh definitely like more flexible and yeah.

E

Maybe some I'm not sure, like uh from doc's team, if anyone is already working on the documentation there, if you have more info.

A

Patrick asks when is 7.5 due so currently the beta 2 is scheduled to be released tomorrow and we are tentatively uh planning march 23rd for the stable release that is subject to change, because we've had a few high priority, bugs that required immediate patch fixes.

A

um So, like I say it's scheduled march 23rd right now, um but that is subject to change, but soon so most likely sometime next week, so fingers crossed hope. I didn't just jinx us knock on wood like product all right. Anybody else, any more questions.

D

I have a question if we have a question for the people on the call. Actually, if we.

F

Oh, that is great.

D

User feedback, um anything from how you read the documentation, do you tend to jump in and code something figure something out and then read the documentation? Do you read stuff? First, what's your preference?

D

Do you use any tools to read the documentation? I know uh you said your. Your english is not your native language. Do you do you use any um google translate or anything that or any other tools that help out in this regard, or does anyone else have any feedback about this reading docs in general,.

F

I have a feedback, I mean it's not only for grafana labs, it's in general, the program I mean when I started working with grafana, I think, half a year ago there was a lack of documentation in many parts, and documentation was improved so drastically in the last half a year right, it's a really good job and every time when I'm looking for something right now I see so much more information.

F

I exist, which was not exist before there was only. There is only one problem. How I can understand that something changed in the documentation and not following prs in grafana.

A

Yeah we're trying to get better about uh uh letting people know about that. um I will, if it's a non-release documentation, update I'll, usually post an announcement in the public docs channel um and we've been trying to be more extensive and detailed with the what's new document. You might have noticed the last few. What's new in grafana version, 7., whatever have been a lot longer than previous.

A

What's new we've been making a point of trying to add the to both be more detailed so that people know what changed and to link from those new features to updated documentation so most of the features, in fact, almost all of the features have links to the documentation updates that they pertain to. There are just a few back-end items that didn't actually require documentation changes, but we included them in the what's new so that people were aware they were happening.

D

In addition to that, um there's conversation that there's com there are conversations that I'm having on the enterprise side about how to make things more consistent across products, and so uh even simple things like making things structured so that it's more easy to simply read a change log um and then comparing uh from a content strategy perspective.

D

If we have what's new over here and a change log over here and another change log over here, we're putting this together in a common picture, so to speak so that you know okay. This is this is the scope of what I can expect to be able to read and um the changes are going to come in a streamlined experience.

D

So when you're experiencing this at the as an end user, as a user of grafana, you can know okay. Well, I'm getting what I what I can expect to get in terms of the information about changes, um so to say that less verbosely we're looking at this from multiple angles uh across different parts of the products.

A

D

A

Yeah rss feed or something.

D

Diana one one thing that's interesting, um so you mentioned mikhail that the in the last six months there's been some positive improvements and there's a reason for that diana. Might you want to say something about that.

A

Well uh about a year ago, or a year and a half ago now geez, I started and I started improving the documentation and making some major changes and about what four or five months ago jeeta joined up, and so at this point we have three technical writers on our team and are hiring a fourth and so yeah we've. Basically, uh graffana labs has been putting people and money towards improving the documentation and I'm really pleased with the progress we've made.

A

What you guys can do to help is, let us know if things are, if where we can improve the documentation, we love feedback. We don't get enough, let us know what is working for you, what is not working for you, what needs to be expanded or what is wrong if there are any mistakes in the documentation, because we don't know what we don't know and well.

A

We are very experienced software writers, we're not experts at most of the data sources, because there are a lot of data sources and there's a lot to know with all of them. So you know by all means, and if they're we also love it. When people provide documentation that we can add add into the documentation set, so you know we, we love community involvement and we are happy to try and make it easier for you.

A

There was a question about localization in the chat. um We have um I'll probably uh send this to ursula because she's our our expert on localization, but we've been kind of debating about how best to do that. Because the thing about localization is, it adds a lot to the workload on on our side and it's also very complicated, because there's.

D

Both the documentation.

A

Yeah sorry go for ursula.

D

It's okay. I can say a little bit about that. So it's! It is not on the plan right now, the schedule or the plan um definitively so that, if people are, you know, have expectations about something like that coming out. We just need to be very clear about that. What that does involve is very it's. It's, it's a it's a very large project um and we do get uh offers for help about translating into various languages, and I know matthew has some experience involving community members in translation in his previous role.

D

uh If I understand correctly, um we do need a lot of um planning for that, because- and I and I basically did a brain dump uh internally and have about four pages of things, to consider in terms of questions from uh knowing, for example, which region of the world we would go into and and whatnot and and then what that would mean and there's also, you know things from a legal side.

D

It's not always the case where you can simply sell a product with uh in another line in another country, without translation, um so every region is different. There are different requirements for different regions, and the the enormity of the project is something that we need. We we need to chew on. You know bit by bit to be able to make this more manageable and for starters, the very first thing that's required.

D

I think, for such a project is to clean up the source language which in this case is american english, and so we have a lot of work to do and um yep that's true angita also. So thank you for mentioning that, because we do internally have quite a lot of experience. um We even have a person on the ux team has been a professional trans technical translator, um so we do have people to lean on when the timing is right and that is still going to be tbd for this foreseeable future.

D

A

Jar since we've got you here when you talk about translation, are you talking about translation of the grafana, ui or translation of portions of the documentation.

A

Okay, so that yeah, translating the documentation is a lot more complicated than translating the ui. So I'm boy yeah, because it wouldn't be just translating the documentation we have today. It's also translating all the documentation we have in the future checking to make sure the translation is correct and yeah that that is a that's a heavy lift right. Now we're kind of starting with a look. What we're looking at is.

A

Could we enable the potentially enabled the community to translate some portions of the grafana ui and if we were going to translate some of the documentation? Which parts would we translate, because all of it would be a little bit uh complicated? But there might be some parts like the getting started and installation dude.

F

Like I say, we're still.

A

We're still discussing this and it's it's something we're paying attention to but yeah. You look like you want to say something.

C

Yeah I actually, um this is not related to translation, so I can go after. We have finished this. uh You know uh talking about this topic, but um so I'm just gonna pause like I.

D

Think I've kind of gotten to the end there.

C

D

The only thing is that it's definitively not scheduled and not on any road map, but we are very much. uh We have the resources internally to understand, just how big this project would be.

A

Yeah we have the resources to understand that right now we don't have the resources to do it.

B

I think the big thing is finding customers that have.

A

B

Specific language needs and uh are also large enough customers for us to have the economic capability of um committing humans and other resources to translation. It's uh it's not a no-cost thing. So um that's that's a huge foundational issue. Is we just got to figure out the money and the you know, return.

C

The business need definitely so. uh My question is for mikhail, and this is, um uh you know, um incredibly excited uh to hear that uh you know you follow grafana documentation and you can see that you know efforts are being made to improve documentation and add uh information.

C

So my question is you know you mentioned that every time you go, you find more information. um Do you find it overwhelming, or do you do I mean?

C

Is there a mechanism or something you know we we can come up with like that, can help you quickly identify what is new or maybe you know, get some kind of a message or some kind of a marker that you know within this topic. These are the new sections.

C

um How how can we help you like quickly see what was older information as opposed to what is new.

F

That's a good question, I mean I'm very visual person, I mean. Having always uh what's new in the documentation section by prs is great with new release. For me, I would, I would say, will work like quick video. This is what was changed recently recently like 30 seconds one minute, video. We changed the plugins, we changed documentation for users. The same was what diana did just make with small video posted everywhere right, everybody will know. Oh, this is what changed here. This would change here, because uh there was one one particular issue with the streaming.

F

uh It was changed in 7-4 as the documentation changed. That is something we had to do. I didn't do that and then I had to go into augmentation and torquel had to tell me.

F

Oh, this is a part documentation now, but I had no idea that documentation was updated now it was not a part of that before so I mean, maybe I mean clicking on every single uh pr and what's new documentation is great to read it right, but it's not efficient for the users, especially when you have I mean grafana is one of the products you're using.

C

That's fair. Definitely, that's that's a good suggestion. Yeah! Thank you for.

F

C

A

F

And quick to go through and done and you can post it on twitter and linkedin.

A

That would require me.

D

To tweet, that's a really good suggestion and also we've focused we're we're currently focusing more on the content strategy perspective. So this is this is feedback we can directly take to this yeah. This time.

C

And uh yeah I mean with regards to tweeting sam or someone else can probably help, but I think from what I understand you a quick short 30 seconds or one minute, video and that gets posted everywhere. So uh you know people are aware of like like what topics were attached upon and what new information was added. So it's great.

F

Twitter, this is the way how you learn about the news and what's happening right, so I mean everybody when you have retweet likes right, you eventually, if you're interested and you follow grafana, you will see that and this is them an easy way to get update.

A

Get off my lawn young whippersnapper yeah make me feel old.

A

Any other questions.

A

All right going once going twice all right. Well, thank you. Everyone for coming to this community call thank you for to everyone who participated for the great questions uh for everyone watching on youtube. uh The slides will be posted uh when the documentation or when the video is posted, so check that out and please feel free to leave any comments on the youtube, video or questions we will check those periodically and for everyone else.

A

If you want to give us uh by us, I mean the writers me jita and ursula your opinions on the documentation reach out to us on public slack, and we might be able to uh arrange a quick meeting so that, because we would love to hear what you have to what you think of the documentation, uh what's working for you, what's not working for you and uh how we can make things better.

A

So how can we help you, but let's work together and make the documentation even more awesome, so gina matthew, ursula anything to say in closing or ivana by the way I've done it how's your avocado plant, doing.

E

It's doing good yay it's! I I'm not sure if anyone knows but you prune avocado, so you cut the like most of their leaves and it looks very drastic, but then they become larger. So it looks very poor and like it's smaller, but it's doing better.

F

Do you use alerting.

E

F

E

Not using alerting because I have like a visual uh display showing me how the avocado is doing and I'm not I'm just at home all day, but I was planning to also like when I go away to do our thing. So I know if my boyfriend takes a good care of the avocado.

F

Yeah, that's great get a slug notification or pages duty alert, yeah.

G

F

I have one more suggestion by the way, if you can help marcus with application plug-in documentation, because he wanted to do it for months and it's one of the recent questions for from the community on slack, you can help him.

E

By the way, I have one thing related to this: I know that in explore. We are also improving documentation for plugins developers on like what you should implement if you want uh to use explorer different features in explore. So I know andre is working on this, uh so just um this question reminded me of uh of this okay. Thank you.

C

Yeah- and uh you know thank you, mikhail great suggestion uh about the plugin documentation. I'm sure you know we will be in touch with marcus olsen. I know diana is in regular touch with marcus and we will follow up.

A

Oh, let's be real he's going to watch this video he's probably going to edit the beginning parts of us flailing with the kermit arms and me talking about how my arms are disappearing into space uh out of it. So so no worries about that.

A

All right thanks: this has been good, yep, absolutely awesome.

B

Thanks everybody.

A

Have an awesome day, everyone bye thank.

G

F

F