I'm Jay Fidel. This is ThinkTech on a given, what is it? Wednesday. And we're talking today about how the reopening is going for tourism in Hawaii.  But we really have to care about tourism now. Tourism is the engine of our economy. What was on in Waikiki and the tourism industry affects all of us. And increasingly so, it is what makes this state tick. Don't forget. Okay, so we got to, we got to talk to people who, who do know about what's going on in Waikiki, like Allison Schaffers from the Star Advertiser. She reports on it. Star Reporter, and that's her beat, Waikiki and tourism. And she knows so much about it. It's really amazing and wonderful to have her on the show. Thank you so much, Allison, for coming around. Oh, it's my pleasure, Jay. Thank you. So, you know, you had this really interesting article. It was a couple days ago. It was really valuable to read it because it, it gave us a window inside what was going on with the hotels, big and little. And for that matter, other businesses that were accessory to the hotels. So can you talk first about the hotels? As I'm, I'm, you know, looking at the article, there are 270 major hotels in, I guess, Waikiki or maybe that's the state. A lot of them are, they're not doing business. What's the story? Okay. So the 270 number is from a list of watching, maybe the top lodging accommodations across the state. So that's if you take the top hotels and timeshears and condo hotel. So of that number, less than half are currently open. And one of the things that's interesting, I spent some time computing that yesterday. If you take a look at who's closed, only about 40% were planning to reopen for the August 1st even. So we still have about 142 properties out of that 270 that are closed and only about 40% of them were going to reopen for August 1st. Other, other ones, and there are a lot of the big box, big brand, large properties are waiting longer because in a lot of ways, reopening, if you've got a huge property with huge infrastructure and energy costs, it's more expensive to reopen at very limited occupancy. Yeah, some of them, some of them have taken the approach of refurbishing the hotel. A couple of them you mentioned in the article, including I'm remembering the Holly Kalani for one, and they don't plan to reopen. They might have reopened earlier if there wasn't all this up down about, you know, lockdown and then reopening and then lockdown. But they're talking about the middle of 2021 now. What's going on there? If you look at a property like that Holly Kalani, they have a huge inflow typically from Japan. And while Hawaii has been working on trying to get a travel bubble or a travel corridor with Japan, we like their low numbers and we thought they would like ours. The issue is it's really hard for any other country to separate Hawaii from the rest of the US. And so while we're working on bringing, trying to formulate travel agreements with places like Japan and Korea, New Zealand, Australia that have like-minded philosophies about COVID and limited case numbers, we haven't... Those are the bubble countries, right? Those are the bubble countries. But we're not, you know, everybody says, oh, well, let's just reopen the bubble countries. We feel like we'd rather have those visitors back than the US visitors, which is our core market. And here's the thing, you know, they don't want us back right now. And if the Japanese visitor were to come, they would have to quarantine to Hawaii, which is part of the US. They would have to quarantine for 14 days upon their return to Japan. And there's not very many people that, you know, want to do that. And therein lies the problem with that. But you take a property like the Hale Kalani, and you take some of the main Waikiki ocean fronts, far more heavily dependent on Japan than the rest of the state. And that's not looking too promising.  And if your numbers are going to be too low to make a profit at all, in some ways, it suggests that maybe you're better off borrowing money or reinvesting so you can be repositioned for the future. Yeah, are any of these hotels on the market? Are they trading? Because, I mean, if I'm a hotelier that's not making any money and I don't see a way out of this, at least not for the short or intermediate term, my first thought is going to be to find a buyer and get out of the business. Yeah, I think, you know, in other times, we've seen that. I think it's a little early yet. One thing, the lenders, they're still been working with a lot of the properties. I think statewide, we have probably somewhere between 40 and 50 properties that are on the, you know, the watch list for the commercial back securities. That doesn't mean that they're necessarily in default, but it might mean that, you know, they've got some sort of an arrangement. So they're being steady. But honestly, when it comes to hotels, most of these lenders, they don't want to take back a hotel that's, that's, it's hard to run them anyway. And the best of times, it's very specialized. And when it's the worst of times, how is that going to be helpful to them? I understand from talking to the industry that most of the closed hotels are still losing between 1 million and 1.5 million every month just to be close. So if you take that back as the lender, it's, it's, that's not necessarily desirable either. And I think we'll see, we'll see some defaults. If this carries on, I think we'll see some sales. In the past, we've thought we've seen sales in these times. Hawaii being Hawaii, we haven't really seen fire sales. We tend to trade at a premium. I hope that still happens in the future. You know, but if you look at other destinations, we're not necessarily any worse off, it's just that we depend more on tourism here than some other places. What about repurposing the hotel? I mean, for example, there was talk about make putting the homeless in them because the homeless are very exposed to COVID in their homeless way of living. And likewise, you know, the issue of taking COVID patients, I don't know if we've achieved that level of COVID patients, but there was also talk about, and in other places this has happened with hotels, tend to be hotels in other places. I wouldn't say that the hotel industry is unwilling, but again, that might be a little early. If we see that in other places, what we've seen is that the government would tend to take out a contract at a particular hotel and more or less lease the space and the government is paying for this program. From a hotelier standpoint, that's probably not the first way you want to recover your money. I mean, can you imagine being marketed later as the homeless hotel? It doesn't exactly, you know, it's not what people think of when they when you're having your traveler's book a trip to Hawaii. Or the COVID hotel, for that matter, there's been other properties that have turned into places for quarantine or places for COVID recovery or hospitalization. We may see that down the road. You know, our numbers aren't such that we need that right now. And, you know, I don't know, though, there may be, if we don't get these hospitality workers that to work, there might be an awful lot of new families that actually are part of the industry that are now homeless. So what about now? You know, we have the August date. We have this potential hybrid of the quarantine and then the pretesting on the mainland or wherever so that we can get a certificate. You know, is that how does that affect the market here? Does that build the confidence in the public? Does it build? Does it build the hotel guests? Does it build the industry? Is it affecting things in any material way? I think there were a lot of problems with the August 1 reopening because they didn't really fill in a lot of the details quickly enough. So actually, if I talk to a lot of the hotel industry, which is part of the reason I think we were only seeing about 40% of the hotels that were closed planning to reopen for that August 1st date, they were actually a lot of them were seeing fewer bookings, so more cancellations for August and September than they were seeing future booking. So it's going the reverse direction. A lot of that was I've heard from very disgruntled travelers, many who have rebooked their trips three times or more to Hawaii without knowing at the time it was announced without knowing if children would have to be tested, not knowing where to get a test, how much it was going to cost, checking with their providers and finding out some of them wouldn't test unless you were sick. Some of the providers were saying they wouldn't even CVS was telling people in some places that they wouldn't get the test results back from it would be an average of five to 10 days. And that's, you know, with the 72 hour window, that's pretty risky for a traveler so much to come to Hawaii and then worry that if they don't get the test result, they would have to quarantine. Now, Governor E. Gay on Monday when he rolled back the date to September first, he did answer a few details, he did say all children would have to be tested. That's pretty humbug. I don't think travelers will like that. But the one thing that he did say that I'm getting some good feedback on is that if you take the test and you don't have it back in the 72 hour window, that you could come here and quarantine until you got the result back, and then you could be out of quarantine as long as it was negative. That's probably a pretty good compromise. That will help. I think the other issue with the pushback now, you know, it gives us a chance to restart bringing tourists back. But I think that there's this perception that somehow the floodgates are going to open and we're going to have 10.4 million visitors or like last July, we had over almost a million visitors, you know, nowhere near. And part of the reason is some of the things that you and I had talked about before that travelers don't necessarily have confidence. Some people don't have confidence in traveling. It's going to depend on what level of confidence they have. And some of these things are out of Hawaii's hand. Some of it's the economic issue. A lot of it's the, you know, with COVID cases sweeping the mainland, especially the some of the US West states where we rely on 45% of our visitor rivals typically that that is not conducive to thinking about planning a trip. If I'm told it's so dangerous, the California governor and I live in California is closing the bars in the restaurant.  I'm not thinking about booking a trip. So in some ways, this delay, we might have, we already missed the summer peak travel period for families. We might have missed another window because there was a time when COVID was not as active as it is now. Now we've got a more active period. So it's hard to say, you know, when we reopen what that's going to look like. But, you know, even on a good year, September or October are not peak travel periods. Well, okay, that gives me a tiny bit of comfort. But you know what? This this thing about the quarantine, even when it was first adopted, I personally, I was skeptical. Why? Because most my observation is that most tourists who come here do not come for as much as two weeks. They come for like a week. That's that's the package. And so how can you possibly spend two weeks in quarantine when you have hoped for getting out and doing stuff and getting out of your hotel room? I just can't imagine that working. I can't imagine a tourist legitimately sincerely intending to come here and spend two weeks in quarantine. Have they been doing that? Or have they been breaking breaking the rules? We neither are some quarantine breakers. We've sent some of them back, including the what the last month that was the 21 members of the carbon nation on the Big Island. On the other hand, I do think that the definitions of who is a visitor and who is a returning resident and who is an intended resident can be somewhat blurred. And I do think that there's a fair amount of people who might be originally from Hawaii or might have family in Hawaii that are either furloughed from their jobs for a very long time or have been laid off and and they may be coming and they may be willing to quarantine for a time. If you're planning on staying, you know, for the entire summer, two weeks at home is probably not so bad, especially if you came from a place where the lockdowns were worse or you had food or shelter insecurities, those types of things. So it's really hard to say. We know that since April, the COVID Flight Assistance Program through the visitor Aloha Society of Hawaii has sent back about 157 visitors who were not prepared to quarantine. And in some cases it was it was flagrant disregard. In some cases it was just lack of knowledge. But in any case, Hawaii didn't pay for all those tickets, but they some in some cases they paid for the whole ticket or a portion and those people have been returned home. Oh yeah, I wanted to ask you that. So yeah, so I have a ticket. It's a return ticket. The dates are fixed. This is a problem. You know, the airlines are pretty inflexible about that. And I get here, I violate the quarantine. The state of Hawaii tells me I got to leave and you say this, the state is paying their way back. That means me as a taxpayer, I'm paying their way back. In some cases, like say somebody comes and they don't have any money or any means. The only other alternative is to put them in our prison. So in some cases that might be more expensive. I don't know out of the 157 how many have gotten full freight. Sometimes the help is just getting their flight, the airline to allow them to return and the state hasn't spent any money on that. So you know, it just depends. What about the airlines? We spoke about public confidence and all that. What's the state of affairs on the middle seat right now? If I want to have confidence, I'd like to see the airlines make it as safe as they can for me. I'd like to see the guy at my right and my left wearing a mask all the way through and I'd like to see an empty seat. It's not a complete solution, but at least it gives me some confidence that the airline cares. You know, I think that all the airlines are taking some steps to restore public confidence. Some are doing more things than others and it varies slightly. I think most of the carriers are requiring masks. The middle seat, originally most of the carriers had committed to it. I understand a couple carriers have bowed out of that and are already booking middle seats. So you know, I think it's like anything else. The onus is on the consumer to double check before you book and brands are different for a reason. So certainly if you want to come to Hawaii and you don't want the middle seat to be filled, there are some carriers who are flying without a middle seat at this point. I don't think though that that's going to be the travel of the future. It's not sustainable for the carriers to be able to afford that. You know, I think currently right now the load factors are so small that it's not as big of a deal. Later they're going to need some revenue coming in, especially when they don't have the federal bailouts. So I think, you know, we can expect to see that for a little bit, but I don't know for how long into the future. Yeah, well I hope we got a recover on this. I mean, you know, I'd like to talk to you about the factors that enter into this decision process by the government and by the hotels. I mean, one is the union and all those people was at local five. We had them on a show a couple months ago and they were very concerned about their people as they should be. And you know, the query whether they had the deep pockets to keep on paying benefits on an indefinite basis. But then you have the hotels themselves. They are a serious lobbying force. They don't mind going down the legislature. They don't mind talking to the governor and so forth. And they're going to be asking for reopening. They're going to be asking for every opportunity to get back in normal. How is that working? Because, you know, it may not be the best thing for the state in general. People outside the tourism industry may be maybe worried about that. And, you know, where is the political and economic influence on this? Where is it coming from and how effective is it? People worried about, I just want to make sure I understand your question. People outside the visitor industry worried about what in particular? Well, they worry about some some guy coming here right now, quarantine or not, and bringing the virus. They worry about, for example, testing a person, finding a person who is sick, testing that person, tracing that person, tracing everybody he talked to, and finding out what, you know, where the infection went from him into our community. I'm not sure we're doing that. So that's a concern of the person outside. And then on the other side of it, the hotels want to reopen, I think. The union wants them to reopen, I think. So where is the tension on that? I think there are a lot of detail to still be worked out. Obviously, we're trying, they're trying to come up with this September 1st now reopening plan that has some rules that you would be subject to a pre-arrivals test, and that if you didn't have the negative result, you would have to quarantine when you got here. Obviously, we know that's not a foul-proof method, because in many ways, as you pointed out, the quarantine is it's mandatory, but it's still kind of on the honor system. We could do something different, other destinations have. Some people are pushing for that in Hawaii. Ultimately, I don't know, you know, if that will get any traction or not. There are destinations like, I think Cambodia is one of them, that if you go, you're required to do about a $3,000 deposit that pays for your quarantine intel and all of your meals until you're out of quarantine, and you know, they take that stuff very seriously. There's some destinations that are doing that. Other destinations are requiring a second COVID-19 test, with the idea that if you stay more than a few days here, that they would want just to make sure that you didn't pick up COVID-19 on the flight, or in some other you know, if it or even before you got here, that in the window between the test and you getting on the flight, but you it didn't materialize. You know, certainly, these are things that we could do. There's a bit of an outcry from the visitor industry. They don't want to see that, because they feel like if we make it too onerous that visitors won't want to come back, and they're not looking at very many visitors returning as it is. I mean, I was on a conference call earlier today with local five, and even for the August 1st reopening, some of the bigger properties were talking only about bringing about 12% of the workforce back, and that's based on they think their occupancy is going to be about 12%, and then they thought the next month they would bring back 20%, and then 30%, and then maybe 40%. From what I'm hearing in the industry, we're not expecting to see, you know, 50% occupancy into maybe in the holiday frame if we're lucky, but probably not until next year. Yeah, it's pretty serious now, because our economy is dependent on tourism, not just the hotels, but all the accessory, you call them accessory, you know, businesses in your article, and I really wonder if we have a sense, if people in general have a sense, and whether you have a sense of how profound the damage will be on a long-term basis. You know, if you extend this whole process into September and October, oh my gosh, and then, of course, is the Christmas season where, you know, so many people come here, and we may not have that. If it's a function of the vaccine, I'm not sure we will have the confidence necessary to bring those people over here by the millions, essentially. They're not here, what happens to the rest of us, because that money, you know, feeds through the whole economy, keeps us all going, and if we don't have jobs and we don't have that money filtering through the economy, gee whiz, what happens to Hawaii? Fact is, it's the engine of our economy, so you must be thinking about that. What do you think is going to happen here? Because we have no immediate solution. Let's talk about a vaccine and a therapeutic, but no immediate solution. And if you had to make an optimistic guess, you would say, well, sometime in the spring, can this industry last until the spring? Not without some additional bailouts or support, and certainly the people can't. I think part of the problem that we have in Hawaii is, you know, but it's not just Hawaii, it's everywhere. People find it hard to pivot, you know. We went into this, we started the year out with the lowest resident sentiment towards tourism ever. We had 10.4 million arrivals that brought in about 18 billion dollars in visitor spending, but on an adjusted basis, it was really only about what we've had when we were bringing in, you know, 6.5 million visitors or so. And because of that, and because they were pockets of the community that were feeling over tourism, there was a lot of a resident sentiment against that. And the natural inclination, I think, now, and it's a wise one, is to take a look at how we can rebuild tourism in a way that would be favorable, and it would take into account some parameters that would make people feel like there was less tourism. The problem is we really started discussions about rebuilding tourism, probably too late in the cycle, and now we're entering a phase of desperation. You know, it works when you take some time to think about adjusting a destination, and the reason I say that is, look at Kauai. They were shut down for, the North Shore of Kauai was shut down for more than a year because of mass flooding, and when they reopened, they put into place the tourism management plan for Hain Estate Park that really did help that community feel a little bit less overburdened and overtaxed by all the cars along the roadway and, you know, not being able to go to their own natural attraction. We could do that for the state of Hawaii too, but I think we've gotten into the situation where those discussions should have been taking place immediately as we collapsed tourism, as well as the discussion of how do we start bringing it back. But we were so panicked about just trying to be safe, and I understand that, that now we're kind of playing catch-up, and it's very difficult. You know, you talked about people being afraid, you know, with tourists coming, and you know, I definitely get that, but without a pre-arrivals testing program or some protocol in place, what we're left with is basically a quarantine model because we cannot stop U.S. people at this point from coming to Hawaii. It's a state, and as an American citizen, you have a right to go to any state that you choose to. And so we cannot stop people from coming into Hawaii. We can insist that they follow the quarantine, which they may or may not. Or, you know, we could put in a testing program, and we might get a few more visitors, and we would hope that, you know, probably the visitors that would be willing to jump through those seats are a more compliant and well-heeled sort of visitor because I'm hearing that the test will probably cost anywhere from $150 to $300 a pop. And so if you're looking at that, that's the sort of visitor that Hawaii typically has said we want fewer visitors coming that are able to spend more while they're here. You know, but beyond that, the whole delivery aspect of it is something we have to talk about too. When a visitor gets here, if things are not open, if they have to wear a mask everywhere they go, if the residents aren't welcoming because they don't want them here, because there's not that confidence, if they can't get housekeeping in their hotel rooms, if they don't have service, if they, you know, we're going to have the other issue of what kind of an experience can we provide for them. So these are all discussions that need to be taking place as we head into this September 1st reopening, and hopefully since we had the August 1st start and stop that gave them a little bit of a head start on preparing because, you know, last week we certainly weren't prepared for the August 1st reopening with less than a month in, and so hopefully with, you know, now that there's a little bit more time they'll work out some of these details. Hope so. It's a matter of rebranding, you know, it's not so easy. It's a matter, for example, of putting ultraviolet light in these hotels, you know, to kill virus. They do it in hospitals, they can do it in hotels, and if I'm a tourist and they tell me, oh yeah, you know, between visitors we go through every room and we use ultraviolet light, I feel better about it. It's a branding issue, and I want to think that Hawaii is not only clean but super clean. But let me ask you my last question, Allison, because we only have a few minutes left. It's probably the toughest question of all, I'm sorry. So you mentioned that this is the time to think and maybe reimagine what tourism is like in Hawaii. This is the time, not later when we're, you know, in greater trouble, not later when a lot of companies and tourism organizations have folded. And so, you know, I'm a little worried, for example, about Alamoana. That's an accessory retail establishment. It's directly connected to tourism, of course. Now there's talk about building condos in part of Alamoana instead of having shops. Now that's troubling in the sense that those condos are not necessarily going to be for local people, are they? They're going to be for investors offshore in Asia, whatnot. So you say, well, that's a change. And then maybe that comports with, you know, the dynamic of, you know, of the new world, of the new COVID world. But it's not necessarily something I would treasure myself. And so the question is, what do you see for tourism in the new post-COVID world? When the problem is solved and people start coming back and we have to rebrand ourselves and attract tourists, maybe not in the same numbers, and integrate that tourist experience with the, you know, the local community, somehow they get it all harmonious. How do you envision tourism in Hawaii when we get through this thing, the other side of the tunnel? You know, I think what has always been special about Hawaii is the culture and the environment. I think that that needs to be front and center.  There are destinations in the world like the Galapagos Islands and places like that where people are willing to pay a premium to go for a very special, very unique, very exclusive experience. And you know, that may be more where we're headed. The mass, mass tourism of Hawaii when we opened it up for jet travel and anybody can come to Hawaii. You know, they'll still, I think they'll still be, that'll still be a part of the tourism economy, but maybe less though as we try to pivot into more what the community would like to see. And now that they're launching campaigns right now and, and, or starting, starting to go towards that direction and what they're hoping for, appealing to visitors to care about Hawaii that want to do what's right for this place while they're here and are already invested in our destination. So you know, hopefully those are some of the discussions that are taking place. You know, how do we make our rules and lockdown get us to there rather than just using them to stop travel? How do we use them to reopen travel in a way that we would like to see it reopened? Yeah, Alice is great to talk to you. You know, there's a long road here and it's still going to be central no matter what happens to the state of Hawaii and you're going to be there, you're going to be on it, you're going to be reporting from it. And we hope we can check in with you from time to time and see what's happening. Really appreciate it. Oh, my pleasure Jay. Thanks so much. Aloha, Allison. Aloha.


And today I'm going to start my discussion with circle. In fact, I'm quickly going to take you through main and JEE advance concepts. But at the same time, I would quickly revise whatever you have learned in circles so far without much delay. So let us start our discussion with the first conic, which is the simplest of all, which is the circle. I'm not going to take a lot of time for revision. Just a few things that I want you to all know. First, you should know the equation of the circle in various forms. So we'll start with equation in various forms. First one is the center radius form, which is quite familiar to all of you guys. So if you have a circle whose center is at h, k, and whose radius is going to be a units, its equation is given as x minus h whole square y minus k whole square equal to a square. No doubt about it. Very simple concept. Second is the equation of a circle in parametric form. For the same circle, which I have mentioned right now over here, for the same circle, if you write the equation in parametric form, we write it as x equal to h plus a cos theta and y is equal to k plus a sine theta. Here theta is a parameter. If you try to eliminate this parameter, you will end up getting the center radius form of the equation of the circle. Quickly moving on, this is all known to you. So I'm not going to spend too much time on it. Third is the general form. The general form of the equation of a circle, as we have already seen in case of a general second degree equation, a and b should be same. So what I did is I assumed them to be 1 or you say you can divide throughout with a or b. And this becomes the general form of the equation of a circle where the center of the circle is given as minus g minus f. And the radius is given as under root of g square plus f square minus c. So this is also known to you guys. No need to waste too much time on this. The fourth form is the diametrical form. Diametrical form of the equation of a circle. So whenever a circle is given to you, whose extremities of the diameter. So let's say this is the diameter. So let's say extremities of the diameter are given to us as x1, y1, and x2, y2. Then we write the equation of this circle as x minus x1, x minus x2 plus y minus y1 times y minus y2 equal to 0. So nothing hard and fast about this. This was all known to you. Fourth is the equation of a circle. Equation of a circle passing through, passing through three non-colinear points. Three non-colinear points. Very important, normally people tend to forget this. It is in the form of a determinant where the first of the determinant is x2 plus y2 plus xy1. Second row is x1, y1 square. Passing through three non-colinear points. So let the point be x1, y1, x2, y2, and x3, y3. x3, y3. So it will be a determinant given by x2 plus y2, xy1. x1 square plus y1 square, x1, y1, 1. x2 square plus y2 square, x2, y2, 1. And x3 square plus y3 square, x3, y3, 1. Now guys, how does this equation come about? This equation comes in a very simple way. So let the equation be x square plus y square plus 2g. So I'm going to prove this quickly. 2fy plus c equal to 0. Let this be the equation of the circle. And since it satisfies these three points, x1, y1. So x1, y1 will satisfy this equation. x2, y2 will also satisfy this condition. And x3, y3 will also satisfy this condition. Now, all I need to do is I need to eliminate gf and c from this equation. Now, again, treat these numbers as coefficients. Treat these numbers as coefficients of gf and c and 1. Treat them as coefficients. So these are all coefficients of g, f, and c, and 1. And the determinant formed by them should be equal to 0. So the determinant formed by all these coefficients should be 0 because your gf, c, et cetera, and 1 cannot be trivial. So treat this in light of a trivial solution of system of homogeneous equation. You directly get this expression. I would request you to remember this expression because it proves to save a lot of time. You cannot afford to sit and derive this in the examination hall. And it's very easy to use this formula. So these are the various forms of the equation of a circle. Now, we are moving to the next concept, intercepts made by the x and the y-axis. In fact, you can say intercept made on the axis is by a circle. So let's say there is a circle like this. And this is my y-axis and this is my x-axis. So basically, if I want to know how much intercept has been cut by this circle, let's say it's x square plus y square plus 2 gx plus 2 fy plus c equal to 0 on the x-axis. That means I need to know what is the length AB. Please note that AB is not the diameter. It is the intercept cut on the x-axis. So how can I find AB? Very simple. You'll say put y as 0. When you put y as 0, you get x square plus 2 gx plus c equal to 0. And we know that this point will be something like x1 comma 0. This point will be something like x2 comma 0. And what I need is mod of x1 minus x2. So how will I get that? Very simple. You know its roots are going to be x1 and x2. So x1 plus x2 will be minus 2g. x1 into x2 will be c. So we know the formula x1 minus x2 whole square is x1 plus x2 whole square minus 4x1 x2. That is going to be 4g square minus 4c. So x1 minus x2 mod will be under root of this, which is going to be 2 under root g square minus c. So remember this result. It's very, very helpful in many cases. However, you can also find it out by using the fact that you know the distance of the origin from the x-axis. That is nothing but the ordinate of the center and you know the radius. So you can always find this length and double it up. That's another way. But it's very important to understand or look at this concept from quadratic equation point of view as well. Similarly, the intercept cut on the y-axis. Let me call it as CD. Intercept cut on the y-axis will be 2 under root f square minus c. So please remember this result. CD is 2 under root f square minus c. And AB is 2 under root g square minus c. Please remember this result as well. Moving on, next concept is position of a point with respect to a circle. With respect to a circle. So if you have been given any circle, whose equation is x square plus y square plus 2 gx plus 2 fy plus c equal to 0, the first thing that I want to discuss over here, guys, this term henceforth would be referred to by the name s. s stands for second degree equation. So this is a second degree term. So I will represent this term by s. So this expression is x. This expression is called s. Now when I substitute, let's say I talk about this point, x1, y1 being inside the circle. Let's say it is at position a. When you substitute x1, y1 into in place of x and y, I would call that expression as s1. So if the point is located within the circle, that means in case where the point is at a, you would realize that your s1 would be negative. That is, the value of this term that would be obtained by substituting such a point which is within the circle would be a negative number. If it lies on the circle, that is your case b, of course, the point is going to satisfy the equation. So s1 is going to be 0. And if it is outside the circle, let's say at point c, so for case c, it would be greater than 0. By the way, s1 is called the power of the point with respect to the circle. We say power of a point, if it is negative, it the point lies within the circle. If the power of a point is equal to 0, it lies on the circle. And if power of the point is greater than 0, it lies outside the circle. And one important thing I wanted to discuss over here is that if the point actually lies outside the circle, let's say I take a small case over here. Let's say this is the point x1, y1. So when you draw a tangent from this line onto the circle, so let's say I call it as pt, then length of pt is going to be under root of s1. Please remember this. So if you square root the power of a point, you will end up getting the length of the tangent drawn from the external point onto the circle. And as you can clearly see, if the point is within, the length of the tangent will come out to be imaginary. And if the point is on the circle, it will come out to be 0. And if it is outside the circle, it will come out to be positive.


Hi everyone, I'm Joe and this is 2020 Prism Football Cellopak break number 3 with 8 Panini 1 football spots being given away. So we're going to do the break itself first as always and then we'll re-randomize your names with a different dice roll and those final 8 spots are going to be given away and the video itself for 1 will be in a separate video so look out for that. Big thank you to everyone here for digging deep and making this happen. I appreciate it. Let's roll it. Let's randomize it. 5 out of 5, hard 10, 1, 2, 3, 4, 5, 6, 7, 8, 9 and 10th and final time. After 10 we got Adam down to Evan, hard 10 for the teams, 1 and 10th and final time. I didn't think Dwight was going to be the one that was going to be thrown out though. I thought they would have been both teed up but Dwight must have been saying something else. There must have been something else involved. Alright, there's the first half of the list right here. Here's the next half of the list right over here. There must have been some extra words in this Sixer's Lakers game. Alright, let's sort by column B, let's just print and rip. So who's the marquee player in this basketball game? I guess Ben Simmons? Yeah, I think they'll sell soon. And then I always put the late night information in the break schedule as well. So we can always spy on that to see what the deal is. San Antonio Winfield, Rookie Silver, Red, White and Blue, Teddy Brusky, Matt Ryan and Rookie KJ Hamler. So the Antoine Winfield will go to Tampa Bay, that'll be for Chris, and the KJ Hamler going to my rivals, the Broncos, Nick Stober. Alright, now let's give away those spots. Joe Christian down to Ricardo and everybody in between. Let's roll it. Let's randomize it. Six and a three, nine times. So top eight after nine, you're going to be in the break. One, two, three, four, five, six, seven, eight and once more. Alright, yep, ninth and final time again. So from nine on down, my apologies, Ricardo, sorry, we'll get them next time, but I appreciate everybody giving this a shot. Congrats to, though, the top eight. You're happy because you're in the break. Congrats. Oh, Ricardo, there you go. So you're good. Adam, you're in. David, Robert, Ryan, Joe, Greg and Ryan, Ryan with a couple spots out of the eight. So congrats to you. We'll see you for the break in a separate video at JasperCaseBricks.com.


Hey, everyone. Thank you for attending. Today we're going to be covering comprehensive observability using deeply linked metrics and traces. So my name is Ryan Allen. I'm currently a software engineer at Chronosphere. At Chronosphere, we're building a hosted metrics and monitoring platform specifically designed for very large scale high throughput use cases. So kind of the core storage tier within our platform is actually the open source metrics engine M3 and M3 originated from Uber's original high throughput metrics use case. Before working at Chronosphere on metrics monitoring, I was working as working specifically on platform architecture at a company called Applied Predictive Technologies. So the agenda for kind of diving into deeply linked metrics and traces. First, we'll kind of cover just what the observability signals are in the landscape and also just, you know, for an engineer what their experience tends to look like when they get an alert, for example. Next, we'll actually dive into, you know, the journey of designing and implementing this deeply linked metrics and tracing metrics and traces feature. And then lastly, we'll talk about kind of a future where once deeply linked metrics and traces are actually widely available, how that dramatically can improve the engineer on call experience by, you know, providing us the ability to build features such as jumping directly from an alert in an email or a pager duty, for example, to a request comparison where we're able to immediately diagnose what is the difference between, you know, a successful request versus an unsuccessful and identify the root cause of an issue. So first to start, we'll just cover kind of the three primary observability signals that people leverage these days. The first is metrics. So metrics are usually kind of the first signal an engineer gets when something goes wrong and metrics under the hood are just essentially many different time series that we track over time. And can then, you know, set thresholds on to alert off of or just track trends over time and kind of get that very high level, less granular but but more expansive view of an overall platform. So kind of the characteristics of metrics are first, they're very, very structured. So whenever you're emitting a metric, you're specifically emitting that metric with a particular name as well as a, you know, finite specific set of tags associated with that. And then all of those combinations of name and tag values, ultimately represent kind of a single trend line that you could graph over time. And now, as a result of being very structured, they're very fast and efficient to aggregate both that, you know, the query time so when you're actually querying it from an alert or from a graph, and as well as collection time so, you know, as a result. It means that you can really run many, many queries within short periods of time, and it's not really going to result in performance issues and the same is true for collection time so it's very easy to just, you know, admit many different metrics from a single service and you know collect them with like a local thing. They're also as a result of being very structured, very efficient to store so you know when you're storing just information that you know is you know some value associated with some time. It's very, it's very easy to more efficiently store that in some storage tier or on disk, then let's say some arbitrary kind of blob of data. Now, all of those are really great pros to metrics but you know the downside to this very structured nature obviously is that it doesn't have kind of any arbitrary information that you might want and might be very vital in diagnosing a problem and so it lacks kind of that granular per event that you could need when diagnosing something so an example of that type of information could be you know, like the exact HTTP request response for a single request that happened to, you know, occur in your platform. And so as a result of, you know, these characteristics metrics are really best for that high level observability and initial kind of alerting of what's going on, and then kind of going into more detailed root causing requires using some other observability signal. So, that's kind of where logs come in so logs are on the other side of the spectrum, and these are, you know, this is kind of the observability signal that that is as old as time, and it just involves kind of dumping any arbitrary information out that you can then reference later. Now, the characteristics of logs are generally very unstructured. Obviously, you know, there are a lot of libraries and tools these days that help make it easier for engineers to be more structured in their logging so that they're easier to search for and more efficient to search for. However, because of the inherent nature of logs containing really any arbitrary information, they're intrinsically slower and less efficient to activate. And then additionally, they're less efficient to store since you can't kind of make specific assumptions about what that particular log looks like when you're ultimately storing that data somewhere. Those are kind of like the performance and operational downsides to just storing any and all arbitrary information, but then obviously the huge pro and why logs are essential is that they do have this per event detail preserved so that you should, as an engineer, be able to find any information that was relevant to any particular event that occurred within the platform. And so, as a result, they're kind of the best tool for, you know, actually getting into the weeds and diagnosing a particular problem. Now traces are what well metrics and logs are kind of, you know, the two signals that are as old as time traces are a more recent observability signal that has become very popular with the advent of micro service architectures and just platform is becoming more and more complicated.  So you can see here how it will be able to essentially tie together specific types of logs kind of like entering and exiting specific services and giving you an understanding of how much time is being spent within a particular step within a particular service. And so it's easier to be able to then kind of diagnose where within your more complex architecture a particular issue is happening. So, again, you know they provide the transparency into this execution flow which is really vital in micro service oriented architectures. They're kind of in between metrics and logs in their, in their kind of nature of data. So they're very structured in so far as all of the particular kind of steps within a trace need to be ultimately tied together by kind of a request ID. And so that's a very kind of structured piece of information that flows throughout a given trace. Though they're also unstructured in that many of the libraries which admit traces allow you to kind of store arbitrary data as well. And so in that regard they're unstructured. As a result of kind of them being in this in between, you know, level they're not nearly as efficient to store and query and things like this as metrics. And so as a result. of the quantities that are doing tracing at kind of large volume. They have to actually sample down the total number of traces and you can do this intelligently and try to say, Okay, here all the kind of distinct combinations of values of data associated with my trace and let's try to have particular time periods to store at least one of that distinct set so that we have kind of a representative sample. That being said, there, there are still kind of limitations to how one can go about the sampling and so sampling is you know one of one of the kind of biggest challenges to comprehensively supporting traces within your platform. Next we'll talk about kind of what the average experience is for an engineer when they get an alert. So let's say, you know, you're on call, you get an email alert, and in that alert you see oh request latency is high, and then typically, you know with it embedded within that alert you'll have some sort of link to kind of the, the source of the alert which often would be let's say a graph that points to the specific metric that that triggered the alert. So let's say you know we jump to our email we click the link to Grafana. Now we're on kind of a dashboard that is associated with that alert. We have to kind of parse and say all right which of these graphs has the metric that we care about oh okay it's the bottom left it's request latency. So let's go into this. Here we can see that there's kind of a divergence between the time that's that that these requests are taking. And then we can also see kind of the particular splits in time series tag values at the bottom so we can see okay, kind of the information about these two particular trend lines is that they're coming from the customer get endpoints. They're coming from the same Docker internal hosts. It's coming from a hot rod job, and kind of where they're diverging is it is in kind of like which histogram bucket they fell into in terms of total latency. So from there, we could say all right well things are slower on one path versus another another but from this information it's not clear why that would be. And so now we kind of have to jump to some new signal to try to figure out what the root causes. So that's where you know you would then jump to something like a trace or a log. It would be really useful here because what we really want to understand is like what's the difference between kind of the request that are running slowly versus the requests that are running faster. So, usually what you can then do is you can jump to let's say kind of an open source trace visualizer like Jaeger. So we go to kind of the search function there, and then we try to narrow our search to try to find one of the try to trace that represents, you know, one of the requests that actually fell into this longer request latency time bucket.  And then as a result we get kind of some subset of traces that match those parameters. So now, let's say we click into one of those traces that we found.  It's not totally clear from this particular trace in isolation what the difference is between this and kind of a good one. Okay, yeah, it looks like you know, there's some time trying to talk to Redis but that fails and so then it talks to my sequel which takes a pretty decent amount of time and then there are a few other kind of validate customer steps at the end. But it's not so clear like it what is the ultimate root cause here for why this is slower than let's say some other case. So usually then what you'd want to do is you'd actually want to find. Go back to kind of the search functionality of the trace and then change that latency to be kind of the faster version so then find a sample of a trace that actually represents, you know, the good case versus the bad. So then we'd say, okay, here's actually a trace that is, you know, faster than the other. So we see, okay, interesting. It looks like the Redis case here actually succeeded and then there is no my sequel step which is, you know, the slower case here and obviously you can manually like do this diff mentally. However, Jaeger actually has a cool feature in which you can actually compare two specific traces and visualize the specific kind of step differences between them in the same way that you would do a diff in code. So let's say we kind of grab those two different trace IDs, we use the compare functionality, and then now we can actually very easily identify, hey, the difference between the request that takes a long time versus the request that doesn't is that the request that takes a long time actually has this one additional mySQL step. And so now we know, you know, with very strong evidence that the kind of root cause of why this particular set of requests are taking longer than the others is there's something specifically wrong with mySQL or maybe it's just that mySQL is slower in this case, because we're not hitting like the Redis cache. So now we can actually say, okay, well if we want to actually improve this, then the way in which we would do it is by specifically targeting, you know, the mySQL step. So that's kind of like the flow, for example, of what an engineer would do when they get that first alert of a latency metric being divergent in a bad way from kind of the norm. So the question would be, could we actually kind of skip all of those steps in between where we're doing manual searching and manual comparing and things like this, and instead be able to just give you that direct link immediately so that the on call engineer can just click one link and jump into depth. And essentially, the way we can actually go about achieving an experience like that is with something like deep linking metrics and traces, and the idea here at a high level is to say, instead of having kind of metrics be this one that is causing the alert, but that's it. And then traces being this other thing that gives us more contextual information. Could we actually kind of tightly couple them together in the same way that you would tightly couple kind of like two pieces of data, or two tables together with a foreign key. So we can kind of make these actually natively compatible so that we can actually jump straight from kind of a metric data point to the trace that would be associated with that particular data point. So, generally, kind of, as we saw in the example where we were searching Yeager for a trace that looked like the parameters associated with the particular metric. So these are linked is is not really kind of this, you know, tight coupling but rather a loose link by convention, which, which is to say, it is just convention that the way to set up your metrics is to make sure that the tags actually are similar to the tags that you include on traces that when you do ultimately do that manual search step, you can actually kind of properly narrow down your search. So, again, it's important that these tags are similar, so that you can actually jump to this search step and make sure that you're kind of able to consistently tie metrics to traces. However, there's no kind of like enforcement of this and this is not kind of like a native or tight coupling of this information together. So what would be great is if we could actually add this kind of more foreign key relationship or native type coupling, and the way we could do that, for example, would be to make sure that every single data point that you see on some sort of time series for a metric has a span ID directly associated and if we did live in a world where that was so then you would be able to, for example, you know, click a particular data point on a graph and then jump to the particular trace immediately from there. Now, the question is how can we, you know, go about making that a reality. So, one of the first steps to doing this is to actually kind of think about how we can include this information and propagate it in a way that allows us to consume it properly. Now, open metrics is kind of the standard for how metrics are admitted and how they're kind of represented to whatever is collecting them and then shipping them off to some, you know, some tool like Prometheus. Now, one of the aspects of open metrics is that it has this concept of an exemplar which is essentially kind of a comment string that you can append to the metric values as they're being admitted so you can see here. That HTTP request total for search for status code 200, the value is 1725 and following that, you know, following that hashtag symbol, we can then kind of include arbitrary data with this same protocol that we can then consume on some other side. One way where we can propagate, you know, for example, trace information alongside metrics information would be by leveraging this exemplar. And so one of the changes that we've made to kind of make this happen is by including a trace ID with every single kind of emitting of a metric value embedded within that particular exemplar in open metrics. And now kind of a next step would be to say, okay, well, now the protocol supports being able to expose trace IDs with metric values. How do we actually, you know, admit that from code now open telemetry is an instrumentation SDK, so that you can kind of instrument your applications via code to emit both metrics and traces. And by modifying kind of this common library, we can make it so that it actually abides by that, you know, that that use of exemplars so that when we are actually exposing metric values, or including whatever contextual span ID is associated with the context of that request. By modifying this library, we're actually now able to make sure that when we admit it, we're including trace IDs as exemplars in code. Now, a third step here is to then actually kind of properly now consume that exemplar that includes the trace ID, right, so it's like our code is using open telemetry to write out that trace ID in the exemplar. The open metrics protocol supports the fact that we can include this metadata in the metric kind of emitting structure as an exemplar. Now kind of on the Prometheus or M3 side, we need to actually be able to kind of consume that additional metadata. So, on the Prometheus side, we just modify kind of the scraping endpoint to make sure that it's including these exemplars along with the values, when it's actually scraping the data. And then kind of after making sure that we're scraping it properly, then the next step is making sure that we're actually storing that data properly as well. So kind of an additional step that we've added is having M3 store these exemplars alongside every single data point. So, you know, we're now getting a data point scraped from Prometheus or scraped as Prometheus protocol, and then M3, let's say, now has that metric value in addition to the exemplar. And instead of just storing the data point as we normally would, we store the data point and then right beside it, we also store that exemplar metadata. Kind of then the last step is after we now have kind of this metadata persisted in M3, the question is how do we retrieve it properly. And so then kind of a final kind of implementation piece here is to modify M3 query to actually read out that information so that when we're reading out the data point values, we're also including with that result, you know, the associated span ID for every single data point that we return. One other kind of nuance here that's important is that when we're reading out these exemplars with data points, M3 query also has to perform, you know, common aggregations for the queries that it runs. So, you know, some or max or average, or, you know, more complex operations, it's important that as we're kind of rolling up results, we're keeping those exemplars with the results as we're rolling them up. Now, we spoke earlier a little bit about sampling and how that's very kind of, that's very much one of the biggest challenges with tracing. Now, kind of one of the reasons why sampling techniques are really insufficient for ensuring that you have 100% always correct representative traces compared to your metrics is, you know, let's say you're doing some sort of head based sampling technique where you're trying to choose at the start which of the traces you want to keep based off of have the distinct combinations of tag values associated with that trace. The problem here is you potentially miss cases where you actually need to know information about that trace that occurs actually at the end like request latency. So at the time of like choosing which of these traces you want, you don't know whether or not that trace ultimately will fall into kind of the histogram bucket of, you know, the longest time versus the shortest time. So this is for this endpoint and for this status code, etc. And so one of the, you know, kind of gaps in the in common sampling text techniques is that we really have to kind of roll the dice in certain cases to to try to get this representative sample, when ideally we would want to just be able to have 100% certainty that all of the traces that we're storing are truly fully representative of all the of the particular kind of metric combinations that we have. And so I guess I skipped over this but the kind of the way that deeply linking metrics and traces actually solves this problem is, and we'll talk about the architecture here in a bit. And essentially, because we're storing trace IDs along with data points, we can use that tight coupling to essentially tell the trace storage tier just store these specific traces, and the reason you should store just these ones is because the trace stores that we're including in our metrics persistent store. So then, as long as kind of the coordination of what to store is synchronized both between the metric side and the trace side, then we can always be 100% sure that the trace IDs that are stored with metrics are also actually stored in the trace storage itself. So kind of we talked about all these different pieces. Now let's actually try to like walk through the flow of how they all work together. So first, on the left most side, let's say we have this app that is going to be emitting both metrics and traces. Now, within that app, you know, we're going to be using open telemetry, which is the library. And we, you know, emit both the traces and metrics. And so that's kind of the library that's making sure that trace IDs are going to be included as exemplars with metric values that get emitted. So then if we take this top half and walk through kind of the metrics flow. Open metrics is emitting those metrics with exemplars abiding by the open metric standard, which is to say this particular kind of protocol format, which includes being able to append arbitrary metadata information as exemplars. So open telemetry is exposing that trace ID as an exemplar. Next, we have Prometheus actually scrape that data, which includes kind of the metric value as well as the exemplar from that application. Next, it actually then forwards that right to the M3 aggregation tier, which is in charge of then actually persisting that to M3DB, which is the long term storage node for it. So kind of Prometheus again, gets the metric value has the exemplar, it gets to the M3 aggregator, the M3 aggregator then like actually writes out that data point with the exemplar to disk, and that that's ultimately done then in M3DB. Now, now let's talk about kind of the tracing flow here. So in addition to open telemetry exposing metrics to the Prometheus scraping, we also have kind of a Jaeger collector that is reading the traces that are being emitted from our application. Now, kind of the last piece of the puzzle here to solve this sampling problem and ensure that we are actually always storing the trace IDs that we ultimately are including as, you know, values, or as traces for each data point of a metric on the metric side.  So essentially what happens here is we just keep all 100% of the traces in memory here but for a short period of time so that we can essentially just sit here and wait for the M3 aggregator to signal to us which of these span IDs we actually do want to persist. So instead of just arbitrarily sampling kind of some subset of spans, which then might not actually be, you know, the ones that we're storing on the metric side, or, you know, in a traditional tracing case might not be a representative sample that we want. What we can do is we can actually just keep them in this holding tier and wait for the aggregation tier to say, hey, definitely stored this particular span ID because I just persisted it alongside this particular time series data point. And so by doing this, it ensures that on the metric side we're selecting a representative representative sample because every single time series itself is, you know, one of the proper unique combinations of values including things like histograms. And then on the trace side, we actually can then only store those specific subsets of traces that we ultimately are persisting there. And we can also, you know, include more than just that subset but this allows us to get at least the 100% coverage comprehensive, you know, sample of traces for every metric data point we would care about. And then kind of lastly, you know, once this data is stored both in M3 as well as Yeager, we can now kind of read out, you know, metric values but then know this metric value is associated with this trace ID so we can create kind of a contextual link between, you know, let's say, Grafana and Yeager. Again, this is kind of a visualization of what that would look like. So let's say, you know, we're reading data from M3, we're viewing the M3 query results on a graph, but because M3 query can read out the exemplar which includes the trace ID. We can actually leverage a Grafana feature where you can add kind of per data point annotation functionality to launch from a particular data point to a link. We can actually add to that the ability to just create a link that links from Grafana to Yeager using that particular span ID. So that is kind of the whole architecture change with all of these different open source projects to kind of build out that deeply linked metrics and traces. Now kind of we're going to talk about what this feature actually looks like by leveraging that, you know, that implementation that we just discussed and specifically how that empowers us to be able to create an experience in which an engineer can get an alert and then directly jump to a request comparison. Cool. So I'll now jump to a demo. So first, I'll just describe kind of what we have running locally. So we're running this hot rod server, which is essentially just simulating a bunch of metrics and traces that we can use as examples. And it's kind of functioning as a test kind of car or our ride sharing service. We're also running Grafana that is visualizing a few of the metrics that are being emitted. We're running Yeager, which we'll see in a second.  So, you know, normally let's say you have an alert that looks like this where we have an error, or we have an alert on the metric total customer requests and specifically for, you know, 500 error requests. So kind of the traditional flow here would be that you could click a Grafana link. Now we can see kind of, you know, the metric over time or within this time range that is associated with that alert. We can see these ones are 200s. These ones are 500s. But again, the next step would have to be doing this kind of manual searching through Yeager. But instead of that, we can actually directly link because we have the exemplars to either the trace itself, or even better, kind of a trace diff that says, here's the difference between the 500 case versus, you know, a generic 200 case. And so, for example, in this, you know, 500 versus 200 case, we can see, Oh, okay, the trace looks exactly the same up until these last three customer steps. And what that means is, you know, the 500 case actually stopped short of doing these last three cases. And so my SQL must be the root cause of this problem. It must have failed ultimately in my SQL. And we can actually, you know, click the trace and then actually see, okay, yes, it does look like this trace came down up to my SQL and ultimately fail. So that is kind of how, with all of that, like under the hood, you know, with the span IDs being emitted with the, with the specific metric values, it allows us to kind of build this, you know, alert experience, which can just immediately generate a useful kind of diff between kind of the error case trace and the normal case trace. And the other kind of cool thing that we can show here is how we embed these particular traces on the specific data point so I can click here, or here and I can either jump directly to the trace here, or I could, you know, click here and jump to the particular diff associated with with that trace, or with that metric data point rather. So that's kind of a demo of like that whole architecture running locally that we just described. Now, again, like how is that working so, you know, open telemetry and open metrics are exposing span IDs as exemplars, Prometheus is scraping them. Prometheus is empowering us to actually read and write those exemplars so whenever we're storing a data point or reading a data point, we're also in, we're also storing that exemplar or also reading that exemplar. And then lastly, you know, we can just leverage kind of Grafana features to make sure that links include those span IDs and jump you to kind of the Yeager that's running nearby. So that will just kind of what the result now looks like when we have not just kind of a value, a set of values for a particular kind of metric that we're returning but also it includes kind of the span ID and trace ID. One question might be, oh, what are some other kind of cool features can we build here so kind of some some ideas would be, for example, being able to on the UI select, hey, here's a data point that I want to compare to this data point. So you can kind of essentially say, I want to, you know, from here, not just have an auto generated diff based off of, you know, 200 versus 500, I actually want to like manually specify which two data points I want to be comparing kind of the way to build these kind of concept contextual links and integrations really can just be based off of, you know, how we think about metrics.  So an example would be whenever, you know, request latency is in this bucket then use the fast, like whenever it's in the slow bucket then use the fast bucket as the comparison, or whenever we're looking at, you know, RPC requests, we can say whenever there is an error case use the success case as the control. We can even actually kind of, for like really commonly exposed metrics like RPC metrics, we can actually probably just build plugins themselves that us that that know what these metric names are and what the like various combinations are, so you can kind of just get them automatically generated for free as opposed to as opposed to having to kind of manually set them yourself. So cool, that's kind of a summary of the whole architecture flow of, you know, natively tethering together metrics and traces and as you can see it really is a powerful tool to cutting out a lot of the manual labor in between, you know, getting an alert on a metric and actually finding some relevant trace and understanding what is different between that trace and some other, you know, control trace. So the demo we just showed is actually publicly available for folks to run at home. You can jump to it from this link, you just have to clone the repo there's a read me that describes how to do it. So all of the various pieces that we were describing are kind of in different states so a few of the PRs have been merged so the one that's actually adding the support for this exemplar metadata to open metrics has been merged. Also, the exemplar support for the Prometheus client library for exposing that exemplar has been merged. There are some other ones that are in flight so we're hoping to, you know, work with people in the communities to get all of that over the line. And then lastly, here's kind of all the links to the various open source projects that that we use to build all this so open metrics open telemetry Prometheus M3 and Grafana. Also, there's another video of the CTO at my company Chronosphere Rob Scalington talking about kind of some of the more interesting implementation details of how we've linked metrics and traces as well. So thank you for attending and hopefully I can meet all of you during Q&A and answer your questions. So thanks a lot.


We gather here to celebrate people in Australia coming together and being as one. I acknowledge in the past and the things that have happened, but also moving forward to the future. We at the Gamori unit in conjunction with Griffith University hold this on the Gold Coast and Nathan Camp is at each year. Gamori! The crowd's swelling so we're happy with the turnout. It means a lot to the whole university community. We've got the vast chance that they're here with our senior staff. The thing that I'm really pleased about this year, we've invited students to join us as well to celebrate and commit to reconciliation. I'm here to sort of be part of this big group today and just really show the line and show the support for reconciliation. We've had 300 registered for the Walk and Talk. That's the biggest since the Walk and Talk commenced five years ago, so that just shows the impact of how important that conversation around reconciliation is to our students. It's great to walk with people from the broader university community. It's really important to stand up for what you believe in.


All right. Thank you so much Dan for playing the video. Seems like we have a question or two in the Q&A box and I think you've started answering them, but I would like to basically just voice it out and maybe you can answer it live for the rest of the audience. So David asks, we are using the lab 11.5 EE, we expect features to work with this version. And I think the answer to the quick answers, yes. And Dan basically elaborated it in the Q&A box. But then David asked again to clarify that he is the platform owner. Can he change the default pipeline that is automatically created for his users? For example, can the security add or change a scan and add it to the template? Okay. So you're talking, right. So you're talking about the, on your own instance, changing the default auto DevOps pipeline. I don't believe that that capability is in place today. I'd have to go validate, but I'm pretty sure that right now it runs an internally defined pipeline that is that template that you can see if you look at the new file templates, but I don't think that is customizable at this point. All right. Thanks Dan. And then Alexi asked a question, which I think the first one I can answer pretty quickly myself. So is this video available somewhere? Answers yes. We actually will send a pre-recorded demo and the Q&A session today in the follow up email to all attendees and registrants. So you will be getting a copy of that. And then Alexi also asked, it can be, oh, okay, actually. He actually has an answer here. And he would like pricing. Oh, he's asking if pricing is negotiable for 200 plus members. Not sure if this is a Dan question or more sales team. I'll let you take it Dan. Better asked of the sales team. Yeah. Cool. All right. So any other questions from the audience? Otherwise, maybe we can go through. Yeah, if you don't mind, there's a question that David asked first, which I'll, I'll just reiterate the dance around so that the follow on question was is what I guess what David you were meaning was was the default pipeline customizable, but I just want to reiterate that you can take the auto DevOps pipeline that that is reconfigured by us and you can create your own, you can use it as a template to create your own CIML, get CIML file and then customize it from there. What we're missing and it haven't gotten to yet, I guess is the setting it as the default for the whole instance. But looks like Alexi found a way to do that. But through the main normal UI you can't and but but you can make a copy of the of the auto DevOps pipeline and customize it. You can also create your own entirely different pipeline and use components from the auto DevOps pipeline. Cool. Alexi has another question Dan for you. Is there a way to expand UI via some form of JavaScript plugins integration? Yeah, so we do have we do have integrations. But a you're talking about doing your own JavaScript UI changes to the to the UI. It is all open source so you you. I'm sure you can I don't we don't have a framework in place to support that at this point. But again it is it is all open you can see everything. That is that makes up both the CE and the version and hook in what you need to there. But again, yeah, we don't have a plugin framework for UI changes at this point. So seems like that is it in terms of questions from the audience. Maybe we'll share one more question that we often see come up and then we can wrap up the call about that then. All right, so Dan. I think a lot of people are curious. If we can connect to any Kubernetes cluster or only once we're integrated to. Yes, we can. We have a tight integration currently with with Google's GKE cluster in that you can use your login to connect in and use the UI to configure the whole thing. However, right next to that is the ability to connect to any standard Kubernetes cluster using the standard API. And that there's also you buy for configuring that and what you do it's all managed in the background the same way. So yeah, you can connect to anything. Again, any, any, I shouldn't say anything, any Kubernetes cluster that is using standard API. Great. Thank you, Dan. And I think Alexi has another question so and also and he at his own integration, for example, modified basic your integration with something a little more sophisticated. Yes, you can as a matter of fact we encourage you to contribute it back so that everyone else can benefit from it as well. We'd love to get contributions and and we have a team that will look at contributions every every release and pull in pull them in to to the main code base and then we maintain it from there. So, no guarantees that everything that's contributed will make it but but you can absolutely add your own integrations on top of the code that's there. And we'd love to hear more from you about if you made a correction or made something better than what we have out there we'd love to to share that through plug, I'm sorry, through contribution, other the JIRA itself is a plugin. So I guess it would be a contribution to the plugin. You're not having so you're having trouble Alexi is having trouble with a merge request. It sounds like something we want to work with you offline on, you should be able to if you're on gitlab.com working with the code base you should be able to open merge request on either of the code bases. So if it's not working there's something else going on we need to resolve. We can take that offline. If Alexi maybe we can just hang out after we're done here and get your contact information. I think we have the contact I'll send it to you then. Okay, great. From registration and. Alright, so if there is no other question and I guess we can wrap up, giving maybe another minute if there's anyone that's itching to ask any more questions and then not move on. Alright, thanks for seems like Alexi is submitting a merge request. Thank you for that. So thank you for the questions everyone and then for answering the questions so this demo is something new that we're trying so love to hear what your thoughts are on today's session, and would really appreciate your responses to our survey, which I'll drop in the chat. I'd also like to invite everyone to sign up for a free trial of gitlab ultimate. If you haven't already, I'll chat that link as well. And finally, if you have any other questions, don't hesitate to reach us via our sales contact page about dot gitlab.com slash sales. Thank you. That's all for today. Thanks for joining us.


So, I'm Senior Technical Product Manager at VMware and I will talk about this one here, VMware, these integrated containers, VK, PKS and open source stuff. So integrated containers, what's that? It consists basically of three pieces. One is the web interface, it's the harbor registry, and the so-called VIG engine. And what's the VIG engine? It gives the user, which in that case is using Docker, the illusion of a big Linux system. You create a vSphere resource pool by a command, it's called vik machine create, and you get this pool, so to say, and you can talk to an API endpoint and actually shoot Docker commands against it. The good thing about this, it's one container in one virtual machine, so the vSphere admin actually sees the containers, can do micro segmentation with NSX, even billing everything which works with virtual machines can be done with containers. But it's not an orchestration engine, right, it's just for running containers, actually quite useful for stateful services, things like that. In the cloud, you see that also from Microsoft, from others doing the same thing, we actually did that three years ago already. The registry, which is part of it, has image scanning, image signing. You also can replicate registries between different, you can replicate images between registries, sorry. So that was the first one. The second one is about Pivotal container service, which is a collaboration of VMware, Pivotal, and also Google at some places. And as you see at the bottom left, you have that one running on vSphere with all the integration I talked about yesterday, NSXT, vSARN, vSphere integration. You can also run it in the cloud, but you still manage it on your own, right, because on AWS, on Google Cloud Platform and soon also on Azure, but you run it and manage it on your own. That's the difference, right. You consume infrastructure, don't build it yourself, but you still operate Kubernetes on your own. I mean, using a framework like PKS. What they use, of course, I told that yesterday, it's Bosch basically, using the Kubo or CFCR project, spinning up Kubernetes cluster, managing them, doing life cycle management, updating, fixing stuff, things like that. So it can spin up very easily multiple clusters. The third one is the fully managed system. It's a SaaS offering. You might ask, why do you need that? I mean, there is, for each cloud provider, there are these kinds of offerings. It's something which will run on every place the same, right. We just use the cloud environment, but we run it the same. It has some integration with the services, as we have seen before in the IBM cloud. You can have it integrated with AWS services if you run it on AWS, if you run it on other clouds, you have another integration. And actually, you see at the bottom, VKE cluster create, that's how you create a cluster. With Wicked was big machine create, a virtual container host, which is resource pool, and then Docker run. Last thing, it has a concept of smart cluster. That's actually quite interesting. Also policy framework. Smart clusters mean when you spin up a VKE cluster, it has no worker nodes running yet. As soon as you do a Qt control, run something, or apply something, or help install, we will actually spin up a node in the background as soon as you need them, and also delete them again if you don't use any resources anymore. So it's kind of out of scaling in an automatic fashion. That's a smart cluster framework. The policy framework is actually pretty interesting. Last slide. You also have a lot of open source projects, I mean, used in a lot of places. If you use, for example, on Linux, OpenVswitch, which was a solution for me, Xera, they became NSX later on. That's a project which is now part of the Linux foundation, but you see there is much more stuff. This mini Linux photo OS, which we use for the recent server, clarity is actually the HTML5 UI framework to create our own websites, everything. Harbor, Lyotis, Internet of Things framework, and a lot more, right? Maybe the last one I want to mention is Hatchway, which is storage for Docker and Kubernetes cluster, where you can use Visa policies to attach to POT, which is very interesting. So you have more IO, more bandwidth for each POT, and the dispatch project is kind of an enterprise umbrella around some function-as-a-service frameworks. And I am a little bit ashamed, but I forgot to put open files on the slide. That should also be there. Actually, the developer is now working for VMware. That's it. I stayed with my five minutes. Is there the next speaker already here, or is that the end? That seems to be the end. Thank you.


In my role as parliamentary representative for Castery's South-East constituency and minister in the Ministry of Equity, Social Justice and Empowerment, I have experienced many successes as well as challenges. It would be remiss of me if I did not take this opportunity as we bring 2023 to a close to place on record my profound appreciation and gratitude for those who have contributed to both of these in one way or the other. I say thanks for both the successes and the challenges because my successes have taught me to repeat the actions that brought success and my challenges taught me to revamp, revisit and review, in other words, to will and come again. Firstly, I want to thank the constituency council and the constituents of Castery's South-East for their continued support and understanding since I assumed the role of their parliamentary representative. Serving is enjoyable, but not always easy, especially when you would like to meet the needs of everyone. Yet there are limited resources to meet the demands and often times as parliamentary representative I find myself with headache and heartache of deciding who needs the help first and most. It is a daunting task, but in many cases my constituents who request I have had to delay understand my predicament and for that I am very grateful. I want to assure them that I have the best interests at heart and will do all I can to address the needs in due course. Also, my ministry's mandate is a very important one because we are responsible for the plight of many underprivileged persons in society among other work and I truly believe that we have made great strides in addressing the needs of that community. This would not have been possible without the support and commitment of the employees of my ministry and I seize this opportunity to express my appreciation to all managers and line staff of the Ministry of Equity, Social Justice and Empowerment. I want to recognize the support staff of my ministry as well as the heads and staff of various agencies under my ministry for catching the vision and working towards accomplishing it. My dear administrative assistant, Ms. Tenj, my attache, Mrs. Andrew, for keeping me organized and of course my dedicated driver.com for leading me in the right direction, literally. I want to wish my cabinet colleagues, the staff of my ministry, my constituency and all sentlosions a Merry Christmas and a Happy New Year as we look forward to brighter seasons. God bless us all. Thank you.


Welcome to Toffy TV. It is the Everton News Daily. This video is sponsored by Unibet. For more transfer stories, get over and check out the Unibet blog page. There's lots of updated transfer stories on there. The link is in the description. Fabian Delth is set to become an Everton player. He's apparently joined up with Everton in Switzerland as they move near completion. A 29-year-old midfield player from Manchester City ready to sign for Marco Silva and become Everton's third signing of the summer. Delth experienced winning the Premier League two years on the run with Manchester City, being there for four seasons, played over 90 games for Manchester City. He's a player who plays in a Pep Guard, the older side, then for me it's a really good sign. He brings leadership qualities, a wealth of experience to Marco Silva's young team. We don't know whether or not Delth's going to be guaranteed a start in Everton's team, but what he does is he covers in lots of positions as well, can play sentiment for fear, left back and even cover at right back if need be. But a good signing for Everton and like you say, Marco Silva's third summer signing. Everton, who drew nil nil yesterday with FC Seon in pre-season, are ready to face Monaco on Friday. Delth may be involved in that, but we saw 45-minute action for the likes of Luca Dean, Bernard, Guilfee Sigarton, Michael Keane, Joven Pickford, Seamus Coleman, so Everton will step up their work ahead of that clash on Friday, like you say, against Monaco in Switzerland. In the Afghan yesterday, Nigeria were knocked out, Henry on Ykuroo actually got on the pitch, came on as a 78th minute substitute, but Nigeria were beaten, but Ghana and his Senegal team made it through to the final. They won 1-nil and will play in Sunday's final. It means that Ghana probably won't return to pre-season training until the first week in August, he'll be given some time off after the half combo. Big congratulations to Ghana for getting through there. Further transfer news out of the club, Anthony Robinson has apparently moved closer to his move to Wigan Athletic. They offered £2 million for the USA international left back, looks as though Robinson's time is up with Everton. He played last week against Carriabangi Sharks for the Blues having spent the season on loan at Wigan and they've managed Paul Cook wanting to take him to Wigan permanently and they've offered £2 million, which is apparently being accepted by Everton and Mo Bezit being heavily linked with a move to Fulham over the weekend. That still hasn't quite progressed at the moment, but it looks as though Mo Bezit on his way out of Everton as well. Finally, Kate Zuma has gone to Japan with Chelsea for their pre-season tour. Obviously a lot of Evertonians are a little bit concerned about the Zuma situation, but he is a Chelsea player and therefore will go and play on tour for them in Japan. We'll have to wait and see whether or not anything develops with Zuma. He's out there in Japan with Chelsea. Let's hope Everton can get a deal sorted with him fairly quickly and make him a permanent Everton player. If you haven't subscribed, please do so, but it only takes a second. If you want more videos, get over and join us on Patreon. See you later.