And, you know, this comes from E.T.3 Handegard and there were some other folks that also had similar questions. Mr. Mark Jetty was one of them. And the question came in and it talked about in the light of recent events that are going on in Seventh Fleet and other parts of the fleet operating around the globe, you know, are there currently any efforts in action to combat the casualties we have been suffering? If so, is there anything that we at the more junior levels can do to help in these efforts?  You first look at these things and you go own it and you go, what can we do?  We have to learn every day. We continue to educate ourselves. We continue to hone our skills. We focus on those watch station qualifications. We mature our skill sets. We develop every day. And the other piece of this that I think that everybody can do is we're all leaders out there in every part of our organization. And we need people to continuously be those leaders and identify those things that we can continue to improve upon and then challenge leadership with those things and then kind of hold each other accountable to that stuff. So great question that came in. There's a lot of things that we can do. Keep focusing on maturing those skill sets out there, focusing on developing our competencies and our operations and warfighting effectiveness and be leaders across the entire organization. And I would just add on to that. First of all, this idea of ownership is a real powerful one, right? We just need to own our jobs, be experts in what we do, hold ourselves to those standards, challenge our leadership to understand it and get better as well. That's exactly the mindset behind this operational pause that we ordered. Hey, we're going to just stop for a second and we're going to make sure that we've got the fundamentals straight, right? We're going to try and remove any kind of distractions from our day on that particular day and make sure that we do have ownership of our jobs, particularly in sort of the fundamental blocking and tackling, the elements of safety and the basics so that we can, you've heard that term, brilliant in the basics. This is a day to concentrate on those basics and make sure that we're doing everything we can to be as brilliant in there as we can.


Thermodynamics, in its generalized sense, is about the theory and study of how energy transforms matter within all physical systems, from the formation of stars to photosynthesis to the running of your car. The laws of thermodynamics are central to understanding ecosystems by the nature of their physical state. With the solid understanding of thermodynamic principles, we can begin to create abstract and rigorous models to the complete energy and material flows through an ecosystem. Thermodynamics is a very exciting area of physics because although the theory of equilibrium thermodynamics is well understood, the thermodynamics of systems far from equilibrium remains very much an active area of research. Thermodynamics is the branch of physical science concerned with the interrelationship and interconversion of different forms of energy, in particular thermal energy. On a more generalized level, we might say it is the study of how energy transforms matter through processes, the structures or order that emerges out of those transformations and how we can describe these states of order and disorder in terms of information and the capacity to work. Put energy into a system and that system will respond. This is the nature of a thermodynamic driving force. It is a way to push and pull on a material to alter its state and structure with any type of energy. By applying some energy, the system responds, apply a pressure and see the volume change, increase the temperature and watch the material melt, decrease it and watch it solidify. One of the great benefits to having thermodynamics as the theoretical underpinnings to systems ecology is that it applies equally to physical, biological and engineered systems, giving us an integrated framework for the rigorous modeling of both ecosystems and industrial economies, often in a quantitative fashion if need be. Through thermodynamics, we can see that the same processes shape both the development of ecosystems and our technology infrastructure and is through this understanding of thermodynamics that we have engineered our physical environment. Through understanding this process, we first learned to cook. We learned to shape metals through smelting. To produce steel, by understanding the subtleties of these thermodynamic processes, we could create different types of steel by regulating how rapidly the molten metal is cooled into a solid. It is through this understanding that we learned to make engines that turn heat into mechanical work. We can make electricity from spinning turbines and to make plastics of all kind. We obviously don't have time for a full discussion of thermodynamics here, but we will firstly give an outline to equilibrium thermodynamics and its basic laws before going on to talk about non-equilibrium thermodynamics and in particular dissipative systems. Equilibrium thermodynamics as a subject in physics considers the macroscopic bodies of matter and energy in states of internal thermodynamic equilibrium. Thermodynamic equilibrium is characterized by an absence of the flow of matter or energy. More generally, equilibrium is a state where the system will not change unless given some perturbation from its environment. Isolated thermodynamic systems, if not initially in thermodynamic equilibrium, as time passes, tend to evolve naturally towards this equilibrium. In the absence of externally imposed forces, they become homogeneous in their local properties. This condition of equilibrium is really enshrined in the zero law of thermodynamics, which states that if two systems are each in thermodynamic equilibrium with a third, they are also in thermodynamic equilibrium with each other. The zero law is clearly a statement of equilibrium and it is this equilibrium through which we define the measurement of temperature as that which ceases to flow between systems in thermal contact. The first law in its generalized sense is a statement of the conservation of energy in matter. It posits that energy can never be created or destroyed, but it can be transformed from one form into another. This implies that the total energy of an isolated system remains constant over time. The first law tells us about the flow of energy within a physical system and that we can trace this transformation from one form to another through the system. The second law of thermodynamics is an expression of the universal principle of dissipation to kinetic and potential energy observed throughout nature. The second law is an observation of the fact that over time differences in temperature, pressure and chemical potential tend to even out in a physical system that is isolated from the outside world. The entropy of an isolated system that is not in equilibrium tends to increase over time, approaching a maximum value at equilibrium. Entropy is a measurement of the number of degrees of freedom a system has. Take the example of a perfect crystal, in which case the atoms are all locked into rigid positions in a lattice formation, so the number of ways they can move around is quite limited. In a liquid, the options increase considerably. In a gas, the atoms can take on many more configurations. This is why the entropy of the gas is higher than liquid which is in turn higher than a solid. When the entropy goes up, it requires more information to describe the state of the system and it would require more work to be done in order to reconfigure the system into its original ordered state. As such, entropy is a key measurement in information theory where it quantifies the uncertainty involved in predicting the value of a random variable. The second law states that whenever energy is converted from one form to another, some of the energy becomes low level heat. This means that the conversion of energy from one form to another is never 100% efficient. Some of the energy is lost as heat. The lost energy is still energy but it's no longer high level energy that can be used for work such as moving things or fueling metabolic processes in plants and animals. Thus the second law is one of the few, if not only, physical laws that differentiates between the directions of time. The third law tells us that as a system approaches absolute zero in Kelvin temperature, the entropy of the system approaches a maximum value and that it is impossible to reach the absolute zero of temperature by any finite number of processes. The second law defines an increase in permutations and randomness over time but biological systems are characterized by increases of order and complexity. As a result, it is often noted that biological systems must be functioning at a state far from equilibrium. This observation has led to the extension of standard thermodynamic theory through the development of what is called non-equilibrium thermodynamics. A recognition that standard thermodynamics only really applies to systems at, near or moving towards some equilibrium. It is therefore legitimate to ask to what extent equilibrium thermodynamics can be generalized to cover more general situations of non-homogeneous systems, far from equilibrium states and irreversible processes. Many efforts have been spent to meet such objectives and have resulted in the development of various approaches coined under the generic name of non-equilibrium thermodynamics. Most systems found in nature or considered in engineering are not in thermodynamic equilibrium. They are changing or can be triggered to change over time and are continuously subject to flux of matter and energy to and from other systems. Equilibrium thermodynamics restricts its considerations to processes that have initial and final states of thermodynamic equilibrium. The time course of processes are deliberately ignored but with far from equilibrium systems, the forward and reverse reaction rates no longer balance and the concentration of reactants and products is no longer constant. Damping of acoustic perturbations or shock waves are non-stationary, non-equilibrium processes. Driven complex fluids, turbulent systems and glasses are other examples of non-equilibrium systems within physics. Whereas standard thermodynamics describe systems that have a relatively low exchange with their environment, making them relatively closed. Non-equilibrium thermodynamics is dealing with systems that are in a generalized sense more open than closed, having an almost continuous exchange with their environment, meaning we cannot just describe them as moving from one equilibrium to another, but we now have to interpret them in terms of constant change, flux or flow of resources from the environment through the system. To recognize the difference between equilibrium and non-equilibrium, we can think about a ball at the bottom of a bowl. This is a system in equilibrium. Now imagine this ball rolling down a hill. It is now in a state of disequilibrium, there is a constant input or release of energy from the system as it travels across a gravitational potential gradient. In this process we can say that its potential energy is being dissipated, but this ball is really just traveling from one equilibrium to another. It will get to its lowest gravitational potential energy sooner or later and then just stay there. To get a truly non-equilibrium system we would need one that is continuously traveling across some energy gradient, continuously dissipating energy in the process. This is a dissipative system and is exactly what biological creatures do. From a thermodynamic point of view, this is essentially what defines biological creatures. They are able to maintain themselves far from equilibrium by accessing free energy and dissipating it and reiterating on this process, in so doing continuously traveling across some potential energy gradient. Dissipative structures are open systems, they need a constant input of free energy from the environment in order to maintain the capacity to do work. It is this continual flux of energy in and out of a dissipative structure which leads towards self-organization and ultimately the ability to function at a continuous state of non-equilibrium. A famous example of a self-organizing dissipative structure is the spontaneous organization of water due to convection. If we take a thin layer of water at uniform temperature and start heating it from the bottom, a pattern starts to emerge as the temperature between the bottom and top of the water reaches a critical level. The water begins to move away from an equilibrium state and an instability within the system develops. At this point convection commences and the dissipative structure forms as heat is transformed through the liquid, a patterned hexagonal or honeycomb shape emerges called Bernhard cells and the capacity to do work is realized. But as soon as the energy source to the heat is taken away, the ordered pattern disappears and the water returns to an equilibrium state. Just like the convection of water, biological organisms are also self-organizing dissipative structures. They take in and give off energy to and from their environment in order to sustain life processes and in so doing function at a state of non-equilibrium. Although biological organisms maintain a state far from equilibrium, they are still governed by the second law of thermodynamics. Like all physiochemical systems, biological systems are also increasing their entropy as part of the overwhelming drive towards equilibrium. In order to avoid this move towards equilibrium, they have to maintain themselves on some energy gradient. Just as the input and dissipation of energy within the water in the pan enabled the formation of non-equilibrium patterns of convection cells, it is the constant input and dissipation of energy that enables biological creatures to exist far from equilibrium. Open dissipative systems make an effort to avoid a transition into thermodynamic equilibrium by a continuous exchange of materials and energy with their environment. According to the theory of dissipative structures, an open system has a capability to continuously import free energy from the environment and at the same time export entropy. The internal structure and development of dissipative systems as well as the process by which they come into existence evolve and expire are governed by the transfer of energy from the environment. Unlike isolated systems or closed systems in a broader sense, which are always on the path to thermodynamic equilibrium, dissipative systems have a potential to offset the increasing entropy trend by consuming energy and using it to export entropy to their environment, thus creating negative entropy or negentropy. This prevents the system from moving towards an equilibrium state. A negentropic process is therefore the foundation for growth and evolution in thermodynamic systems. It can be said that order in an open system can be maintained only in a non-equilibrium condition. In other words, an open dissipative system needs to maintain an exchange of energy and resources with the environment in order to be able to continuously renew itself. For dissipative systems to sustain their growth, they must not only increase their negentropic potential but they must also eliminate the positive entropy that naturally accumulates over time as systems are trying to sustain themselves. The build-up of the system's internal complexity as it grows is also accompanied by the production of positive entropy which must be exported out of the system as waste or low-grade energy. Otherwise, the accumulation of positive entropy in the system will eventually bring it into thermodynamic equilibrium, a state in which the system cannot maintain its order in organization. In other words, this is what we call death within a biological system. Of central interest within non-equilibrium thermodynamics is then the idea of a potential energy difference or gradient across which the system exists and this idea is captured in the term exergy, whereas energy and entropy are central concepts within standard thermodynamics. The idea of exergy is central to non-equilibrium thermodynamics and systems ecology. It is a measurement of both the system and its environment, more specifically a measure of how the system departs from its environment, the maximum amount of work that can be done before the system comes to equilibrium with its surroundings. As such, exergy is a measurement of the potential for usefulness. Because biological systems are largely defined by this capacity to maintain themselves far from equilibrium, we can theoretically understand how alive they are by asking how far from equilibrium they are. This is what exergy tries to capture. As such, it is often used as a basis for the analysis of the health or resilience of an ecosystem. When exergy is zero, the system is in equilibrium with its environment, which would equate to the complete collapse of an ecosystem. Whereas most of the laws governing thermodynamic systems are theoretically time reversible, dissipative processes are path dependent and irreversible. A non-equilibrium state means for its description time and space dependent state variables. Because of the exchanges of mass and energy between the system and its surroundings, an irreversible process is one in which free energy is dissipated. How the process was performed comes to matter. This time irreversibility is closely related to efficiency. The destruction of exergy is closely related to the creation of entropy and thus any system containing highly irreversible processes will have a low energy efficiency. As an example, the combustion process within a power station's gas turbine is highly irreversible and approximately 25% of the energy inputted will be destroyed in the process. In this module we've been briefly outlining the basics of equilibrium and non-equilibrium thermodynamics that forms much of the theoretical underpinnings to systems ecology. We firstly defined thermodynamics in a very broad sense as the theory and study of how energy transforms matter through processes. We then went on to talk about the four laws of equilibrium thermodynamics. We discussed non-equilibrium thermodynamics as dealing with systems that are more open than closed, having an almost continuous exchange with their environments, where we now have to interpret them in terms of a constant exchange, flux or flow of resources from the environment. We talked about the theory of dissipative systems that maintain themselves on some energy gradient, allowing them to maintain a semi-stable state far from equilibrium importing energy and exporting entropy, a dynamic that is characteristic of biological systems of all kind. Finally, we discussed the idea of exegy as a metric for measuring this out-of-equilibrium state and the vitality of an ecological system.


current levels financially viable. As I mentioned before, with the commercial industrial mixed use where you have say industrial on the first floor and two stories of say office above, if we had tested that potentially on a different site where the land values were lower than the sites that we happen to test it in, I do think that that is a possibility and that could potentially work. So I do think that the adjustments that have been made to the proposed zoning from a mixed use perspective dealing specifically with the industrial in the office for a second, I think that may actually allow a viable mixed use commercial industrial mixed use product if it was the right site at the right price and the rents could achieve what they would need to for the project to come out to be financially viable. Thank you. Hopefully that answers your question. Well, I just don't want to take too much time. I'm so confused, but I mean, so I guess the second scenario was not financially viable, but would it have been financially viable with, sorry, the second site, would it have been financially viable if you had done any of the three other options to it? I would have to go back and test that to answer that question. I don't want to answer it on the fly. Okay, thank you very much. Sure. Thank you for the question in the comments. Mr.  I'm just curious if you're trying to ask a question. Yes, I was hoping to ask, well, actually not ask a question, but just make a couple of statements. Absolutely. Thank you. New to this. I guess my main concern is with allowing residential in the industrial commercial zone. My rec project is such a huge disappointment to me that it's actually eliminating an office building and substituting residential right in the middle of the industrial zone. And I'm afraid, see, residence is easy in Arlington. Everybody wants to build residential property. Commercial and industrial is harder. And I'm afraid that if you're allowing for residential, then the developers will grab onto that and any industrial and commercial parts will just be an afterthought. We'll basically be allowing more residential. And I'm looking for the town to do the harder thing. Not the easy residential, but the harder looking for commercial industrial uses. I just assumed see the land state as it is, then go for more residential on that. I think the commercial in the office will help with taxes. As one person said, not a great deal because there's such a small amount of it. But I'd very much like to see Arlington offer jobs as well as bedrooms. And if we allow, I can't say I'm totally against some residential here or there, but I'm afraid if we allow for any residential, it's the camel's nose under the tent and everything's gonna end up that way and the commercial industrial will just be an afterthought. And we would have lost whatever chance we have to add some diversity to our community. So thank you. Thank you so much. Rachel, we have one more hand up from Stuart unless it's actually Colleen that has a comment. But I'm just looking at the time. You've been very gracious with the amount of time you've given for the public comment tonight. Can I take the last comment? Yes, let's take that last comment and then we'll close public comment for this particular item there and then move to any questions that the board might have. Great, thank you. Stuart, please. Thank you. Yes, thank you for indulging me. I'll be very quick and thanks for the extra question. Stuart Morrison, 73 Kensington Park. So what I'm hearing from a number of people and expressed very lucidly by Alan Tosti just now is that there was a strong desire for industrial and office development in the remaining few parcels that we have. The problem I saw from your analysis is that the land cost and just the economics don't always work out as much as we would like it to work out. And so that's why people started looking at putting residential into the mix and that seems to make things work better. But as Alan pointed out, residential is easy. So if I was to give this, I'm not the person giving anybody any charge, but if I was to give this organization the charge as to where to move forward, my suggestion would be that rather than looking at residential, seeing that that's how you make money in these projects and throwing up your hands, the thing to do is to figure out what tools are required in order to tip the balance in favor of industrial or office uses. And again, I mentioned earlier, maybe too briefly, but taxes or incentives put in by the town or zoning changes, strengthened zoning changes. The question should be addressed in the final report is how do you make industrial work in Arlington without having to do residential? So that's my thought here, my suggestion. I thank you for your time. Have a good evening. Thank you so much. Rachel, I'll turn it back to you for comments from the board. Great, thank you. And thank you to Eric, Emily and Aaron for the presentation and for your thoughtful answers to everybody's questions and comments who posed them this evening. I really appreciate all the time you spent with us tonight. I'll just go through our list of board members for any comments or questions that you'd like to share or any clarifications that you'd like to ask. So we'll start with Ken. Well, thank you for what you've done here. I think this is good. I like the bonus structure with the height and so forth like that. And I wanna stay away from right now the mixed use because I think there was quite a bit of talk about already. I wanna address a few other things. If we want to encourage industrial or commercial space in these areas here, let's think of an owner of a company or a developer. What is, why would they build here? And I think one things we can't control is the land value because it is what it is. But what we can't control is maybe transportation to a certain degree. So I think what we have to look at is maybe having carpooling from these workspaces to parking structures elsewhere where they can commute in earlier or all the areas where we say, hey, we have a resource here in Arlington. We have a bunch of very smart people that live here that could potentially just walk or bike to these areas. And there's a pool of desirable employees. I think that's those smaller things we should look into that could actually encourage someone to pay the premium to develop or operate space here in Arlington. I think we have to look broader than just, we can build more height or we add houses. I think we have to look at the actual desire of people working here. They can work here, they can walk a park during lunchtime, easy access to restaurants, all those things that would encourage employees that would wanna work here as opposed to in an industrial park somewhere else or an office park somewhere else. There's a quaint community here that people wanna work here because they wanna live around where they work. I think that's something we have to actually look into a little bit more. And that's what I was seeing as comments. Thank you, Ken. Erin, did you want to address anything there? Do you want me to just take, I'm happy to just take all of the comments from the board and have you address at the end unless there's something specific that you'd like to respond to. I don't have anything specific to respond to with Ken, but I'd be happy to hear the compliment of comments from the board and then give a response. Wonderful, thank you. Thank you. David. I really appreciate the work that Emily and Eric and their team have done on the project. And I think the economic analysis that we saw tonight from the performance scenarios, I think was illuminating, but I think as we've already discussed, you could spin out more and more scenarios to try to dig into that even further. I really appreciate the input from the public and I share some of the concerns that have been expressed. Arlington has lost one commercial or industrial parcel after another over the last several decades to purely residential development in many cases. And I think with the scenarios that we've looked at, being somewhat pessimistic on doing purely commercial and industrial redevelopment in the industrial zones, I certainly see how that creates an incentive to want to allow some level of residential development alongside the commercial and industrial, but I really do feel strongly that we need to make sure that we are guarding against the residential components becoming predominant in our quest to spur development in those zones. Thanks. Thank you, David. Jean? Yeah, good evening. Yeah, thank you for the good presentations, great questions from the public and really good answers. I think that the consultants and the working group have done really great work on this and I think what we're going to get out of it, I hope is a new structure of how things can be built and developed in the industrial zones and then it will be up to the town to do what Ken and some other people have suggested, which is apply other tools that are available to try to attract the right development to the area. But really the first step is to figure out what the zoning should really look like in the industrial zones, so we can move on to use those other tools to get in industry, commercial, et cetera. So I think this is a necessary first step and I'm really looking forward to seeing the actual proposed zoning changes that come out of the next zoning while a working group meeting. I like the bonuses and incentives. I think they're absolutely what's done these days in lots of places, so we're not sort of inventing something new but using something that's good and that has worked in other places. I'm not opposed to residential in the zone. I understand the reasons why some of it will help round out the zone and might help with finances in some place. I think I'd share everybody else's concern that we don't want it to become a residential zone with token industrial or commercial and I think one of the tasks of what comes out of the zoning while a working group is to have a proposed regulation that will not not allow residential to overwhelm the commercial and industrial. I think one of the nice things about allowing residential here that nobody's mentioned is that there's gonna be enough residential to spark the inclusion of Arizona by law and we should get some more affordable housing here which is something that we sorely need in Arlington. I think that would be good. I'm just wondering, I saw our comments but I have a question I'll sort of put in here now. I'm interested in whether there was some thought about having artists working living space and if there's a way to incentivize that because that's often a nice thing to have in these sorts of areas. So I know that's encompassed by residential but was there any thought of any way to perhaps incentivize it? I guess we can jump in right here. It is an allowed use for artists live workspace as part of the zoning. Emily, anything in particular that you wanted to mention related to artists live workspace? No, it's not incentivized. It is allowed, it's not incentivized and there would have to be a separate structure that's instituted so that it could be confirmed that the people who are using the artists live work are in fact artists. We talked about a couple of different ways, different communities do it differently. Some have the requirements within the zoning itself which seemed not only onerous but unworkable. So we've proposed an alternative in this draft zoning to take care of that. The idea of incentivizing is an interesting one. I'd have to think about that one a little bit further. Okay, thanks. I'd like you to think about is there a way to do that a little bit? I like the emphasis on the environmental issues. In this, I think that's really terrific and it's clearly the way the town, the state, the world needs to go in a lot of ways. You know, last time you did a presentation, I was a little concerned about the definition of solar ready because it was only photovoltaic and yet that's still here. But I'm gonna quote to you from the Solar Ready Buildings Planning Guide of the National Renewable Energy Laboratory in which they identify three types of solar ready, photovoltaic, solar hot water and solar ventilation preheat systems. I'm not at all familiar with the third. I'm familiar with the first two but it sort of seems to me that our definition of solar ready needs to be big enough. So it's not only solar voltaic but also solar thermal and maybe solar ventilation preheat. Although I'm not sure what that is. So I can't comment about that one in particular. I would also prefer the electric charging stations or cars to be mandatory and not optional. They're not very expensive, you know and if they're mandatory they happen and I don't see them as being the breaking point for any particular development. Yeah, I did like the proformers. I don't know some of the details that people mentioned. It was really helpful and very instructive to see those. One of the things that I'm concerned about here and I don't know if it's come up or if you've talked about it is the potential for site contamination because most of these old industrial sites have some level of site contamination. And I wonder if that's come up and has been part of the discussion in terms of sort of the finances because it sort of seems to me that if it's there somewhere in the background the town can sort of start thinking about how to work with whoever the developers on Brownfield's tax credits and all those other sort of good things. So I'm just wondering whether that's been part of the discussion. It has come up but we have not done a parcel by parcel analysis to understand what sort of contamination would be on each site that would be and that's in the industrial districts. It's also typically the owner or the previous owner's responsibility to address those issues and not necessarily something that the town would would be a party to other than perhaps some overseeing. It would be permitting through the DEP primarily. Right, and we probably don't even know the contamination on the sites because they might never have looked for them but if they start doing construction or if they need construction loans they then might have to actually get that and find out. So yeah, I don't know what to do with it other than to say it might affect some of the financials that you've looked at for some of those things and I don't know whether it's worth mentioning that somewhere in the report or not. I'll leave that up to you. I'll just sort of put that out there or something to consider. Yeah, I think I'll sort of close up with, you know, I think we need to do this although what this is I think we'll probably be tweaked a little bit because if we don't, I don't think the industrial zones can reach a potential where it creates more workspaces for people in the town and more tax revenue for town. So we clearly need to do something about this. And then the town is going to need a process once this is in place to be able to do all the things of lots of people have talked about to make them happen. You know, one of the disappointing things that just happened was the tea cutting back on a lot of the bus service into Arlington and we just hope that that will be reversed when the pandemic's over but the last thing we need in town for our industrial zones is to eliminate the 79 bus and to combine some of the other buses. So I think that's just another thing for the town to work on but thank you very much. This was great and I really appreciated the presentation and all the work. Thank you, Jean. Katie? Like my board members, I just wanted to share my appreciation for the incredible work that's gone into this this really clear presentation that I think outlines a lot of really sort of exciting regulatory steps for our industrial zones and I'm really excited to see sort of the next steps and the specific proposals that you guys come up with with the zoning bylaw working group. So my comment is primarily, you know, in line with some of the conversations we've already been having during this meeting to say that I do really see and I think you guys made a compelling case for why we need residential in these industrial zones and I very much see my colleagues perspective as well as that of members of the public that we don't want to let the residential overwhelm but I think also acknowledging both broader economic trends our communities desperate need for housing. I think taking those things in concert it makes a really compelling case for including housing. And so one thing that I'm just encouraging you guys to think through as you start, you know thinking about the public process for these kinds of zoning bylaw, these zoning bylaw proposals is thinking about sort of other models for other communities that have implemented these kinds of proposals and this kind of mixed use zoning in industrial districts that were not the only place to consider these kinds of changes. This is pretty typical given that Arlington is hardly alone in facing these kinds of economic constraints. And so I think really clearly outlining sort of why this is necessary and why, how this can be possible actually I would say enhance sort of the industrial districts and a lot of ways to have that kind of mixed use development. So anyway, that's my only comment. Thank you for this. Great, thank you, Katie. And I'll just add that following whichever, whatever the final format of the zoning recommendations are recommended and potentially adopted I agree with Ken that as a next step creating that value proposition for incentivizing and attracting commercial and industrial development by really identifying the highly desirable workforce from a recruitment and retention standpoint and all of the other items that go into that type of a value proposition is a really important step for the town in terms of marketing this. And I too, in addition to what several numbers of the public have indicated as well as several of my colleagues and very much in favor of more limits and restrictions on the amount of residential that can be included in these developments as well. I think it's really important for it to be primarily commercial and industrial in its final format. Any other questions or comments before we close? Great, well, thank you very much. I really appreciate all the time and effort and again, especially the really thoughtful responses that you've given to all of the questions and comments that have come up this evening that's been very helpful. So thank you so much. Yeah, thank you, Rachel for the time and thanks to Eric and Emily for joining us this evening. We appreciate their work. I think we have a good understanding of what the conversation needs to focus on with the working, excuse me, the zoning bylaw working group coming up in January. So I think we have our marching orders. Jenny, do you have anything to add at this juncture? Just to thank Erin and Emily and Eric for all of your work on this and also the work of the zoning bylaw working group really been helping to give a lot of feedback and input along the way and sort of grappling with some of the challenging issues of what we have left and available that's industrial and commercial and what we can actually do with it. So very much appreciate the conversation and the presentation and all of the comments. Thank you. Yeah, thank you. Great, thank you all. And with that, we will close agenda item number six and move to agenda item number seven, which is the open public forum. So for tonight's open forum, any member of the public who wishes to speak, please use the raise hand function. As a reminder, you will be asked to identify yourself, your name and your address and then you will be given three minutes to speak with any comment that you would like to make to address the board. Okay. And I do not see any right now. So I will close open forum and that is our agenda for this evening. So do I have a motion to adjourn? So motioned. Is there a second? Second. Take a roll call vote. Kim? Yes. David? Yes. Jean? Yes. Katie? Yes. And I am a yes as well. Thank you all very much, everyone who attended and for all of our speakers this evening. Good night, everyone. Good night. Happy holidays. Have a nice Christmas. Happy holidays. Good night. Happy holidays.


Well, I think I would do now what I did when I was a student. I would go around to talk to people and say, what are you doing? That's exciting. So that's how I ended with the particular thesis work that I did. I talked to a professor and I said, I like that idea.  I'd like to work with you. And I think that's pretty much enough. If they've got something that sounds cool to do, maybe it is.


What's going on everyone? Sam here with the latent sports cards. We are ripping one box at 22 Paninian Origins football international blaster for Monty M. So good luck Monty. It's like an 18-wheeler lock up that's trucking that. I haven't seen him but they do have case hits and you can only get the numbered rookies in here. So you can't get numbered rookies out of hobby. Sameer White, Kenneth Walker Rookie. Yeah. Catapults Rookie, Johan Dotson. Yeah, there's the Big Bang case hit is in this one. Plus, like I said, we pulled like gold rookies numbered to 10. The 1-0 ones will be in here. So there's some big cards for sure. There's no lava. Shreya McBride, Malik Willich, Team Origins, Joe Naina. Kenny Pickett Rookie, nice one there. Kevon Tibidot, got Catapults, Christian Watson, and Tyler Algier to 2.99. There you go. Congrats Monty, nice Algier. You had a good day for me in fantasy. Thank God. Nice one. Here it is. Jalen Tolbert. There's a variation Rookie of Breeze Hall. Nice one there. And Team Origins, John L.A. Here's two to go here still Monty. Jalani Woods, Catapult Rookie of Kenny Pickett. One of Negroes. What kind of soda do you want? Well, they don't have that. Is this okay? Yeah. That's an underrated funny part of that. Yeah, yeah. Can't make this stuff up, man. Jameson Williams, Devante Price, and Orange. Kenneth Walker to 1.49. 29 out of 1.49. Nice one there Monty. That'll do it for your break Monty. Thanks again for the support my friend. We'll get those right out to you buddy.


Russia to deploy new howitzers to Ukrainian battlefront. Russia plans to deploy its latest howitzers against the Ukrainian armed forces, according to Sergei Chemezov, the head of the Rustic State Defense Conglomerate. These howitzers, which have a top range of up to 70 kilometers, are reportedly designed to provide a strategic edge over Western artillery models. Earlier reports in the Russian media suggest that several coalition SV howitzers have already been deployed to Ukraine's front lines. The coalition SV features a modern 2A 88 gun with a 152 millimeter caliber with a firing rate exceeding 10 shots per minute. It also incorporates modern automation for aiming, target selection and navigation processes. I think they will appear in the northern military district soon, since howitzers of this class are needed to provide an advantage over Western artillery models in terms of firing range, Chemezov said. In 2021, Russia's President Vladimir Putin changed the status of the Russian northern fleet, whose zone of responsibility was chiefly the Russian Arctic to the northern military district, incorporating into it also the Murmansk region, which shares borders with Finland and Norway.


If you do this, the Narcissist will never return. Narcissist target people who they perceive as being weak or stupid, people who are kind and generous, people who value love and companionship. They will use these types of people to get what they want. But once you refuse to give in to their demands, they're never going to be the same after that, because all they care about is getting what they want. And they will follow all the stops to achieve that, because in their minds they are the best things since sliced bread. They created a false self that is omnipotent. It's perfect in their minds.  But they always want things that they can't have. They have unrealistic desires and expectations, things that are impossible or complicated and difficult to do, which is why you may just want them out of your life. You may want them to never return again, because even when they leave, they always find a way to come back. They always have a reason or excuse to hoove you, but when you know who they are, it changes the game, because they will avoid anyone who knows their true nature. They will become non-confrontational, because they know it's a battle that they cannot win. When you confront them on their lives, they will become defensive, and they will see you as being unworthy of their attention. They won't want to be around you anymore, because they see you as a threat to their false identity. When you see through their facade, they know the jig is up. They know it's game over, and when you cut contact with them, they won't know how to find you. They won't know where you are, so you have successfully defeated the narcissist. If you let them back in, they will only come with more lies and manipulation, which is why the best thing you can do is to ensure that they never return, but if you have publicly exposed them, they will disappear on their own, and it's unlikely that they will ever return, because they can't stand the thought of being humiliated again, so they will avoid you. The narcissists cannot function without their false image, without it they will go insane, and then they will run and hide, until they're able to find a new audience, a new group of people who are willing to watch their performance. They will never come back to you. If you stop providing them with everything they need to survive and function, it doesn't matter how much time you wasted, or how much money you lost, it doesn't matter what you went through.  They cannot be around someone who doesn't care about them, because that type of person is unlikely to hand over the resources to them, which is why if you don't want them to return, you need to cut off the supply. You need to go gray rock, you need to avoid showing them any emotion, because they will try to guilt trip you into doing what they want. They only want to be around people who they can control, people who they can use for their own benefit, and if you're not going to do that, they will go. At that point you will be worthless to them. They won't have any use for you.  They would rather move on to someone who in their minds is better, so they will avoid you like the plague, because they see you as the cause of their irritation. They won't bother coming back, because they believe that they have already won. They believe that they have already got what they wanted, so they will be busy bragging about what they have robbed from you, while they're all flocking for more unsuspecting targets. If you want the narcissist to never return, you need to have a strong support network.  They're most effective when they're your only source of influence. But when you have other supportive people around you, it's more difficult for them to capture that type of person. When all is said and done, they cannot return unless you let them.  You can ignore their Hoover attempts. You can go no contact, and then there's nothing they can do. You just need to see through the illusion. You need to recognize that you're being manipulated. You're being used for what you have rather than being valued and appreciated for who you are. When you accept that, it will be much easier for you to walk away. Thank you for watching. If you found this video helpful, please give it a thumbs up. Share your thoughts in the comment section. Hit the subscribe button to receive the notifications. If you would like to support the channel, you can donate at paypal.amyslashnarksurvivor. You can book a one-on-one with me on my website. It's narksurvivor.uk. Thank you for watching, and I'll talk to you soon.


Okay. Hi everyone. I'd like to thank everybody for joining us today. Welcome to today's CNCF webinar. Take your monitoring to the next level. I'm Kristi Tan, Marketing Communications Manager at CNCF. I'll be moderating today's webinar. We would like to welcome our presenters today. Larian Heimovic, Co-Founder and CTO at Rookout, and Michael Aleil, DevOps at Rookout. A few housekeeping items before we get started. During the webinar, you are not able to talk as an attendee. There is a Q&A box at the bottom of your screen. Please feel free to drop your questions in there and we'll get to as many as we can throughout the presentation and we'll save some time at the end as well. This is an official webinar of the CNCF and as such is subject to the CNCF Code of Conduct. Please do not add anything to the chat or questions that would be in violation of that Code of Conduct. Basically, please be respectful of all your fellow participants and presenters. Please also note that the recording in the slides will be available later today at the CNCF Webinars page at cncf.io. With that, I'll hand it over to Larian and Michael to kick off today's presentation. Take it away, guys. Hey, guys. It's great being here. Thanks to the CNCF for hosting us. My name is Ivan Hamovich. I'm Rookout's co-founder and CTO. Here with me is Michael Aleil, our head of DevOps, and it's great being here, speaking with you. Throughout these presentations, Michael and I will be speaking interchangeably and we'd love to answer any questions you might have, so feel free to send them throughout the presentation and we'll try to combine them into it. So let me start by introducing ourselves. As I mentioned, my name is Liran Hamovich. I'm Rookout's co-founder and CTO. I've spent most of my career doing cybersecurity, starting off in researcher and developer roles, followed with team leader and product management roles. Along the way, I kind of fell in love in modern software management technologies, to see that agile DevOps already lean, and that's kind of how I fell into monitoring, as well as other disciplines, and also the deep passion to understand how software actually works, which kind of combines the story of Rookout, but that's for another time. Hello, everybody. My name is Michael Aleil. I'm a DevOps at Rookout, and I'm a software developer. Before I jumped head first into the ocean of development and DevOps, I was learning the ropes the hard way. When you start out, it's not easy. And one of the way that I stay sent is by trying to walk smarter than harder. That means automation and doing things the right way. So today, we wanted to talk to you about monitoring, and I think the first thing we want to discuss is the importance of monitoring. Why should you care about monitoring? I'm wondering, what's your favorite ID? How do you like to write code? Well, Michael, what's your favorite ID? Well, for example, my favorite ID is Web Store. I think it has all the necessary tools and all the features I'd like to have when I develop something out of an application. So for me as well, I am a fan of internet and other ideas, but in the end of the day, nobody truly cares about how do I, or we tell or any of us, write, build, test our code and how does it run on our laptops. What our, for instance, look at our CEO cares, what our board members care, what our customers care is, how does it operate in the real world? How do customers experience the product? How do they benefit from it? And that's the essence of the importance of monitoring because that's the only way you can truly know what's happening when the code is running away from you and in real environments. So why should you personally care? I'm guessing that most of you aren't founders or don't have to deal with customers most of the day, but as developers, even front-end, back-end, or even if you're doing operations, I think that most of us care about what is the experience that our customers or users are having as a day-to-day in our application. And that's one of the reasons you should care. That's also one of the reasons that hookup was founded to give the possibility to understand the application more intricately. Speaking of monitoring, there are two types of monitoring, two basic approaches. There's white box and black box monitoring. Let me start with telling you a bit about white box monitoring. And basically it wraps up as monitoring the software as if you wrote it, which we in fact did. And you can instrument your code by placing logs, metrics, or just any traces and see what is going on inside your application in real time kind of when it's running in production and not on your own laptop or dead machine. The second type is going to be black box monitoring. So that means you're going to interact with your application as an outsider, as the user would do it. For example, that means, you know, going into a website, clicking on a button, purchasing something, and that's basically the way that a user would experience his way around your application. And so let's dive a little bit deeper into black box monitoring. It's actually the same pair of the two in many ways. It's about monitoring the system from the outside. You exit as a customer. And so there are very little requirements. At the end of the day, you can very easily do it. And there is a whole bunch of tools that allow you to do it. To do this, think them and status cake allow you to send out DNS request to essentially HTTP requests. There are fancier tools such as the data, the detectives that allow you to actually simulate events request, and even full on a testing tools, such as Selenium cypress and test cafe, which allow you to see the latest sessions, and see the results. are often used for testing and integration tests, front end tests, they can also simulate a customer or user at a very high fidelity and seeing entire flows going through the system. The nice thing about black box monitoring is that you can always use it and so it's a great way to solve the problem when white box monitoring isn't enough. Now why wouldn't white box monitoring be enough? Maybe you've just created a new product and people aren't using it all that much just yet but you want it to be ready for primetime so that when people do use it it will be ready. So if you don't have any real-world traffic then white box monitoring is going to show you zero activity either way. Using black box monitoring you can simulate that activity and see that it's working properly. Maybe you already have an activity in the system but you have some very important edge cases that aren't being executed often. For instance making a purchase or changing a configuration. Those actions might be rare but vital and so you might want to do them then just using black box monitoring as well. And last but not least occasionally you see that you do have traffic but the traffic is highly unpredictable, highly variable. There are a lot of natural errors that occur within the applications traffic and so it's hard to monitor for errors or latency and so on because it's highly predictable and so using black box monitoring and running predictable well-known scenarios allow you to execute it in a way that you can measure in anticipates. On the other end you have white box monitoring which is basically the opposite. It's monitoring the software from the inside and we kind of divided it into three different three different layers let's call them causes symptoms and business. So causes is is what broke what what is breaking your system basically what is making your system not fork the way that is intended to. Then you have symptoms so that's going to be why is broke the way it did and the list none of the three is going to be business monitoring and that's a bit less standout and you probably haven't heard of it before but that's the way that you can actually gauge how customers or users are using your application and how that impacts your software development cycle. So let's start with causes. Causes were defined very well in the Google's SRE book and that's essentially a defect causing the system to misbehave. This is whatever is causing whatever the problem is in the system whatever infection so to speak in the system is causing it to misbehave and that can be a network outage a hard drive failing or a data center crashing whatever and how do you monitor for it? It's about setting metrics and thresholds first and foremost at the infrastructure level and load balancers and the hard drive operating system and so on. There are a whole bunch of tools for that some of them are commercial such as a Dynamics New Wellig and Datadog but some are open source such as Prometheus or Elasticsearch. Now it's important to note that systems are very very big and there are a lot of moving parts and each of one of those can fail but not any failure in a system especially in a large cloud native system is going to cause an outage or problem and so you want to limit your focus on monitoring causes for the causes of truly matter. One way to try and catch it which you can discuss which we're going to discuss later is focusing on causes that have caused problems in the past because if it happened once it's likely to happen again and you want to monitor for it. At the same time don't try to monitor everything because that's going to be a lot of work and there's a good chance that those local failures are not going to hurt your system. Yes I'm going on to symptoms so as I said before it's whatever is broken in your system as a whole what caused an outage or a kind of issue or degradation of service and the way you monitor that is going to be by setting basic metrics and thresholds and creating monitors or alerts at the application level of your of your server and you can use the same exact tool at Dynamics New Wellig, Datadog, Prometheus, Elasticsearch and many more and it's something that you should almost always use why because most of the time when you integrate your software that you're using into any kind of these tools you will have a default dashboard with any kind of metrics and that can be represented as for example HTTP endpoint metrics like error codes and latency or request per second and that's always something that you want to keep an eye on when working on your application so you know how it fails, how much load it can get up to but as Miran said it's not something you have to overdo you have to think about what you want to monitor and see because if you have too much data in front of you then you get overwhelmed and it's hard to understand what's actually important in all of that. We're going to show some example of that later but getting started with symptoms monitoring is very, very easy, very straightforward and can help with monitoring almost any system. Yeah so first of all we're going to talk a bit about an example of this kind of monitoring so this is taken from the Reddit status page and they show a bit of the system metrics on the website and as you can see you have all kind of graphs and dashboards showing all kinds of lines that represent a lot of things like the request rate of the website itself, how much errors the Reddit gets over a certain period of time or how much backlog that means how many posts or how many votes are in the queue of being processed in the application and as an example I will take the the graph about the request rate and talk a bit about the trend that is going to it's kind of going up and down and it represents how much traffic goes through in general to the application to the website over the course of a day and you'll see that over the whole week as it's shown here is quite stable and quite the same trend but the moment you know that and you have some kind of data to check it against then the next time that trend is going to change and you're going to have a bigger peak you're going to know and be able to predict that it's going to be most likely an issue with the application. And so the final type of monitoring the most interesting and the most underutilized one is business monitoring. What business monitoring is about monitoring the value system is creating for your user and your business. A whole bunch of famous companies that have done a lot of it for instance Netflix is famous for monitoring the number of plays on their videos. If people aren't playing enough videos then they aren't generating enough value, people aren't using them enough and that's a problem. On the other hand by the way if people are too often clicking the play button then there might be a problem with the streaming service that shows aren't getting started so people are repeatedly trying to launch new shows. Facebook started with likes, they are monitoring the number of likes in the system.  On the other hand if a number of likes per minute is going down and they're on call then they are going to drop everything and go ahead and check it out because this means something is wrong with the system and they are not making as much money and it doesn't matter if it's because the system is in a computer is down, the network is down or a baby player carried. The business is not getting what it's need and so we have a problem. And so that's exactly how you monitor it. You set cost to metrics and thresholds that measure what you care about and we're going to show a couple of examples. This time you can use the same set of tools, the same set of APMs but you can also use various BI tools if you're looking at more long-term analytics and you should definitely use business monitoring as much as you can because it provides you with much more accurate perception of what value you are generating and the challenging part here is not only defining but getting enough transactions, getting enough flow so that you can see the ups and downs and one way to do that is also to extend the time frame instead of monitoring every minute which is obviously awesome. You can also monitor every hour over 24 hours. You definitely don't want production down for 24 hours but if you just release the version and conversion rates are going down then it's better to find out after 24 hours than not knowing about it at all. And here are some examples for business monitoring. So some of the things that you'll be able to monitor as part of your business is going to be the first thing is visitals. How many people actually come and use your website or application? How many people log in? How many people sign up? And that can be a metric that you check per day, per week, per month. That's entirely up to you and what you need. Or as we talked about Facebook, like share and accessing content. If a lot of people click the like button, if a lot of people share a certain post, it might mean something is working but if less people are doing it, it might mean something is broken or not working as intended. Or taking as example other kinds of platforms, for example Zoom, how many people schedule a meeting per day or does it change when something special happens in the world or during a holiday or something like so. And the most important one that's what most companies care about is revenue. And for example as part of an e-commerce website, you can be able to monitor how much people are purchasing a certain item or upgrading a certain service and that might tell you something is working better than some other things. As one example, for example from what we are doing, we're producing a periodic final report monitoring our self-service signups. And every week we're able to see how many people actually sign up to the application and how many people do get how far in the process of the signup and starting in the application. And that's something that helps us a lot in having a better experience for new users. So I wanted to share with you a story. This is a story from the very first very, very early in Rookout. It's about two and a half years ago. Rookout was still a two-person team, just me and my co-founder. And at the time we weren't even VC funded. And we've just deployed Rookout to our very first customer, which by the way got acquired by Google since then. And so our customer, the VivoFoundee, installed Rookout, the data collection platform on his app and then logged into our platform online, went into his server, set the breakpoints, and so that he could collect live data from that remote app on the fly without having to write any code, rebuild or redeploy the application. And so he was happy, saw data coming in, data flowing. And so he turned, closed his browser and went home. At the same time, RSDK deployed on his Python application, kept sending data to our load balancer residing on Google at the time. And then data kept flowing into our Python backend, which were deployed in active, active mode behind the load balancer. Each of those backends got a piece of data and put it into the Redis database. We used the time to deploy. When I got in the morning, the system crashed and then I discovered the system crashed was caused by Redis going down. So when I got there in the morning, what I saw that the load balancer returned 502 errors, gateway inaccessible for all incoming requests. Checking out Kubernetes, which one of the backends was deployed, I saw that all backends were in a crash loop. They were in a crash loop because their hands checked include reading and writing from Redis, which turned itself into a read only mode, which is what Redis does when it is unable to back up itself. By default, when Redis is unable to fork, which requires a lot of memory, and back itself up, it moves into read only mode so that you would notice something wrong. And so overnight, his data kept flowing in from the customer's application, and our Redis bloated. At some point, it had more memory than the machine could hold, and it couldn't fork itself anymore. And so everything kind of crashed. And so it wasn't too hard to fix it, obviously. All we had to do was increase the size of the Redis RAM, the Redis distance RAM. And since those early days, our architecture is much bigger and much more resilient. But still, at the end of the day, it's a good story to see in a simple system how things break, and how can we monitor for them? Some example of what could have been done better to monitor and even prevent that downtime. And it kind of warps in with all the layers of monitoring we've talked about until now. So we could have as easily as having some metrics about 502 errors, or any kind of HTTP errors, and we could have known that something was not working. Because if the error rate was 100%, obviously the system is not working as intended. Or if we'd have an end-to-end flow, actually simulating a user doing what a system is supposed to do, end-to-end, then we should have known that something was failing in the middle of that process. Or as the last part of what we talked about, the business monitoring, there's actually no activity in the system. No new breakpoint could be placed, no data was flowing, nothing was happening. So it is a good indicator that something was wrong. And it goes on and on. And the most important one here, I think, is the database memory. When talking about databases, they are very prone to having issues, especially with IO, like memory and disk use. And that's one of the first things that's also easiest to monitor. It's very simple to put a new dashboard showing you how much memory or data your database is using and get an alert when it's getting close to high. And then you could even, as I said, prevent that downtime. I think the key takeaway from this slide is that you can use multi-layered monitoring. You can have many different forms of monitoring. Monitor both for causes, symptoms, business, and even black box monitoring. And you can monitor different areas of the system. And each of those can, especially when it comes to critical big errors, chances are you're going to see them across the system and then see them in multiple places. And it's very easy to get that. So get started with monitoring the more you have the better. But even just a handful of monitoring can take you a long way, especially when it comes to those big errors, everybody's afraid of. And so we've covered some of the basics, some of the concepts of how can you monitor. We've shown a very first downtime. And we are fortunate enough to not have many, but it wasn't the only one. But how should you go about starting your own monitoring program or improving your system monitoring? Where should you focus on? So I think at the end of the day, monitoring is very basic to start with. But it's kind of an iterative process, a multi-layer kind of monitoring. And it's going to go, it's going to get better and better over with time as you learn from your past experiences and learn about what you actually need as a business or as part of your application and what you need to know about what's happening inside of it. So the first thing that you can start and monitor is going to be HTTP, DNS, and TLS. So you can have easy, easy tools that can tell you when your certificates are going to expire, when your DNS is not up to date or not working, or even just trying to reach your system and can tell you when it is down. And to insanity test test and simulate how a user might experience going into your application and using it as of right now. You can have some kind of value indicator activity, meaning that you can monitor, you can monitor how your system is actually, is actually giving value to a user. And if something is not working as intended, for example, Netflix, if you click the play button and don't get a video showing, then it's not giving any value to the customer and in turn will down the revenue of the business. And the most you need to set up obviously the endpoint latency and error rate, queue item counts, it's something that comes most of the time by default with a lot of tools. But I'm going to let a bit learn, talk about databases and why this point is especially important. So what I like the most about endpoint latency and error rates is that it's one of the easier things to set up. As Michael mentioned, many APMs have been out of the box. And it's fairly easy to configure. Just if HTTP requests take more than half a second on average, then that's a problem. If more than a 5% of my requests are 500 or several errors, that's a problem. And that those numbers I just wrote might or might not work for your setup. Maybe your setup need requests under 50 milliseconds, or they can be under 5 seconds. But that's very easy to experiment with. Take it a bit up, take it a bit down. And in a couple of iterations of very little work, you've got yourself some basic monitoring to see that everything is going well, or that something's wrong. And that's obviously as things move along, you can obviously make it more complex, divide it into various endpoints or divide it into various servers. But even this very basic configuration helps you get started. So another thing that's definitely worth checking out is queue icon counts, as queues items increase, as backlogs increase, especially if it goes beyond the third rate, when your system is not ingesting a request date or whatever at a fast enough rate. And that's a problem that's waiting for happen. Obviously queues are there to protect it, to buffer you, so that you have some time to response. But if those numbers are going up, you probably want to check out why maybe scale up the system or figure out what's going on before things break in a nasty way. As we mentioned in the past, databases tend to be very resource intensive, and they tend to be very critical to the system. And so you should definitely monitor databases, especially monitor the memory and disk space, and if one of those seems to be going, seems to be filling up, then your system might be in the way for how time. So definitely check out those causes. That's the only cause I would recommend starting out with, unless you know what you're looking for. So the alternative way that we choose to use monitoring is based on three steps that you're going to do again and again to get better at it.  The second thing is going to be to install and configure a few tools, meaning you want to collect data using these tools. It can be metrics, it can be logs, it can be traces, and anything that you want to observe. The next step, once you have some data, is going to be to analyze and see how it works for you, how it shows the actual state of the system, the actual state of the business, and what you can actually understand from it. And once you've done all of these three, you start to know what is working for you or what is not working for you. And one of the most important things I think is that if you overdo it too much, you're going to have a hard time understanding what is actually important. If you have 15 monitoles in a layer that's going on at the same time, it's going to be even harder to know what is wrong with the system as a whole. But if you have, let's say, five monitoles that are very specific and tell you what is wrong at a glance, it's going to be a lot easier for you going forward. And so you start out by planning your monitoring. What are you trying to achieve? What do you need to know? What data record you like? If you have no monitoring, then probably any piece of monitoring, any piece of data will be useful. If you already have some monitoring in place, then think about what's missing, what's keeping you up at night because you have too many layers and you need more data to fine tune them. What's missing and didn't make you up when the system went down. And in general, which parts of the system do you care about the most? What's the most danger to your business? What's the most risk? What do you want to make sure that if something goes wrong, you know? So the next part is going to be implementing the data. You can install any tool. It's going to be going from data docs in your relic to open tracing to any kind of log file planning utility and instrument your application by setting and sending metrics that are important to you about your users, about the flow that your application is going through, and pipeline the data where you're actually gathering everything. So this is actually one of the things people are about ROOKOUT. ROOKOUT allows you to instrument the application without having to write more code, redeploy, restart and so on. You can just get the data on the fly from the existing deployment without waiting for the next sprint. And then once you get the data, either the easy way or the hard way, you have to analyze it. You have to observe the data and see what is the data showing. What would be a useful dashboard for you to know the overall state of the system? Are things going up or down? Is performance improving or degrading and so on? Things through. What do you want to be allowed to develop? And when that happens, do you truly want to be allowed to develop? Was that the problem that you truly required you to wake up and deal with it? Or was that something minor that could have waited until morning or just resolved itself and you don't care about?  So we do have a question about the audience, from the audience. I'm going to read the question aloud and we can answer it. Are we talking about combination of app telemetry collection, usability, infrastructure and app monitoring in the same platform? There is a multitude of OSS and commercial solutions out there, including Prometheus, Wavefront, Neuralic, AdDynamics, etc. What is your main differentiator? So ROOKOUT isn't a monitoring software. ROOKOUT is a data collection and pipeline platform. We allow our customers, software engineers, to provide software on the fly. And so we allow software engineers to connect to code running and staging production other remote environments and extract application snapshots, metrics, logs on the fly and pipeline into any of those other analytics tools without having to go through the rebuild, redeploy, restart cycles. Michael, anything you want to add? Yeah, just that, you know, all that process of rebuilding, rewriting code, going through test and CI CD and all that, that is what is taking the most time for, I think, a lot of the most developers. And that's also what we see here with monitoring. It's that interactive improvement that takes the most time getting it right, because we don't get it right the first time. As much as we want to think we are the best in our field, it's hard to do it the first time. Overall ROOKOUT is used for a better understanding code, learning code, debugging code, and monitoring code and not just monitoring itself. If you guys have any more questions, feel free to... So that's kind of all we had for today. We'd love to hear any questions Michael? Yeah, just a friendly reminder that there is the Q&A box at the bottom of your screen in the Zoom. Feel free to submit questions. We definitely have some extra time. In the meantime, there was a question that I answered in text about, can we get the slide deck? So yes, it will be available after we finish this recording. Christy, are you able to tell where people can find that, the slides? Yeah, most definitely. It'll be on the CNCF webinars page. So it's dncf.io slash webinars. And as we were saying, the recording on the slide will be available later today. And it looks like we have a question that just came through. Yeah, what is the difference between ROOKOUT and Jager or other open telemetry products? Go for it. Yeah, so the main difference is with ROOKOUT you're able to, let's say, debug or understand things live in production. Whereas with Jager open telemetry it's going to be, again, that process of you're looking at your metrics and monitors, dashboards, and you're always missing something. You don't have the full picture and you want to add something new. So what you're going to do in the traditional way is going to be to add these metrics in your code, redeploy, go through the entire pipeline, and maybe in a few hours or a day later you might see the new results. And what we do allow to do is do that in a matter of one click in a few seconds. I think the best way to learn more about ROOKOUT is to go online to the ROOKOUT website and check out the videos. I think they're going to get you and try to understand a lot what ROOKOUT does a lot better than anything we can say. And feel free to reach out to us to learn more about it. Yeah, definitely. The second question, how do you collect the metrics? Are there sidecar containers, agents, etc? I'm thinking that you're asking about how we collect the metrics at ROOKOUT. So Liran, if you want to answer this one. So ROOKOUT is an SDK you install into your app that allows you to do metrics collection, low collection on the fly as simple as that. So if you're running in Kubernetes, you're going to add the SDK into your app, build it into the container image, and that's it. Oh, a lot of other questions. Hi there. In your opinion, what would be the cloud native monitoring stack, the factor in the market? I think it all depends on what your tech stack looks like. Are you purely cloud native, or do you already also have some more legacy software, whether that's Java web applications or mainframes? Do you need those stacks to be combined together? If so, you probably want to look at something more traditional, such as fDynamics. If on the other hand you're purely cloud native, if you're managing your own servers, then Devdog is a good combination of infrastructure and APMs. While if you're letting somebody else manage servers for you, you might want to look at something that's more tracing oriented, such as Exegon or Honeycomb. There's a big difference, and obviously some of your security and performance needs are going to implement that as well. I guess if there was one size that fits everybody, then that window would own the market. It looks like there's another question in the chat, and that didn't make it over to the Q&A. I'll read it to you, guys. It's from Josh. It says, can you show how Rookout provides more insights than typical APMs like Yeager? I'm pretty sure the answer, you're telling me, but I'm pretty sure the answer is no. We're not allowed to show the product on this webinar. Correct me if I'm wrong. Yes, that is correct. The answer to that is no, but feel free to reach out on LinkedIn, Twitter, or just check the website. We'll be happy to show you in private more about it. Great. Great. Okay. Well, I think that covers all of the questions. Thank you again, Liren and Michael, for a great presentation today, and thank you all for joining us today. Just another reminder that the recording in the slides will be available later today on the CNCF webinars page. Oh, and we got one last question here. Could Rookout do the same thing like Scout APM that traces N plus one problem? I personally don't know Scout APM, Liren. I don't know Scout APM either, so I'm going to need some more details on that. Sorry. We'll check it out after and drop us an email and we'll get back to you. No problem. All right. Anyway, thanks again, everyone for joining us. We hope to see you at a future CNCF webinar. Have a great day. Stay safe. Bye. Thank you for coming, everybody.