What's going on everybody? This is Giovanni from spy options trading. We're done with the holidays everybody I hope everybody had an awesome time with friends family loved ones I know I did but also I was extremely busy During the holidays in the property management world. It was the busiest time of the year So I was extremely busy. I hardly got an opportunity to actually watch the markets live From time to time I would sneak in and and and and sort of just see the market action and whatnot But I had no time to actually watch the markets live until today. I didn't place a trade today So instead of you know, just showing you a boring trading day where I didn't place a trade I thought I would talk to you about an indicator that I came across that is The most intriguing indicator I've ever came across it's intriguing because It's the most objective Indicator I've ever seen by objective. I mean It's the same and it doesn't matter whether you're looking at the daily charts the 15 minute 30 minute 10 minute 5 minute all the way down to the one minute chart It's all the same what I mean by that is on the one minute chart It could be a value of say just one and it's one regardless if it's you're looking at the five minute ten minute hour Daily, it's the strangest indicator. I've ever seen along with being the strangest indicator. I've ever seen I have Researched it and I can't seem to come across a good explanation for what it is. I I don't know I don't know what it is and Mainly because it is so objective and because there's not much information out there That leads me to believe that I should look more into it The indicator that I'm talking about is the implied volatility indicator and when I mean by that is I'm not talking about implied volatility Dealing with options directly. I'm talking about implied volatility the Indicator you can find it on thinkorswim. It's you can look it up under. I am P for implied volatility I am P volatility you it's a lower indicator below the chart much like you would see the MAC DR sideline stuff like that, but It's so weird nobody seems to understand Exactly how it's calculated You can find formulas as to how implied volatility is Calculated but as the indicator I can't find any information about it. It's so strange and Also, it's strange because it doesn't matter whether Price is moving up or down that indicator will move up or down I don't get it. I don't I can't seem to understand how it's working much like the let's just say the Sarcastic's indicator. It's a momentum Indicator using past history. It'll take let's say the last 14 candles and It'll give you an indication as to In relation to those last 14 candles where price is whether it's trading in the upper part of the 14 last 14 candles or the lower part or or in the middle implied volatility isn't like that It's strange. I can't even begin to explain to you how fascinated I am by this one indicator And it just leads me to believe that I need to really look deeper into this indicator Incorporate into my day to my day trading. I think That it's sort of justifying the price movements. I think I don't know exactly What I mean by that in a nutshell. I think that I mean that when the price is moving up Is there enough volume to justify that move up and then vice versa when the price is moving down? Is there Volume justifying that move down. That's the best thing I've been able to come up with in the last month or so Maybe a little bit longer since I've actually come across this indicator And I've held it for so long because I just I don't I don't understand it And I've been trying to do some research into how it works how I can use it to my benefit when day trading. I Can't find it anywhere. I've googled it many many times Maybe I'm overlooking it. Maybe I'm just thinking too hard and maybe it's just right there So if anybody has any information about this implied volatility indicator, I'm I'm literally talking there's a difference there implied volatility as You know when we talk about options trading directly It makes sense and I'm able to find tons and tons of tons of information about implied volatility when it comes to pricing options and Options trading but implied volatility as an indicator when we're looking at stocks or ETFs underlying securities. I Can't find anything about it. Nobody's talking about it Please if you find a video or something You know link it down in the description below comment down below your thoughts Maybe your insights on on this implied volatility indicator I just wanted to bring that to everybody's attention to all my subscribers on my viewers that implied volatility is something very important in in my Opinion I think it's very important because it's so objective No matter what time frame you're looking at and because there's very limited information out there on the Internet like just think about that Something that's so objective and there's very little information about it. It just it's so Just mind-blowing like it's so weird, right? It's why why aren't people looking at implied volatility? Indicator I don't know your guess is as good as mine.  I don't have enough information. I don't have enough knowledge when it comes to Trading in general, so I'm very ignorant. So I apologize for that But thank you so much everybody for watching my videos all the support. I've been getting tons of emails In what not to see, you know where I am and you know my still training of course I'm still training, but I just haven't had enough time to today trade, but I'm at it again I'm been trying to hone down on this implied volatility indicator that I just want to figure it out like it's so weird. I Know I'm a broken record. I've said this so many times throughout this video that it's so intriguing to me But it's worth looking into everybody if you haven't yet subscribe please to my channel I would appreciate it greatly good trading information here on my channel And I also show you my day trades as they happen good or bad Thank you so much everybody for watching. Don't forget to like and share my videos comment down below What you thought about this video? I would greatly appreciate it. See you again next time


Everybody forced here being 2023 Star Wars master work hobby eight bucks hasten for 18 random mini box So open the case. This would be the front says it has our tag there four boxes top to bottom Bridges open um Four boxes here all open up face them this way the first box up top of any boxes one two three and four Just like that left to right and we'll go box one bucks two bucks three bucks four and then to the back row Just like that open it up here show you guys and then we'll random and then we'll rip Sign everybody a number here the other way facing us Same thing the back All right, there we go Again, this will be one is one two three and four and then five six seven eight We just keep going down then we go to the back row. Good luck on the random everybody We'll randomize names and numbers and then we'll rip that is a seven six and one one two three four five six and seven JD and the Chris V and the mini boxes now one two three four five six and seven 28 down to five one second. Let's move these over JD 28 Ryan G 12 Aaron N 25 Jonathan M 14 JD with 11 Timothy C 29 Chris V 3 Matthew L 7 Timothy C 31 Chris V 20 John B 6 JD with 16 Strive has 10 Christopher S 30 Andrew P 17 Shigunori 23 Jacob M 19 Francis D 15 JD 13 Shigunori 26 Robert I 27 Jared M 18 Andrew P 24 Francis D 22 Jonathan M 9 Matthew L 32 Francis D 8 Daniel F 4 Tuan with 2 Arturo 1 Tuan with 21 and Chris V with 5 number 10 for your strive How many beers you've had tonight? Oh wait, it's a mini box number. Sorry. Sorry mini box number. Yeah, I got you got you got you All right, let's do it call out names as we go along here Results can always you found a late in sports cards. That's calm everybody probably 13 Yeah, that sounds like it sounds like a Tampa fan Fire the cannons man. I'll have to go tell get was strived next year UCF Let's do it Not even gonna let it know we're gonna show up. All right Arturo number one Nice Harrison. Congrats, dude Sounds like a good night to hit a J-Rod out of it Good luck Arturo number one here. Oh, you got a plate. You got a plate a Lot of dinner plate, but a printing plate Edie on the blue foil of IG 88 rainbow foil that's to 199 that is peeling on the bottom Yeah, I'll send a Boxer-Rabber with this one for your number one Arturo and a printing plate the Mandalorian That's awesome Heck yeah Arturo. Congrats. Here we go. You haven't sold that for a little bit of Mars Swam in number two. So I'll set that up after this before I start personals Zero on the blue. There's some damage on the bottom of this as well and a relic of Dryden Voss That is not the right thing there. Dryden Voss on the shirt sourced fabric relic Some thick sleeves. You got a Boxer three Chris V Chris V number three Jarrett Gager on the blue What a base here in a twilight server autograph and Tray Bartlow is twilight server to 99 and the before Daniel F thicky thicky Dooku on the blue foil of BOSC BOSC number two two ninety nine a Java autograph as Leilani shoe as Java and a Cassian and or Radar screen a relic Cassian and or good mini box there at the end numbers five through eight here five Sausage Ventress blue and an auto Magistrate Morgan L. Speth Diana Lee, you know santo 1099 nice hit for Chris V with number five Six is for John B. Green Moff Gideon to 99 a Rainbow foil IG 11 more damage on this one same same card to IG 11 248 of 299 So number six John B. We'll get you a a box and wrapper if you want to try to get that replaced And a Calter Nali autograph Paul Casey Seven Matthew L number seven here Come on Hunter on the blue Luminar a undo the auto Olivia Diablo signs is the same a Mario Rivera does And number eight Francis D the Al Organa on the blue and a Riva commemorative stamp Riva commemorative stamp great. All right. We need to hit some big cards here moving forward first two hobby boxes out the best starting off with number nine Let's next one nine through 12 Jonathan amble number nine IG 11 on the blue Or does a quill and an axe wolves auto Simon Castanetes is axe wolves BD1 on the blue and a general Leia General Leia in number 10 stamp relic for strife right 11 is JD You know Jen, you know Princess Leia I stamp not the best, but lay a stamp decent Oh boy, we got something big here number 11 JD with number 11. What do we got? What do we got? I'll cast this on the blue canvas at 25 imperial guard One of one framed autograph Moses Angram as a Riva Big hit for JD mini box number 11 Geez dude one of one Riva autograph Congrats again JD Ryan G with number 12 still no sketches through three boxes here Our sketches green assaged ventures to 99 close drive close Trial X server Andre Barlow. You just have to try again tomorrow on Star Wars Masterwork Okay, number 13 count 13 through 16 here Not handing out free rolls right now 13 JD Jana blue. There's a foil of Tuscan Raider to 299 rainbow foil and An Ahsoka source fabric relic number to 10 10 of 10 shirt lining Ahsoka source fabric relic 14 Jonathan M director Krennick numbered six of 10 nice Krennick Low number there and a yando Donna on the radar screen relic yando Donna Remember 15 Francis D. Where's all these sketches at one of every 10 mini boxes? You're getting unlucky right now Captain Rex on the blue armor color match there and Auto hondo Onaka Jim Cummings nice hondo and this is 16 for JD purple land. Oh now it's out of 50 30 to 50 Lando cauricium And a fixer auto Skyler Bible man is late. Yeah Good live for eight hours and 45 minutes. Okay, we got six or 17 through 20 here Andrew P with 17 I wish I wish Jarvis that's a rainbow foil Obi-Wan Kenobi or Ben Kenobi No Lane don't say that Obi-Wan the 299 and rainbow foil auto massage ventures for a 15 Niko Futterman Yeah, Lane's got to be at this. He's got like the show starts at 9 a.m What's the guy doing probably sleep in chocolate for strawberries? Yeah, what are we on 18? 18 Jared M She just grew up. I've seen like photos green the 99 Bail Organa and An alpha trawler autograph tape Fletcher is alpha trawler to 99 Strawberry and that's Lane's breakfast too. I guarantee he's saving some for breakfast Dude, Lin is like hash brown. You got chick-flavored one for breakfast and he gave me a little Little hash brown bite things. Oh, yeah, he gave it to him. He gave it to me All right, yeah bet I house those things. No hell. Yeah, no sauce. I was just like no Shove on them second. We're on 19 here for Jacob M Finn on the blue Got a foil Obi-Wan quote Strike me down. I should become more powerful than you could possibly imagine it to 99 rainbow foil Do a lot of Ezra Bridger Hondo Onaka super cool 20 to 50 Taylor Graham Jim Cummings. That's awesome Congrats to Jacob with number 19 here do a lot of Ezra and Hondo We'll mag that People love Ezra and Hondo together. It's not three. You got something. You got to be a cop by one now It's driving moved up an hour. Oh boy 20 for Chris V 20 You where the sketch is that I don't know that it's really you let it's one in 10 that we're getting suit We're either gonna get a bunch in the last few years. Just getting super unlucky higher bike traveler auto Alfred sing come on Lane Potatoes seriously should give land of 24 hour time out Dude baked potato French fries Potatoes literally any kind I think I like yeah I'll grab the thin sliced in one dude. I go to restaurant. They got that I get that That's something I never want to make because it's all thin slice and all that stuff anyway 21 Twan Twan with 21 Settable to lots of flavor, which is good. All right, green Bob Bufreg. That's my guy right there It's a 99 and nice a Luke stamp 21 of 50 commemorative stamp Luke Skywalker for Twan 22 Francis D Well, we need a little and the Revo one of one though. It's but it's there happens in big hits Get a printing plate as well. So oh Here we go. Here's our first sketch Longest I've seen us go without a sketch in a case 22 right Francis D Carson TV on the blue Boba rainbow foil to 299 Whoa, that is sick Jin or so sketch. Oh my god. I like that a lot That is Andrew Fry. Holy cow. Jin or so.  All right super familiar with Star Wars tyranny on the blue and Auto magistrate Morgan L. Speck Diana Lee, you know something and 24 Andrew P purple Zeb out of 50 Zeb arellios and Then auto Captain Rex deep Bradley Baker. It's a good one for you Andrew Deep Bradley Baker autograph I think the Rex one does a little better than some of the other ones, but the guy like him does all the clones some of the Characters on the card actually do matter All right 25 through 28 25 is Aaron So that is canvas Django nice to 25 Django There's peeling on that. Let's send a boxer rapper to number 25 and a sketch Wow a ray sketch. I like that one. That was pretty cool. I like the style on this Ray sketch it in sign No signature I Wonder if the artist inside any of them who did this who did this? Six sketch either way What if you could find out by the style if you know the sketches if you know the artist really well Maybe maybe you can find out that way Never seen a non-sign sketch. We're actually maybe I think I might have I might have seen the non-sign sketch before and what another Like a chrome product. Anyway, um Nexus 26 Shikonori unsigned And they didn't know and they never put the card over they just forgot they could just forgot How to happen if they were having me do sketches which you never would but theoretically if I were to be good I would for sure forget Purple to 50 Valin Hess and Radar screen relic Bayes Malbus screen the 99 Robert I with 27 Banksy The things Banksy does Star Wars sketches. They could they could yes green Krennic number to 99 and a Jar Jar auto there he is Is How would I'm at best Jar Jar auto always gonna get a Jar Jar Robert and JD with 28 That's a blue Qui-Gon Jin and a Chris Sanson auto. That's Kerry Jones. It's Chris Santon. I guess that would make sense Come on guy just sign it guy or gal 29 to 32 here 29 is Timothy C. Let's sketch go. We're getting some sketches at least. What's in the third one here? That's good. I was still below average on the amount there blue grogu sketch Is that max that's max Rebo isn't it? Yeah, dude the blue elephant guy Rachel Jane art Max Rebo It's one of the legal favorite words is coward Christopher s on number 30 Speaking of Boss green Canaan Jarrus a Use the force loop rainbow foil quote card here to 99 and Kira on the medallion here crimson Don signet ring been there before illegal Sorry, man. So we got two numbered parallels though 31 Timothy C What if Timothy gets a sketch and I know you'll just the card that in between the sketches didn't happen Carson Tiva red three of 25 Foil den guard at 299 and a fixture auto scholar Bible and 32 for Matthew L here sketch sandwich I've had a few sketch sandwiches back in my day Don't sleep very well that night Can't leave the house either Get the cold sweats eating some sketchy sandwiches blue drash and an Imperial comms officer Otto Katie O'Brien That does it for the break. Thanks again everybody that full seller promo going up in a bit here


Hi everyone, welcome to the future is bright, the future is remote write. My name is Tom, I'm one of the Prometheus team and actually primarily work on the remote write code. In my day job, I'm the VP product at Grafana Labs. I'm still trying to figure out what that means after three years. I also started the Cortex project alongside Julius and more recently started the Loki project, the kind of Prometheus inspired log aggregation system. When I'm not coding, when I'm not working, I like to make 3D printers and occasionally brew my own beer. So without further ado, today I'd like to talk about four things, right? I'd like to talk about remote write. How did it start? What is it? What is it for? I'd like to talk about standardizing remote write and a lot of the recent efforts over the last two months to define what it means and to test that. I'd like to talk about what's next or what's in the immediate future for the remote write protocol. So I'd like to talk about metadata, I'd like to talk about exemplars. And finally, I'd like to talk about, you know, further off in the future for remote write, some of the ideas we've got. I noticed the slide says, examplars, I'd love to know what they are. So what is remote write? Actually, funny enough, the story of remote write kind of matches my story with Prometheus. The first PR I did to the project was to switch the remote write system from GRPC over to Proto buffs and HTTP. This was because it was quite hard at the time, you know, this was almost five years ago. It was quite hard at the time to get GRPC to go through an elastic load balancer. And I wanted to use Prometheus remote write to send data to Cortex. And really, that is what Prometheus remote write is for. It's for sending data to other systems. Prometheus sits there, scrapes the samples, scrapes your jobs, scrapes metrics from your instrumented applications and exporters, collects them, stores them, but can also forward them on to other systems. So we did this, we did this about five years ago. And over the past five years, we've seen many vendors kind of take notice of Prometheus and really add support for Prometheus remote write to their products. You know, they've made it so that you can send data from Prometheus to pretty much any of the metrics vendors in the world. In fact, if you look at the Prometheus docs, you'll see there are over 30 different projects that accept Prometheus remote write or send Prometheus remote write. And really kind of it's amazing that only over five years has it been so popular. And we're not resting there, you know, we really want to kind of push the interoperability story in Prometheus as far as it will go. More recently, in not the most recent, but the one before that release, we added the ability to actually have Prometheus receive remote write requests as well. So you can now configure a Prometheus to send data from one place to another, right? This really solves the kind of global federation problem in a very different way. You know, we noticed with Federation, Federation is the way you can set up a Prometheus to scrape the metrics from other Prometheus servers. So this allows you to have a Prometheus server, let's say in each region, and then a global one that scrapes all the data from the regional ones and get that kind of central view where you can run your kind of central aggregations. However, the challenge here is that this requires the global Prometheus to be able to scrape all the edge ones, right? So you have to open up firewall ports and figure out ways of securing, you know, three or more different Prometheus servers. With the push based approach coming from Prometheus remote write, you only have to open up that one central location and kind of lock down and authenticate one central location. And you can have the edge locations push to that central location. This might not sound like a big deal, but imagine if that these edge locations were on IP addresses that were changing or were maybe on flaky networks. You know, the remote write protocol might be a better fit for that. So this is in the second to latest Prometheus release. It's experimental. We'd love for you to give it a go, see if see what works, see what doesn't work and see if it suits this use case. So that's remote write. That's how it started, what it's used for.  And we want to make sure that this ecosystem is interoperable and really that all the users of all the different components can have the best possible experience. In particular, one of the things we've noticed is there's a bunch of projects popping up that fill this kind of scraped Prometheus metrics and send them elsewhere using remote write. You know, obviously Prometheus does that is the original one. About a year or two or a year ago, we launched the Grafana agent, which is a kind of stripped down version of Prometheus using all the same code, but kind of stripped down lighter weight version that doesn't have any local storage. You can't do queries, but it will just scrape your jobs and send them using remote write. There's also the Victoria metrics agent influx telegraph will scrape Prometheus scrape jobs instrumented with Prometheus metrics and send them elsewhere using remote write. And then more recently, you've got open telemetry, which will also scrape jobs using Prometheus metrics and send them over remote write. So these are the five systems that I'm going to look at and, you know, there are other systems. I have to kind of slip in at least one meme into each of my talks. So we started this effort to standardize it, right? We wanted a document that described what Prometheus remote write was, what it meant to say you were compatible with that. We also wanted to explain a lot of the reasoning behind the decisions, why we've done it this way. It wasn't all just arbitrary. And finally, we wanted to give some thought to how would we future proof this protocol? How would we upgrade this protocol? How would we make it so that when we introduced a v2, we could be kind of backwards compatible? I'm hoping that this will allow us to remove the experimental flag from Prometheus remote write. One of the key things here is that we're not changing anything with this standardization. We're just documenting the current behavior, how it currently works, because there's so many people that use this that I don't think realistically, we can change it, at least not in a incompatible way. You know, this will also allow us to offer some kind of compatibility guarantee. And I just want to say a big thank you to everyone in the community who's commented on the dock, who's proposed changes. It's really been a big team effort. So now that we have this standard, it's time to test those agents that I mentioned against this standard. And to that end, over the last week or two, I've built a test harness that runs an instance of each of the agents, exports some metrics for them to scrape, and then configures them to send that data back to the test harness via remote write. We then, in the test harness, export various different metrics and test, examine the response we get over a remote write and check it matches what we expect. This is relatively straightforward. We export a counter, we check, we get a counter back. We export a histogram, we check, we get a histogram back. But there's a lot of nuance to this protocol. There's a lot of different areas which some people do or don't implement. And so we wanted to kind of figure out what level of coverage we had. These are early results. I'm filming this talk almost a month before you'll be watching it. So hopefully over the course of the next month, some of these vendors and some of these other projects will improve their compatibility with remote write. And we're actively working with all of them to do that. So to start with, obviously we have Prometheus. Prometheus implements all of remote write. The specification is just a document that describes what Prometheus does. So we'd expect it to pass all these tests. The Grafana agent, using all the same code that Prometheus uses, just implements the same thing. And again, we kind of expect it to pass all the tests. Interestingly, we found a bug in the Grafana agent using this test suite. It turns out we were not removing duplicate labels. So we fixed that in the point one release. It was one line of code. The Victoria Metrics agent does pretty well actually. It has some slight inconsistencies around how it does the up metric. It doesn't actually, as far as we can tell, send the up metric when there's a failed scrape, which is kind of important for the test harness to tell the difference between the agent not doing anything and the agent successfully kind of failing. And also the Victoria Metrics agent doesn't implement the staleness markers, which are really important way we can tell when metrics go away. Telegraph, not quite as complete as the Victoria Metrics agent. In general, it doesn't do up or staleness at all. But it doesn't quite have the right job labels there. You can program it to add job labels, but it's kind of missing some of the features of service discovery that would add those job labels. Then finally, the open telemetry collectors, the newest kid on the block, so not as far along in its support. It doesn't propagate histograms correctly, doesn't do a lot of the job labels correctly, no up metric, no staleness markers. We're actively working with the open telemetry team to try and get better support. And hopefully in a month or so, we'll see if they've got better support. I'll be hanging around for a kind of live Q and A at the end, and I'll make sure I bring updated results for that. Next, metadata and exemplars, not exemplars. First, metadata. Not a lot of people know actually that Prometheus client libraries allow you to add help text and type metadata to every metric in your application. Prometheus scrapes this and stores this in memory, stores the latest values in memory, and then has an API so that client applications to Prometheus like Grafana or the Prometheus UI can query this and use it to help build these kind of UIs. So Grafana builds this particular UI just allowing you to see what each metric is. We want to enable systems that implement remote right to have the same information and basically the same experience as Prometheus. And so back in February last year, so over a year ago, Josh added support for metadata to the remote right protocol. So it's an extra field and it's kind of a bit best effort, right? We're taking some of the metadata and sending it on a period alongside your samples. We want to make a series of improvements to this. We want to write the metadata to the right-hand log. We want to send it alongside the same metrics that it's supposed to be sent with instead of just kind of arbitrarily sharding it. And Rob from Chronosphere actually has a PR that achieves some of this that we want to work with him to get in over the next few months. So the next example we want to give is exemplars, right? Spelt correctly this time. In exemplars allow you in Grafana to overlay kind of dots on a graph. And then when you click on one of those dots, one of those exemplars, you can jump straight to the trace that that dot kind of represents, right? So Bjorn added exemplar support to ClientGolan quite a while ago. And Callum added exemplar support to Prometheus in the last release. And together you can implement this really cool experience that really speeds up kind of incident response and debugging workflows and really kind of makes the whole system feel a lot more integrated. Prometheus doesn't actually care where these traces are stored. You can store them in Yeager, you can store them in Zipkin, or you can store them in Grafana Tempo itself. We want to make this available to remote write endpoints to people who are implementing remote write should also be able to receive exemplars and offer the same APIs and the same experience. And to that end Callum from Grafana Labs, he is adding a remote write for exemplars. So this is going to be writing the exemplars to the right-to-head log and then tailing that right-to-head log is as part of the remote write code and sending them out in batches. This will also enable kind of long-term storage of exemplars and some really cool use cases around that. Callum assures me this is going to be merged by the time you're listening to this talk and we really hope that this is going to be in the next major release of Prometheus. So finally, what's next? What are the kind of more long-term things we want to do with remote write? First thing I want to talk about is atomicity. So Prometheus has this really cool guarantee that, sorry, before I go into the guarantee, a lot of you will know that Prometheus metrics are normally, you know, sometimes composite and actually made up of multiple time series.  This is kind of how we build up these histograms and how we can tell latencies in your application. And so it's really important that when you run a query, you only see a complete scrape. You see a consistent snapshot of a scrape. You don't see kind of partial data or half updates from one scrape and half updates from another scrape. Prometheus offers this, right? It's quite a cool feature of TSTB and it's really useful. Remote write unfortunately doesn't do this. It actually prevents systems from offering this guarantee because of the way the remote write client inside Prometheus splits up batches of requests to send them in parallel. So this means that remote write systems might actually get metrics or samples for different series in a histogram in a different order, right? And we'll actually see these partial states. This means they don't have the opportunity to implement this, which we think kind of sucks, right? So we want to fix this. We haven't decided yet how we're going to fix this. You know, one of the thoughts is that we're going to make sure that this scrape, the entire batch of samples that are gathered in a single scrape are written to the right head log in a single batch, which is kind of already the case. But then the remote write system reads that entire batch in a single kind of scrape, in a single read of the right head log and sends it out to the remote system in a single batch as well. And so kind of aligning this throughout the entire pipeline will at least give the kind of the systems at the other end of the remote write or give them the opportunity to offer atomicity. Another thing we're working on solving is kind of or improving at least is the handling of 429. So 429 is the is the status code that remote systems will send when Prometheus is sending samples to them too quickly. It's 429 is kind of rate limit is a back off, right? So Prometheus is designed to back off and retry on 500s. Now 500s indicate there was something wrong with the system, you know, it was the service fault, we couldn't handle the request, you know, please try again. But Prometheus doesn't retry 400s, right? And that's on purpose because 400s indicate there's something wrong with the request, right? And that request will not succeed if you try it again.  And it's weird, I think that 429 is a is a is a is a rate limit, right? Because, you know, actually, if you back off and retry the 429, the request that received a 429 response might actually succeed. Either way, what happens is, you know, we talked about how Prometheus is collecting data from your applications and writing them to a right head log and then reading that right head log and sending it to a remote system. And if that if that if there's a network outage or heaven forbid an outage on the remote system, then that will start to buffer up on disk, right? And these samples will buffer on disk and Prometheus will basically wait, you know, periodically retrying, but wait for wait for the system to come back up. And then after that outage, Prometheus will try and replay that right head log to the remote system to fill in any gaps. You know, what Prometheus will replay as quickly as it can, and it can replay pretty quickly. So it replays many, many, many samples and that upstream system sends a 429 saying you're replaying too quickly. At that point, Prometheus will basically just drop the data. So after after doing all this really hard work to to batch up the, you know, to buffer up the data on disk and make sure it's there for, you know, during the period of the outage, when the system comes back, we replay 429 and drop the data. And it's a real shame we do this. So we think we can improve this by backing off on 429s and knowing when to kind of balance, you know, catching up against kind of falling behind because, you know, you never want a system to kind of get behind and stay behind. So finally, another area we're actively looking in and investigating and looking at improvements for the remote right system is its bandwidth usage. You know, I touched on a bit earlier how we designed the system to be pretty simple, pretty stateless, right? And this is a key principle that I think has really made the protocol easy to implement, right? There are no interdependencies between messages in the protocol. And this simply just drastically simplifies downstream implementations. It makes things like Cortex easy to write. It makes the the adapters between Prometheus and graphite and Prometheus and influx. It makes those adapters simple to write. And I think this has been pretty successful. You know, we've seen, as I said, 30 different implementations of remote right. And I think one of those, one of the reasons this has been successful is because it's a relatively simple protocol. However, this comes with downsides, right? It's expensive, right? The fact that the batches are stateless means that they have to repeat labels many, many times, you know, the same labels sent in most batches. And this really eats bandwidth, you know, we use between 10 and 20 bytes per sample to send via remote right. And Prometheus only uses one or two bytes per sample on local disks. So you can see there's a big, big room for improvement here. And our internal monitoring at Grafana Labs, just to propagate samples between our internal Prometheus nodes and our internal Cortex cluster, we're doing over 90 megabytes a second of remote right. So there's probably a 10x gain here. And there's various ideas. We think a lot of the work we're going to do on atomicity and batching and building these consistent batches will allow us to have a kind of symbol table in the remote right requests that will probably reduce bandwidth usage quite a lot. And that's it really.  Why does it exist? How did it start? We've covered our efforts over the last couple of months to standardize remote right to really document how it works, why it works that way, and then test implementations to make sure that they work the way they should. We talked about what's coming kind of, you know, pretty soon, hopefully in the next release or tour of Prometheus, we should improve the way we send metadata via remote right and start sending exemplars via remote right. And finally, we've talked about some of the ideas we have for the more long term future, how we want to make it remote right atomic, how we want to deal with back off and retry on 429s and how we want to reduce the bandwidth consumption of remote right. So I'm going to hang around now, take some live questions. If any of this was interesting, please do ask and thank you very much for listening. Bye-bye.


Good local time, everyone. This is Audrey Tong, House Digital Minister. It is my great pleasure to be virtually here at the opening session of the 2021 Tsukuba Conference for Future Shapers. Now the theme of this year's Tsukuba Conference is inclusive innovation for the new normal, which I believe is very timely at this moment. As the COVID-19 pandemic swept across the globe and many parts of the world have endured more than one year of closures, of lockdowns, and other pandemic restrictions, we're now facing with a very real possibility that this scenario may eventually recur and become the new normal. Now we need to continuously find ways to deal with the challenges that confront the global population. Well, there is never an easy way to tackle these emerging challenges, but I do see opportunities arise among the biggest global crisis of our time. One of the lessons that a pandemic has taught us is that instead of striving for the most cutting edge technologies, like stronger, faster, higher tech, it is more important now to bring everyone together. Digital technology is coming handy during the pandemic era, and of course beyond. As the digital minister of Taiwan, I have some interesting experiences to share in this regard. Since the end of the Second World War, Taiwan has transformed itself from the relatively simple agricultural society with all powers monopolized by one dominating ruling party to today, a state of a vibrant social, cultural, and political pluralism. The first direct presidential election was held in 1996, and that was just the year where the war well became really popular. The small islands of Taiwan proved to have major advantages in deploying internet connectivity with our size just a little bigger than the US state of Maryland, and a population approximately the same as Australia. Since 1998, Taiwan has been planning the digital government and has successfully completed various stages of digital government programs. And today, this idea of broadband as a human right is firmly at the core of the government's policy. President Tsai Ing-wen announced a platform of Digital Nation Smart Island during her first election campaign in 2016. And the very next year, we launched the Digital Nation and Innovation Economic Development Program, or the DIGI, DGPLUS. And this year, we've operated to the Smart Nation Program with the vision of a Smart Nation for innovation, inclusion, and sustainability by 2030. Now, our vision of a Smart Nation 2030 reveals a new direction for our digital governance policy. Any innovation in our modern world must be pluralistic and inclusive with sustainable development as its goal. And this means that it is no longer the case that the government is formulating policy from the top down. We're no longer dictating new development paths for industries or directing people to shiny new public services, but rather we must be receptive to building ecosystems of what I call people-public-private partnerships. To address problems, we need to be guided by the needs of the people. And indeed, in our pluralistic society, people's needs are ever shifting and regardless of whether governments are willing to address them timely, there will always be civic technologists willing to tackle new problems with digital innovation. So ever since the establishment of my office, the public digital innovation space, or PEDAS, were a policy lab in Taiwan's cabinet. Since the beginning, we have been dedicated to not only work with the public service, but also work with the citizens so that we can work in the public service through social innovation. For example, we held collaborative meetings around a hundred of them to improve, for example, the online text declaration experience. We also worked with the National Pulse Museum to build the new ticketing system. But more than that, we have implemented this into a program called rescueactionbyuse.gov, or REI program. For five years running now, we invited young people year after year to participate in public affairs and encourage them to enhance the experience of our digital services from the perspective of citizens. And this citizen-centered design thinking method have a dedicated annual event called the presidential hackathon, where the winners every year receive a trophy from President Tsai Ing-wen, that carries the promise of realizing their ideas on a national scale. So what we're aiming to do is to establish a mechanism that builds mutual trust based on dialogue between the public sector, the social sector, and the private sector partners. This long running spirit of inclusive innovation plays an important role also in our ongoing fight against the COVID-19 virus. A good example is last year's face mask map. It's initiated by an entrepreneur working with the community called GovZero GZeroV. It's a group of civic technologists. Now, to prevent the panic buying of medical grade face masks, we instituted a national rationing scheme by anticipating that the policy would be insufficient to avoid runs on the pharmacies. We have released a application programming interface, or API, to provide the public every 30 seconds with real-time location-specific data on mask availability. Now, this eventually enabled the creation of the face mask rationing maps. This subsequent 192 to SMS contact tracing system is another brilliant example. We had a wave of infection this May, and we announced a national wide alert level three. So various new mechanisms were invented to minimize public exposure for contact tracing. Businesses introduced their own apps for contact information registration, and the government looked into the experience from the public and the private and the social sectors. And combining their experiences and innovations, we eventually rolled out the SMS-based contact tracing system. Although it's not compulsory, it soon became part of people's lives. And this innovative app-free design by the Gov Zero Civic Tech community proved invaluable. In Taiwan, we have dedicated ourselves to bring technology to the space where citizens live, rather than expecting citizens to adapt to the space of technology. So what we're striving to do is to allow these completely different ends of the spectrum ideas and with markedly different positions to come to the table, to discuss and also to collaborate. So for May, inclusive means taking all the sides. If it's not possible to take all the sides at a moment, well, at least we can listen carefully to all the sides and come to a good enough rough consensus. One practice worth mentioning is the establishment of the one-stop online participation platform, or join the Gov.tw, where anyone can file a petition and participate in budgeting. And face-to-face collaborative meetings are held by the ministries twice a month to explore ways of incorporating ideas from the petitions with more than 5,000 signatures into policymaking. So it is a platform to make sure that literally anyone, not just citizens, but also residents can set the agenda and participate in the decision-making process. In fact, more than a quarter of these initiatives were started by people under 18. For example, the petition to ban plastic straws gradually from our national identity during the bubble tea, well, it was created by a 17-year-girl. So when we're faced with shared challenges that transcends borders, people from various sectors need to work together to explore ways to adapt to the new normal and also to thrive in the new normal. And I believe inclusive innovation is the way to achieve this. And moreover, I do believe that inclusive innovation is going to be the new normal. Finally, let me share with you my job description when I joined the cabinet as a digital minister. When we see the internet of things, let's make it the internet of beings. When we see virtual reality, let's make it a shared reality. When we see machine learning, let's make it collaborative learning. When we see user experience, let's make it about human experience. And whenever we hear that a singularity is near, let's always remember the plurality is here. Thank you all for listening. Live long and prosper.


Have you ever tried Slovenian wine before? This is a tiny country in central Europe, but it packs a lot of Venice punch. I'm gonna break down the country and recommend some of my favorite producers.  Hello, hello, hello. Welcome back to Exotic Wine Travel. I am your host, Matthew Horkey. Welcome back to the show where we help you drink adventurously so you can expand your palette and expand your mind. We're gonna be expanding palatine wines today with wines from one of my favorite parts of Europe here. And that is Slovenia. If you ask a lot of random people, they might not even know where Slovenia is. It's really this tiny country that's kind of wedged in between Italy, Hungary, Austria, and Croatia. Sits right in the heart of central Europe, right in the bridge to Eastern Europe. There's a long history of wine making here. The Illyrians, the Celts were making wine way even before the Romans. Then the country was part of the Austro-Hungarian Empire. In 1918, it became part of the Kingdom of Yugoslavia. And then in 1991, it became independent. There's about 22,000 hectares of vineyards in the country. Just to give you an estimate, that's a little bit more than Napa Valley. And just take this for instance, Napa Valley produces only 4% of all Californian wine. The country's really built on small family-run sellers. There's about 2,500 bottlers in Slovenia for such a small country. That's a lot of different wine brands. Among all the countries in the ex-Yugoslavia, Slovenia is held up in a high regard in terms of their wines. The climate is kind of quasi-mediterranean all the way up to true continental in the eastern part of the country. There are high, high mountains, the Alps in the northern parts of Slovenia. So the cool air comes blowing down that really has an influence on the climate. When you're choosing a wine in Slovenia, luckily most wines are labeled by variety. So that's easy to know what you're buying. There are producers that name their wines after a Kuve name. There are also some special protected names in Slovenia, special wines, you know, like Chianti, Clasco in Italy. You know, Slovenia has some wines like Taran, Svigcek in a couple of others. The name for wine in Slovenian is Vino. Bello means white and Ardece means red. But how do you know what the dryness level is in the wine? There's gonna be four categories and it's gonna be stated on the back of the label. First you'll have Suho, which is dry. You'll have Pol Suho, which is off dry. Pol Slabko, which is semi-sweet. And then finally, Slabko, which is sweet. They also have the German-Austrian rules for Predacat wines in terms of late harvest, selected late harvest, dried berry late harvest and ice wine, but I won't get into that in this video. On the back of Slovenian wine, you can see if it's a PGI or a PDO wine. That is a wine with protected origins. At the bottom level of quality, you're gonna have de gel no vino, which is basically table wine. That's gonna have PGO at the end of it. Moving up a level on quality of a types of wines that you're probably gonna be buying, these are Cacavos no vino. This is basically a quality wine and you'll see a ZGP at the end of it. That basically means an appellation. Think of ZGP like DOC's in Italy, AOC's in France, DOC's also in Portugal. And at the highest level, you'll have Vergunsko ZGP. These are wines that are made with real strict controls. Most quality producers I know battle at the Cacavos no vino level and I think it's because it allows for a little more flexibility in the winemaking. Don't even make me try to pronounce ZGP and what that stands for. I know the Slavic languages. Slovenia is broken down into three wine regions and then those regions have subdivisions or wine districts. Two of the wine regions are in the eastern part of the country and those are Pusavje and Prodravje. Pusavje is around the river Sava, Podravje is around the river Drava. Both of these regions are more cool climate regions. So you're gonna get a lot of white grapes, grapes like Sauvignon Blanc, Lasky Riesling which is basically Welsh Riesling, Grashavina, Pinot Gris, Gertströmina, Riesling, Chippoon which is known as Furment and of course Pinot Noir, some Merlot and some Blau Frankish. You just have to know that Slovenians call Pinot Noir, Modri Pinot and Blau Frankish, Modri Frankinja. I have to admit it's the part of the country where I'm a little bit the weakest in terms of Slovenian wines are much stronger on the western side. Pusavje is probably the least harrowed region for finer wines in Slovenia but there are some impressive producers. Like I came across this one, Chukje, he's a French man making wine married to a Slovenian woman. This is the Lodoma. This is a single vineyard Blau Frankish which is an outstanding wine. Shows a lot of elegance and depth, really impressive. Other producers in that region I recommend are Keltis, Istinit, Klettprus, Sturm and Freely. Podravje is located in the northern part of the country, the northeast part, so it's bordering Austria, Croatia and only at a sliver of Hungary. I think Sauvignon Blanc is the best here. Also, I've tasted some great Gavette Stremina, Riesling as well, Pinot Gris and then especially Chippur or Furment. One of the most famous wine districts of Podravje is Stajerska which produces some outstanding white wines. This is one of my favorite producers actually. This is Vinocupil and this is the White Star. I believe this is Chardonnay, Riesling and Pinot Gris, all blended, barrel fermented, really rich, bigger white wines. I've also tasted a lot of surprisingly good Pinot Noir from this region. Other producers I recommend are Puklevitz, Heapsgood Winery, Johanna's Pratner, Asierbaiz, Madoff, Matitsch, Slapchak, Dukal, Gobal, Gontz and Dveri Pax. This part of the country is becoming hotter and hotter and there's a lot of small sellers doing a lot of experimental wines. It's really a place to keep your eye on. It's a place I wanna spend more time in in the future. Do you wanna try Slovenian wines? Well, there's a great option for those in the European Union. Just check out the sponsor of today's video, Vino.co, that's V-I-N-O-O dot C-O for the biggest selection of hand-picked high quality Slovenian wines from boutique family run producers. Vino delivers Slovenian wines all over the EU and today you can order Slovenian wine with a 10% discount as a viewer of this show. Just enter the coupon code EWT10 at checkout and share this with your wine friends so they can get this offer too. Now back to the show. In the western part of Slovenia, that's where you'll find Primorska. It is the most prestigious region in Slovenia in terms of high quality wines. This part of Slovenia is kind of a mild Mediterranean climate or quasi-Mediterranean. It has influence from the Adriatic Sea but it also has cooling influence from the Alps and there's a lot more rain than a normal Mediterranean climate. This is also a part of Slovenia that has more unique grape varieties and very distinctive wines. Primorska is broken up into four wine districts. In Slovenia, Istra, they focus on Malvasia, Istarska and Rafasq. Malvasia, Istarska or Istria and Malvasia is a wine that can be floral. It can be pretty high alcohol. This is the Karenica and Moshgon, Padermo. This wine is macerated. It's heavy, minimal intervention and stuff but the skins on Malvasia, Istarska are sweet and the tannins are so lovely. I personally prefer the grape to be done in this style. In Slovenia, Istra, you'll also find the grape Rafasq which is a crazy, wild, untamed red grape can have flavors of rusty nail, a lot of wild berries, sometimes blackberries, mulberries, iron, chewy tannins and sharp acidity. When it's done really well, I think it can resemble Northern Rome's Sera. On the other side when it's too acidic sometimes it can be enamel stripping and you really need food. This is a brand new producer in Slovenia, Istra. This is the Zaro, this is the Rafasq. Interesting wine, high in acidity but you have some of those unique Rafasq flavors. Other producers that I recommend in Slovenia, Istra are Rajman, Copa, Rodica, Royaz, Bordeaux, Gordia and Klabien. Move a little bit more north, you have Kras which is a limestone plateau. It's an extension of the Carso in Italy. Here you'll also find these grapes, Malvasia, Istarska and also Rafasq but you'll find some nice Merlot. Also some ad grapes like Vitowska, Pinella, Zelen, those grapes that you find in Vipava. The wines there can be a little bit rustic but really full of mineral flavors. Some producers that I recommend are Chotar, Lisiac, Stemburger and Skrull. Bordering Kras is the gorgeous Vipava Valley. This is a corridor that really connects Central and Eastern Europe. This is a breathtakingly beautiful region. I remember the first time going there just taking the long drive through the valley and just being in awe. In terms of area dedicated to vineyards, this is the second largest wine district in Slovenia. Only second to Shtajerska in Podravje. Here for red grapes you'll find fabulous Merlot, some excellent Pinot Noir and some very interesting Barbera. Cabernet Sauvignon is also grown. You'll also see Blau Frankish. Whites is where it gets really exciting in Vipava. You'll see things like Reboula, also known as Reboula Gialla, Chardonnay, Pinot Blanc, Sauvignon Blanc. Then you'll find really interesting grapes like Zelen, Pinela, Vitowska. There's also plenty of small, minimal intervention sellers. I have some of my favorites right here. Like the excellent Reboula is from Lelčnik or Svetlik. Lelčnik is one of the guys that kind of kicked off this macerated wine movement along with Gravner, Raddakon right across the border in Italy. I mean, his vineyards are basically a stone's throw from the Italian border. You have newcomers to get the game like Garila. I stayed up at their winery once on a press trip high above the valley. Incredible biodynamic wines and the wines keep improving with every vintage. I get more and more impressed the more I taste them. You also have some extreme wines like this Barriabella which is basically a blend. I think it's a Reboula, Lashki, Riesling, Malfacia and then some other random grape varieties just like this Batec Zarya and also this Sveci Miha from Yink. These are three of my favorite producers in Slovenia. The wines can be a little bit crazy sometimes but I really enjoy them. And then you have more classically styled wines like Tillia. Tillia is known for his Pininwars which can be a little bit bigger, a little bit more Burgundian style. They have Tannins. They really need time to soften and they need age. Other producers in Vipava that I recommend include Slavček, Lavrenčić, Vina Bizjak, Berce and Krapež. And last but not least, you have Grdiška Berda or Berda for short. This is an extension of Collio in Italy. Actually, it might be considered the other way around because there's a lot more vineyards in Grdiška Berda than there are in Collio, Italy. There's a strong Italian influence here. A lot of hilltop towns, steep vineyards. It really looks like Piedmont, Italy because you have the Alps in the background. This region has the reputation for a long time of producing some of Slovenia's best wines. Grdiška Berda has just fantastic terroir, fantastic positions for vineyards. I remember my friend who's a producer of wines in Istria Croatia said one time, you know what, those guys in Grdiška Berda have such good positions. Sometimes I think you can just throw the grapes out in the wine's great. In Grdiška Berda, you'll find a lot of the grapes that you find across the border in Friuli, Vinicea, Giulia. That means you're gonna find things like Rebola, e.g. Rebola Gialla, Friolano, which they also call Jaco or Sauvignon Nessie. You'll also find things like Picolet, Mavasia Estarska. You'll also find some international white grapes like Pinot Gris, Sauvignon Blanc, Pinot Blanc, Chardonnay. For reds, most of the best examples are Merlot with some Cabernet Sauvignon blended into it. I actually did a blind tasting the top Slovenian red blends like up against some top flight Italian wines. I'll put that in the description box below. There is a little bit of Pinot Noir to be found in Grdiška Berda, but I think it's more of a place for Merlot. Like the rest of Primoška, orange wine, macerated wine, amber wine is really the focus here although there's a lot of classically styled whites as well. There are also some of my favorite wines in Slovenia. I mean, you have the high quality guys, Eddie and Margin Simčić, Eddie Simčić making classically barrel fermented style wines, Margin Simčić making more classical style wines, although he makes also some macerated white wines, also makes the best Pinot Noir in this part of the world for me. Guys like Šturek, another crazy guy. If you see him, he's always wearing sunglasses at wine shows. I really like his house style, big barrel fermented rich white wines, maybe just a touch of maceration. You have the Frenchman Jean-Michel Cabai making wines there. You also have interesting classically styled whites like Jakončić, another one of my favorite producers also makes outstanding Merlot. You also have real hardcore minimal intervention guides, Klenets, he also has a guest house, makes fantastic food and the wines are just really extraordinary, only macerated wines and a couple reds. Then you have the cooperative Kletberda, 480 growers that still own the winery and a lot of these guys or their families got their start in Kletberda when Slovenia was part of Exegoslavia. And of course you can't talk about Slovenian wines without mentioning Movia, the eclectic crazy wine maker, really kind of helped put Slovenian wines on the world wine map, makes some excellent wines, some crazy wines like sparkling wine named Pearl where you have to discourage it, it comes upside down. Lunar where you have to decant it and you lose this much sediment and as crazy and as loud as the guy it is, I think the wines are actually beautiful wines, especially with age. Other producers in Griskeberda I recommend are Erzitić, Bianna, Kristintić, Konstantini, Madov, Vlažić and Gaspern. You gotta know though, this is one of the more prestigious areas in Slovenia, that means the prices are a little bit higher. With so many wine growers and so many bothers in Slovenia, you're bound to find new discoveries. Like myself, there's always new wines to discover. In doing some of my articles about Slovenian wine, these are some producers that I tasted it for the first time, Patrick Simčić, a young guy, Emeryn Rye, I got his rebooting, his brand, I really like some of his Maserade wines. Making only one white, one red, really impressed more freely in style of wine than you have other crazy guys like Ronk and you're a Shtekar and Griskeberda making some interesting wines. And also, this is a new guy in the scene that I didn't really know about. Kultus, his red, white blank, really good wines. And also you have the old cooperative Vipava 1894, what's now a negotiation in the Vipava Valley. That's the cool thing about Slovenia and wine in general. There's always something new to discover. So I'd love to know, have you heard of Slovenian wines?  What do you think of them? Let me know in the comments below. Stay tuned to our website, exoticwinetravel.com for several articles and some of my favorite Slovenian wines of the last year. And I will see you soon. Hello, thanks for watching. Hey, you made it to the end. Make sure to subscribe to our YouTube channel, click the bell so you know when new videos are out. If you like content like this, check out our Patreon page where you get some behind the scenes exclusive content. Thanks for watching. Cheers. Cheers.