Hello. Welcome to, I think, the last session of the day, the first day at KubeCon. So my name is Eduardo Silva.  First-timers. Oh, that's great. Cool. And do we have any new Fluentbit users who's not using the technology already, or are all users? Somehow. Happy or not, you're users. OK. Lot of questions. OK. Both. That works. Awesome. So to get started, today we're going to introduce the technology. We're going to talk about the stand of the project, where we're going, and how do we fit in all this huge ecosystem that, for new starters, it's got sometimes a bit complex, right? You don't know where to start. Now we have, I don't know how many projects we have in the CNCF, but when we joined, we were six projects. And now I lost account. But today we're going to focus on Fluentbit, what is called the telemetry agent. My name is Eduardo Silva. And the creator of Fluentbit, a CNCF maintainer, has been with the CNCF for a long time, and a founder, also this company called Caliptia, an actual CEO. Let's talk about the problems that we solved in the ecosystem. And I think that's the most important thing. When you start doing this journey, for example, most of you might start with logging. One of the challenges that we had is you don't want to wake up one morning and say, I want to do logging, and feel really happy about it. Actually, you want to solve another problem which is about data analysis that ended up that you want to solve logging, right? So if we look backwards, our goal is to get insights. And to get insights, you need to collect information from applications, from the running systems. And when you get an issue, or you talk to an ops person, or if you're an ops person, the first question is, hey, do we have the logs? Or give me more logs, right? But you might understand that in today's world, getting more logs or more data doesn't mean more value. Doesn't mean more answers, right? And we need different approaches to deal with the scalability of data that we have in our systems. If you think about applications, all of them store the data in different places, usually in the file system, right? With a different file, for example, in GeneX, creates an access log for HTTP requests, an error log, CIS log has its own endpoint. But if you go to, for example, a window system, you will find that, hey, there is an API, a way to extract logs from that not common operating system. And when you want to go deeper and understand how to extract information to do troubleshooting or do analysis, you might end up with three major categories, right? Data lives in the file system where you read a file, or maybe you just read a pseudo device or pseudo file system that exists or is exposed by the kernel on that moment. I'm talking about kernel log messages or a TTY interface. But also, there are other parts where we can collect information from. One of them could be SystemD or JournalD. But usually, those services are not like you just run cat, the command, and just consume the data. Actually, you need to use JournalControl or JournalCTL, or you just need to use the C API to open the journal from SystemD and get the data. Same as for Windows events logs. And also, in this world of distributed systems, data does not only lives in your computer, also in remote endpoints. If you think about the Kubernetes cluster, and you want to get events from your cluster A, your data is not in your node. It might be in the API server, and you need to retrieve this over HTTP. Or also, somebody wants to send you information over the network to check the status of what's happening. For example, if you're running a firewall in a hardware, that hardware is going to ship Syslog messages and somehow you need to capture that information so you can do data analysis. I'm talking about network endpoints. And as I said, the goal is just to collect data. But when you go, in reality, you face these things. You have logs everywhere, different operating system, different ways to collect information, and most of users just walk away, or just say, oh, I'm going to just troubleshoot just maybe I'm going to collect a fraction of the information that is available. But the approach is not scalable, so we need other ways to solve this problem. And imagine that you got the information. You got the information, and now you got them in a rate of bytes that you might understand. You have an instructor log, an example, where we have an IP address, a timestamp, and some information about the HTTP request. When you read this, you understand it.  This looks like a timestamp, and this looks like everything else. But if you just pass these bytes to the computer, and you try to do some analysis, hey, it's just some array of bytes, and that's it. Unless you provide something more meaningful or with some structure that allows you to do a better analysis. Ideally, we want to convert all the data that comes in a structure way to a structure. I'm not saying that JSON is the best format ever. I'm not saying that. I'm saying that we need some representation that says, hey, there's a key that has a value that has a meaning. So we can extract that value from it. And in general, the whole world around logging, it's about converting unstructured data from some place, going through a part in a processing process, and then convert it back in a structured way. So our final goal of data analysis gets more easy. And if we face reality, your data is not in one server. They are in virtual machines. They're in containers, firewalls, or any type of machine that you can imagine that can generate data. Well, now we have machines in your kitchen that generate logs, right? That's insane. And you need to collect that information. Maybe not you, but the companies that monitor those things. I don't know why I want to interstate it in the logs from the microwave. But yeah, there are devices that ship that information. And having this mechanism of you writing scripts, you writing every single script to collect data from one endpoint, it doesn't work. For a company, developers jump from one company to the other. Nobody documents anything. And somehow, you need a scalable and unified way to solve this problem of data correlation at scale.  You want to extract the value from that data. But if you don't have control, if you don't have a very scalable way to accomplish this, you might end up paying a couple of boxes to your favorite vendor for data that maybe is not relevant. You're just sending everything. And I know that, yeah, we have Splunk users here. I know you don't want to raise your hand. I get it. That's fine. But you can take the best of that world of best. You're laughing because it's right, right? And not blaming Splunk or any other vendors. I think if we abstract from the problem, what we have is like, we don't have control of that. You start using a product, and it's like, hey, use your credit card. Don't look at the bill for months. What would happen? If you don't have control, you're going to get in troubles. And when moving data and processing data is the same thing. Yeah, you don't care until your money is told you, hey, why we're investing $2 million in a database? Well, we don't have a strategy. Now we need to implement a strategy. And this is the goal of this session. And to solve login challenges, we need to think how to deal with different sources, different formats of data that is structure, not structure, and also think about volume. Because companies and we who are developers, we try to write a lot of software with a lot of print F log messages that ended up in a Splank database that you ended up paying for. And then sometimes it's data that you don't need. And this is where FluentBit comes in. And FluentBit is a unified solution for telemetry data that goes beyond the scope of logs, also does metrics and traces. And FluentBit was created around 2014. It's written in C language. Yeah, we can talk about that later if you want. It has a fully pluggable architecture that allow us to connect different sources with different destinations by doing different type of processing. We provide more than 100 connectors built into the same binary. And it's fully cross-platform for Linux, Windows, Mac, OS, and BSD. Yes, there's banks and many institutions that runs Windows at scale. And they need to solve the same problem. And also when dealing with data pipelines, that's how we call when you start solving this process, you need to have provide ways to level up the user and allow them to bring the business logic into the pipeline by writing, by putting their own rules or policies for the data that is going to be collected. You no longer want to send all the data to your database. That is not working. It's not scaling. You need to have something in the middle that take control of your data. And sometimes writing custom components is a solution. And also FluentBit is a vendor-neutral solution. FluentBit is a graduated CNCF project together with FluentD. So FluentBit is used everywhere, and it will be there for many, many years. So I got this question many times this morning while we were in the booth around vendor neutrality, around open telemetry and how the FluentEcosystem fits around this. And one thing to remember, graduated project, and it connects to multiple ecosystems. Many vendors and sometimes projects that are not part of the CNCF, others, they try to have a pitch in general that to solve the problems in production, you need to replace everything what you have and just use this solution. This is a magic booth. It doesn't work like that. Actually, if you go to production on any environment, you will find three type of databases, different aging collectors, you know? And if you want to solve this at a scale, what you need to do is to have a solution that can integrate to what you have in place. Because migrate this infrastructure tool from one to the other is really expensive in time and investment. So having the right approach is important. FluentBit can interoperate with Prometheus, interoperate with OpenTelemetry, with FluentD and with many others. So from a very high level, FluentBit is a telemetry agent that connects many sources with many destinations and in the middle can do a lot of processing, right? This is what allows you to take control of your data, right? And as I said, we support logs, meters and traces. And maybe you have here about this company, have you heard about this agent fatigue or maybe you have 10 agents in one machine and you have the same thing in, I don't know, 100,000? Yeah, this is amazing. So maybe you have this in your environment where you have Fluent, you're using Fluent to collect logs and also you have, for example, Prometheus, not exporter to collect the operating system metrics. And then you have Prometheus scraping the metrics from the system by using this approach. Now, what happened some time ago is like talking to the Prometheus users, they told us, hey, we love Fluent, Fluent is on every machine, why we don't implement some Prometheus experience inside FluentBit while we can reduce the number of agents that people have, right? And Prometheus focus more on storing metrics, providing the PROMQL, everything that is about storage, right? And from a scraping site or data collection, we can reimplement some collection mechanism inside FluentBit. And what we did was to come out with a solution where this is currently your scenario, we don't have one, we are not here, right? Usually you are here, but you have multiple servers with multiple copies of the same agent. And we come out with this solution where now FluentBit can replace node-exporting metrics. If you want to collect metrics from your patent system, you can use FluentBit the same agent that you have today, and now we'll give you an experience, which is more clean, and you have to manage a list agents. So the way that it works, we have built a metrics collection for Linux for Windows, so the same collector in Windows, now we can script metrics from Windows systems and expose those metrics to your Prometheus endpoints or to your open telemetry endpoints. So no matter what you have, FluentBit is able to scrape the same metrics with the same labels or dimensions and give you a unified experience. When talking about the standards in the industry, it's good to understand what companies use, right? For logs, we all know that it's fluent that can historically process on structured logs in a schema-less fashion with a lot of processing in the middle. But also, we support metrics, right? We integrate with Prometheus, as I just mentioned, we can send metrics to Splunk, if you want, or we can send metrics to InfluxDB. All these features are built in FluentBit today. And from the Prometheus experience, we can do Prometheus scraping, so if you have one application exposing Prometheus metrics, you can use FluentBit to scrape those metrics. We can do not export it, as I just mentioned, but also the data collection of metrics in different operating systems. And when sending, exposing the data out, not that FluentBit doesn't index or store the data for a long period of time. It does only a short buffering and then ships the data or expose the metrics somehow. By using Prometheus remote write, which is the push protocol of Prometheus, or through the Prometheus exporter, which it open-ups an HTTP endpoint and can be discovered and the information can be scraped from there. Also, FluentBit fully integrates OpenTelemetry. OpenTelemetry is becoming the new standard to ship telemetry data across infrastructure, right? But OpenTelemetry is a protocol, is a spec, and on top of that specification, there are easy case to instrument applications. There's one project called the OpenTelemetry Collector, which FluentBit overlaps, but also there's endpoints that are able to receive OpenTelemetry. Fluent, I need to be fluent. I need to connect to all type of protocols, all type of standards, because that's what people need in the environments. And we support OpenTelemetry in the input, OpenTelemetry in the output. But you can do fancy things. For example, you can collect Prometheus metrics and send them out as OpenTelemetry metrics. We have all those layers of conversion internally. From a developer experience, we can extend FluentBit as a pipeline by using Lua scripting, Golang, and now we just ship Wassum. Talking about the experience of logging in Kubernetes, because I know that this is one of the biggest topic, it's always good to remember how this works behind the scenes. Kubernetes is just a group of computers where you have different roles. You have the worker nodes and you have the master, which orchestrate where applications get deployed. So imagine that if you want to do logging that this scale gets really complex, right? You're not going to SSH into a machine to try to extract information. If you have a pod that generates a lot of information, somehow you need to collect it and be able to send that back to a database so you can analyze the information. Usually a pod or a container that's running inside a pod will write information to the standard open interface. That information was going to be stored back by the container engine into the file system in a file, right? And that information gets encapsulated. So for example, if the same example of Apache Lock Message or Nginx, you know the HTTP request will get encapsulated and a JSON message with some metadata like the stream and the timestamp or the time where that message was generated. But that's not enough, right? If you look at the message, that's fine, but also you need some context. A, what is the pod name? What is the labels that are assigned to that pod? Where is that information? And that information doesn't live in the node, lives in the master server, which is here, outside, right? So how do we solve this problem? What we do is like, ideally we want to take the original information and augment that information with everything that give its context to something like this, right? Yeah, there is a lot of information for a single line. But when you're doing data analysis, where is your final goal? You want to query your data, not by the service name, but by some labels. A, show me all the pods that color equals blue and you want to get all the information from all the nodes. And the way that it works is deploying in Kubernetes, deploying flow embed as a demon set. Do you know what a demon set is? Okay, a demon set is just a pod that runs on every single node of your cluster, right? You see the flow embed in there and flow embed gets access to the logs of every single pod. And once it collect the logs, it goes to the API server and collects the metadata and then reassemble everything for you. This happened behind the scenes. You will not notice how this works, but it works and that's good. And once the data has been assembled together, it can be sent to your favorite fancy database for analysis. So you can imagine that there's a lot of complexity here, right, getting the data and sometimes you got data that is really, really noisy, applications that are really noisy. And now we're going to dive a quick, I know that we have a lot of questions by going to talk about a bit of architecture and internals. When looking at flow embed as a telemetry agent, you're looking for something that has an input, sub an engine and has some outputs. In the input side, and internally we can expose these as plugins so you can extend it. We care in inputs and we care about IODs, connectivity with UCP, TDP, UDP Unix pipes and sockets. The engine cares about buffering, data serialization, routing, retries, which is really important because when you hit the output section of a pipeline, when you want to send data to a destination, it's not like, oh, it works, it's always connected, network never fails. Yeah, DNS fails the whole day, right? So if you're going to send the data to an endpoint and you cannot reach that endpoint, what is the agent gonna do? Lose the data? No. You need to have some retry logic in place so the output plugin, when it tries to establish a network connection, format the data, it tries to deliver the data and if that is failed, it needs to tell the engine, hey, I failed, maybe I should retry in a couple of seconds. So you try to minimize the times that things can go wrong. So FluentBit is written by for reliability, right? Want to make sure that you don't lose data and we have buffering mechanisms to accomplish that together with the retries and the scheduling. Think about FluentBit as a, imagine now a data pipeline. Now we have more concepts in the screen. It's like, first we have the input of the source where the data is being collected from and it's not just to collect and send data. Usually what you want to do is to do filtering or do data processing in the middle, right? And we have the new concept around processors that were shipped on FluentBit 2.1, the previous version, right? And we'd allow you to process the data in the input and the output. And ideally, for example, you collect the data, you process it, you enrich it, maybe you discard data, those get converted into what we call events. Events can be anything, a log, a metric, a trace, and then those events can go to different destinations. And the most common use cases is that you send the data to two or multiple places. Yeah, if you want some example, it's like, we have users who send data to Amazon S3 because it's really cheap. They want to store everything in there. But everything that is more real-time queries, for example, they send it to Elastic or Splunk, but they don't send the whole data. They reduce the data. They apply a different type of processors here. So that means that you can have some real ability but also allows you to reduce your cost in the infrastructure and the software that is around it. Internally, we don't use JSON. We use a data-acceleration format that is called Message Pack. And here on the screen, you can see how we can optimize between reducing the number of bytes needed, but also what is more important when you're reading JSON, you don't have a starting and an ending point. For the computer, it's just bytes. But if you have a binary format, you can understand... Well, the computer can understand when a key starts, when the key ends, or where the value ends, or how many sub-keys you have. So you don't need to do parsing byte per byte. You can just skip around the array of bytes, which is more efficient and, of course, is fastest. When we collect the data, we group those events. They accelerate the Message Pack in the concept of what is called a chunk. A chunk is just a group of events or records that has attached the same tag. A tag is like a label. You can set your own label, which are used for routing purposes. And when the data is collected, existing a chunk, it needs to be somewhere. By default, it's in memory. And then you start creating chunks. In memory, you get more data in between before it gets flushed. So who can tell me what would happen here if I continue ingesting chunks? The buffer fills up, and what happened after that? Yeah, it stopped processing data, but before that, you try to use more memory, and your best friend, the kernel, will say, oh, you're using so much memory, so much, but it's time to die, kill. Okay, so can you fully rely on memory? No. Is it useful? Yes, you have to use it. But you need to play with some limits.  So memory is the fastest mechanism, but it's not persistent. What about if you're just running in memory, and you get a power outage? That data is lost. But also, yeah, it's faster, but you can be killed by the kernel. And then we have another mechanism, which needs to be enabled manually, which is in a hybrid mode with the file system. In file system buffering, we have the same concept, where we're going to start creating chunks in the file system. But if you're familiar with databases, the architectural databases, or how do they work, maybe you are aware about the concept of memory-mapped files. And how does this work? Memory-mapped files, okay, if you have a file in the file system, and you want to read its content, or you want to write data, you need to invoke a couple of system calls. Open this file, set in a position, I'm going to create a buffering memory, and now I'll read a portion of that data in my buffer. Those operations are really expensive if you're doing that 1,000 times per second. This is not just one type per second, this is 1,000 times per second. It's really expensive. But memory-mapped files is an operating system primitive at least in Linux and our operating system that allows you to have a reflection of a file content as a memory region. You incur in less system calls, your data is available right away in memory to be used. And we use this mechanism or concept where we call chunks are up on down. Chunks down means that the chunks are in the file system has not been mapped up in memory. But we're going to use the chunks, they are going up in memory. So if we want to control how much memory FluentBit use to avoid the case of being killed, you had to enable file system buffering, and this hybrid mechanism is going to play with all the chunks. So if it's getting to a limit, it's going to put certain chunks that are not being used at that moment down the file system and to control your memory. This is a very advanced technique that has been used by databases for many years. And you have that in FluentBit right out of the box. Today, FluentBit has been downloaded more than 11 billion times. And it's not wrong, it's not millions, it's billions. And this is insane. And 80% of these has been in the last 18 months. And now, why? Well, everybody's moving their workloads to Kubernetes. Every time that somebody deploy a new node in a Kubernetes cluster, hey, they need to solve login, they need to do a metrics collection, they need a telemetry agent. And FluentBit is the default one. So I would appreciate a thank you to our users, because yeah, this project has been around for almost eight to nine years, if I'm not wrong. But there's a lot to go. And today we are announcing the next version which is called 2.2. 2.2, we are improving all the processors that we have in FluentBit. We are extending this, because I didn't mention that FluentBit, I don't know if you are in the version two, but we support multi-threading. In the past, FluentBit was single thread, right? But A, in today's workloads, that's not enough. Everybody has more than 16 CPU cores. We need to take advantage of that. So we are doing a lot of training inside FluentBit and processing now can happen in different threads. That means that you get more power, you can process more data than previous version of a FluentBit. We got a new filter that is called this info that auto-paint information to your records, like hostname, operating system, kernel version. We got, I don't know, a hundred users that does this manually with weird scripts. Now we're just shipping a simple filter processor that does this right out of the box. The Docker metrics collector used to just support C-groups version one, now it supports version two. So it doesn't matter where you're running, if you're using Docker, we can collect the metrics from your containers if they are running on Docker. If you're using Potman, yeah, we have a plugin for Potman two that supports the same primitives. Configuration engine, if you are using FluentBit, maybe you're using the classic configuration format which is on the left. But recently this year, we launched a new support for Jaml. So if you have your Jaml tools, now you can start using it with FluentBit and you can have your more friendly configurations and you can do your GitOps things and make things more reliable. Prometheus MonoExporter, we just launched a new processor metrics collection for processes that are running on Linux. For every single process, we can collect the metrics besides the general metrics that we have before. We ship a new node exporter in the FluentBit for Mac OS. Why you wanna use this? Well, we have some companies who are deploying FluentBit in their employees' laptops and they want to collect the metrics from their environments. So, well, it works. And also Windows, you prefer operating system. Yeah, you can collect metrics from Windows too by using the same agent and you will have the same experience. Note, with collecting all these metrics, you can continue using your same Grafana dashboards, everything that you're using for visualization. You don't need to change anything. We are deprecating the old Grafana lucky plugin that was written in Gover Grafana. We're working with them and now we have a, well, we're standardizing that's official, the new lucky integration. Now we have a new plugin to collect Kubernetes events. The previous plugin was to collect due enrichment of the records but now we can collect a Kubernetes event for audit logs or anything around security. And we are keeping a little change that bring us a six-time performance improvement when you are changing filters for data processing. So if you're using two, three filters, which is normal, now you wish to process in one example, just to give you an example, 15 messages per second. Now you can, 15,000, you can do 93,000, which is a little improvement. So I hope you enjoy this. The other, I will give you 30 seconds to scan this QR code because we have a community member that right now is writing the new Fluentbit book for Kubernetes and we sponsor Manning and they will give us the early access for free. So if you scan this QR code and you fill the form, you will get access to the book. And the good thing that Manning works like, it gives you one chapter per month until the book's released. So you can start consuming the content, provide feedback before the book's finally released, so it will be here. Just take a photo of that and you can fill it later. Good? Okay, awesome, you took the photos. And in observability, try to be fluent, my friend. That's the way to go. Don't do a dropping replacement for everything because at the end of the day, it will be a problem. It's a limited data, it's really complex to manage and you need a strategy. So try to use the right tooling for that. Thank you. We have a few minutes for questions, but also, since this is the last session, we have more time of the record to talk. So if you want to chat or blame me around, we break something in your environment or if you need something else, please take the time. We have a microphone, if you want to do a question in public, that works, thanks. Hi, thanks, great talk. I want to ask, so I think you had partially already answered this question about overlap between FluentBit and OpenTelemetry Collector. You mentioned something about being graduated projects more mature, possibly. I want to ask also related question, did you have any comparison of performance between FluentBit and AutoCALL? Yeah, so OpenTelemetry is a new project to aggregate data that relies from the OpenTelemetry specification and framework. Right? By experience, FluentBit was created in 2014 and has been fine tuned for performance over eight to nine years and it's really in the C language. Our vision has been always like, you need to process the data without starving other applications without harming the server. So if we compare with OpenTelemetry Collector by the feedback that you get from the users, if you put the collector on every single note of your machines, you're going to end up paying for extra CPU cycles, extra memory that it's not needed. If you want to do tracing or maybe aggregation outside of the boxes, I think that's pretty fine. But our users said, hey, you know, OpenTelemetry Collector is really heavy compared to FluentBit and yeah, you have to use what is best for you. Right, but you don't have any specific benchmarks. You haven't run any. Yeah, we're going to launch some benchmarks because people has been pushing for that. We're going to compare a vector. We always didn't want to get into that because it was kind of a waste of time for maintainers. But I think, yeah, we need to do it because we know that FluentBit is the most green project in the CNCF in terms of power consumption. Awesome. Yeah, we're releasing FluentBit 3.0 next year in Paris with QQ in Paris. So we're going to have all this information together. Awesome, great, thanks. Thanks. I have a question around support for Kubernetes events. So I think you went over the input plugin for getting the Kubernetes events, but I just wanted to know about the output. Do you support the existing plugins to output the events to any existing plugins, or we'll have to write new plugins to export the events somewhere else, basically? OK, the question is, you have created a new Kubernetes events plugin that connects all the events, but now how I can send them out? So FluentBit will get the events, right? Like it will scrape the events from the API server, right? Like KHCP server. But we have a custom plugin that we use today to write logs, like pod logs, somewhere else. So can we use the same output plugin for events as well, or there will be a different output plugin that we'll have to write for events specifically? Yeah, you can use the same, the same one. I think that FluentBit can run as a demon, set a site card, it can connect to any remote endpoint, and can send the data out or to a local file without any major problem. OK, thank you. That's what I thought. Thank you. Thanks. Hey, how's it going? First of all, great talk. The questions I had were first about transforming data. So because, so in open telemetry, because there's sort of a standardized format for telemetry data, you can sort of like, they have schemas and things of that nature, right? And I'm guessing I'm new to FluentBit, but I'm assuming there's not something similar or analogous in the FluentBit ecosystem. Is that an accurate understanding? Yeah, and the main question is around how do we accomplish data transformation and processing? Fluent historically has provided us such features to enrich or to collect or filter out data for years. Now, we didn't dive in that today because sessions are a bit shorter right now, but tomorrow we have one session which is most focused with demos around data processing with logs. So maybe if you can attend tomorrow, you will get all the details about, oh, how do I do processing? How do I remove keys, add keys? Or how I can, I don't know, do fancy stuff like we have a SQL string processor inside FluentBit so you can run SQL inside FluentBit too. There's a bunch of things that are really interesting, but yeah, if you can join us tomorrow, it will be great. That's wonderful. And then the second question I had was around, I guess it's a similar idea around aggregation. So for example, if I have services, they're generating tons of, tons of, tons of errors, and maybe they're not using like a burst filter, logfoja, burst filter type situation, is it possible for us to use like a FluentBit transform to sort of aggregate, turn that into a metrics counter and then potentially drop the underlying log line itself? Yeah, so how we can reduce logs by taking advantage of the metrics features? We have one filter and process that is called log2metrics. So what it basically does, it gets a bunch of records or events, right? And you tell them, oh, this is a key that has the important value. This key is a value, this is a metric name, description, labels, and for all of them, we generate a counter, a gauge, so you can reduce the data from that. Usually used with web servers, so it's there already. Awesome, thank you. That's covered tomorrow too. Hello, thank you for a nice talk. And with all of those nice features, what room and what reason it leaves for FluentD? FluentD, where's FluentD today? FluentD is written in a language that is really hard to scale for today's needs. It's written in Ruby, but FluentD is running everywhere. It hasn't gone away. I would say most of the changes today in FluentD are around maintenance, security updates, but everything that is innovation around metrics, traces, performance, everything is, our focus is in FluentD mostly. So there's not much movement in the FluentD side because the architecture that it has, it doesn't scale for today's needs. So pretty much it means that it leaves it in maintenance mode and for everything you start using, just use FluentD. I would say that FluentD is the next generation of a Fluent ecosystem. For example, if you take, not because I say this, but if you look, for example, the journey of Amazon Cloud, AWS, Google Cloud, Microsoft Azure, all of them were used to use FluentD in the past and all of them migrated to FluentBit. So imagine that they have a different need, a different scale, and yeah, they're using FluentBit and contributing back to FluentBit. Actually today in KubeCon we have maintenance from Google and Microsoft, too. Got it. Thank you. You're welcome. What is the name and time of that talk tomorrow? Sure. Let me check my calendar. Or just the name. Oh, I forget the name, man. Oh, it's Login 430, Login deep dive and best practices. Okay, thank you so much. We're going to continue the Q&A of the stage. Thanks.


Thank you. I guess this is a seamless transition from fossil fuels to renewable energy and I guess a day like an uncomfortable a day like today Reminds us of the urgency of that Transition at least it does for me So I presume this audience does not need much of an introduction to the solar PV industry We all read about it a lot in the papers For those of you who are coming to Stanford from other parts of the US or other countries Also chances are you're going to read a lot more about it when you get here Not only do we have a couple of the major solar companies in our backyard? But perhaps equally important Many of the corporate heavyweights in our area have recently made and continue to make major investments in solar power that includes companies like Google Apple and also on Stanford University that decided fairly recently to make a major Investments in solar to satisfy the electricity needs here on on campus. Okay so Perhaps here's a graph that I think Everybody has seen in some form or another That's sort of the title of the talk the rather phenomenal growth in solar PV worldwide over the last 15 years And if I hope also the ones in the back and sort of did see the different colors clearly Basically on the bottom you see Europe which took an early lead in this but has leveled off recently But nonetheless, this is a very steep very convex curve in which basically the Americas And that means largely the US at the moment and Asian countries are have picked up the slack that has been created Okay, so here is Just to reinforce this a little bit what you see on the left are annual installments of new capacity in 2014 alone You see the US has sort of moved into third place there was about six gigawatt that accounts for actually about one-third of all new Capacity installed in the US last year so solar accounts for that at this point already Countries like Germany to have slowed down and we can sort of talk about this a little bit why that's happening But perhaps the biggest story other than the US is China which in the past has been a major producer of the hardware in particular the solar PV modules The panels if you want to those that country now also is Installing them at an increased pace in the past they have been largely producing them and exporting them to other countries They still continue to do that, but now you have them also as a country that install solar pop, okay? So what I would like to talk to you about in the next 20 minutes or so is the question. How should we interpret? This growth story solar is still small In terms of electricity generation all together if you look at all Electricity generated, but the growth rates are pretty phenomenal and then the natural questions are what has been? what have been the drivers of that growth and is it likely to continue if we sort of extrapolate from what we know at this point That is is this trend sort of here to stay? So that's something I've been working on over the last couple of years And I want to give you sort of some a feel for the work that we have been doing at the business school in this area so Several sort of what you may call drivers or Explanatory factors are being mentioned frequently in terms of what's behind this growth Perhaps first and foremost Technological improvements and cost reductions really at every level of the value chain from modules To of the cost that are being incurred in installing solar systems Including labor hours at the very end that it takes Companies have reorganized themselves in this industry that would probably take me a little longer to to explain But there is a lot in the way of vertical integration of companies that before sort of operated separately Another aspect is financial innovation. We're seeing more and more a model in which the parties that are consuming the solar power The off-takers if you want to are no longer the owners But we have third-party ownership And many people or companies nowadays lease their solar panels And that has led to a new sort of set of innovations that ultimately also have helped to reduce The cost of capital in this area, okay? And finally and this is really what I want to focus on the most in this talk For the US in particular, but also for some of the other countries, notably the European countries Public policy support in the way of tax incentives so in 2009 US Congress authorized a 30 percent Investment tax credit What that basically means is if a company or an individual has a tax liability You get a 30 percent break or refund on this if you make an Corresponding or an eligible investment in a solar facility In addition, there are ways to write off these Investments in a faster way so an accelerated form of depreciation Which once again lowest effectively the cost and those are the two main things at the federal level and then in addition We have seen in different US states Really movements in the way of renewable portfolio standards, which basically provide incentives coders if you want to for renewable energy And related to that here in California the California solar initiative Which was basically just a cash rebate to new investors in solar all of these things have Contributed at least in the US but also similarly in other countries to the boom in solar power so the interesting thing then is sort of to sort out what are really the major drivers here and In particular when it comes to the federal investment tax credit one thing to note is this has a Sunset provision such that at by the end of 2016 the Investment tax credit for corporations is scheduled to go down from 30 to 10 percent And for individual homeowners so for non corporations is supposed to go away in its entirety So as you might expect the solar industry is lobbying Congress Very actively and saying you know don't let this happen So the question that we have sort of have been looking at and I want to share with you a little bit is what would be the impact if That really does happen and what are also possibly alternatives To what's currently on the books in terms of the tax laws So in particular I want to look at three questions here Where are we in the current environment when it comes to cost competitiveness of solar? And I want to sort of look at this at a slightly more granular level here going by Individual states I have picked a sample of five u.s. States which collectively account for about two-thirds of all installations in the u.s And then also by segment So I mentioned earlier some of the big players here those typically invest in what's called utility scale facilities But much of the growth actually has come either at the commercial level where individual companies put solar Panels on their rooftops say of their warehouses or their office buildings and of course the last segment being the residential segment Individual homeowners and individual rooftops. Okay, so let's look at these separately and then also by state So that will sort of provide a if you want to a grid of measures of cost competitiveness So that's sort of an assessment that I'm going to give you in a moment. Where are we now? Or where are we going to be very shortly? and then the question really from a public policy perspective if Congress were not to change its mind and Let's the investment tax credit go down from 30 to 10 percent What would be the impact on cost competitiveness at that point in time? And as the very last thing if I get to it on time Perhaps sketch an alternative scenario that would rather than stepping this down in one big step gradually Reduce that public support that investment tax credit hoping that in the intervening years the industry continues to innovate and reduce cost And we would sort of maintain the current status of cost competitiveness That's sort of the idea and we can sort of quantify this You know relatively easily once we have sort of the the first pieces in place Okay So what's the way to measure cost competitiveness? There's a metric in the industry That's not used just for solar but really across different Energy platforms in fact one of its advantages is that you can compare say the energy Generated from say electricity generated from a nuclear power plant versus a renewable source versus a coal fired power plant and what you do is You basically calculate a unit cost measure which in this industry is called the levelized cost of electricity or also levelized cost of energy so roughly the way to think about this is an Entrepreneur a company that asks itself should I invest in solar or some other type of electricity generation source What would I need in overall revenues? Per kilowatt hour over the whole life cycle of this facility say the next 25 years So that at the end of this process, I am breaking even on this investment. It's a decent investment for me Okay, so Basically what you're comparing is a stream of revenues at this levelized cost in your that must cover And you get a stream of revenues at this levelized cost and that must cover your actual Cost in terms that you are incurring both initially when you make the investment and on an ongoing basis so Conceptually you can break this into three components one being the fixed operating cost for solar on an annual basis Maintenance replacing certain parts that are giving out over a number of years The big component is this unit cost of capacity. That's basically Your overall Systems price that you're paying initially and you must sort of distribute That's where the word levelized comes in levelized that cost over the next 25 or 30 years Whatever your assumption is and then the third thing that we need in those types of calculations is that are the tax considerations Because that's where public policy investment tax credits and all these kinds of things come in So fortunately, you can represent this in a somewhat separable fashion where you can take this tax factor Think of this as a markup somewhere around say 1.3 for conventional but much much smaller for solar that sort of Acts on this cost of capacity Okay, just to give you a flavor of this So here are some numbers This is I'm already fast-forwarding the tape a little bit to 2016 be record because remember 2016 is the year that things are supposed to change and This is my grid in the rows. You see that five different states and in the columns the three segments and Within each cell if you want to I have three numbers one is the cost the levelized cost of solar on a per kilowatt hour basis in The current environment or in 2016 if we still have a 30 percent investment tax credit So that's where the subscript 30 is under the LCOE, okay Contrast this with what I call the comparison price That's sort of what solar needs to beat in order to be cost competitive and then the third Column has what this levelized cost at the end of 2016 would be if Congress doesn't change its mind and the investment tax rate. It really drops off to 10% Okay, so what do we get? Well, let me first say the comparison price differs greatly across the three segments and the reason for that is simply if you're building a utility scale facility Say a utility itself builds it pretty much what you have to compete with our whole sale prices for electricity Those of course are much much lower than retail prices Conversely if you're a company would you have to and you ask yourself should I put solar panels on my rooftop? The relevant comparison is well, what does my energy service provider? Possibly the utility charge me our business on average per kilowatt hour, so I need to beat that Okay, that's still lower than what individual households You all will be paying when you when you're here I guess Stanford takes care of Heard of many for you, but it doesn't for me So I pay roughly 16 cents 16.5 cents per kilowatt hour here in California That's sort of the retail average retail rate in PG&E Pacific gas and electricity territory. Okay So What do we take away from this? Well in the commercial and residential segment solar is in the current environment That is with the current incentives. It is pretty competitive in many of the states New Jersey is always difficult. We'll talk about New Jersey separately perhaps in a moment, but in the others. It's pretty much There say if you look at California Commercial, you know, that's a sizable difference We're sort of projecting at the moment a levelized cost of 10 cents But it costs the business on average 15 cents at the moment So that's part of the explanation why we have seen this boom It makes sense for a lot of parties to do these kinds of investments Okay, and An exception to what I just described happens over here on the utility side There you see if I compare the levelized cost at the in the current environment Against the comparison price that is wholesale prices for electricity Basically, we're out of luck Generally the comparison prices in all of these states are lower than our calculations For what solar accounts for at this point So but nonetheless, we've seen phenomenal growth in these markets. What accounts for that? Well, that's where we get to the state level incentives States have been running their own programs as I mentioned before renewable portfolio standards Which if we get back to the example of New Jersey have become at some point incredibly valuable But that was really sort of a particular thing to New Jersey at some point okay now What would happen if once again the investment tax credit were to drop off and go from 30 to 10% These are the numbers in red and I've marked them in red just to indicate for you and you can verify it immediately There we're basically underwater across the board by a Precisable margin so the conclusion is Even if things improve a little bit here in the in the coming years Costs are going to fall a little bit and that's already baked into those numbers for 2016 if Congress doesn't change its mind Many of us and I agree with those assessments are predicting that there's a serious cliff for the solar industry coming Unless the states were to step in and increase the state level incentives for for solar in this environment So that leaves the question and really What to do about this? is there What we have is a overall a dynamic in which things have been going a lot better for solar costs have been coming down Congress at some point in the US and also in other countries Jumpstart at the industry It has worked out exactly the way it was intended but the timing is off a little bit here because At this point the cost reductions that have been achieved are not yet sufficient to sustain the industry Without the public support. Okay, so that's where we are on this Let me spend a moment here talking a little bit about Future cost reductions, so if we do not just go to 2016 But we're mapping it out try to map it out for another say 10 years all the way to the mid to the mid 20s Can we do that? Well, that's something ultimately sort of a forecast here Looking at past observations and past improvements that we have to do if we want to sort of inform policymakers on this And that's sort of our goal with this line of work So this here is a well-known chart in the industry. It was first presented here at Stanford in a seminar in 2011 by Dick Swanson who was the founder of Sunpower one of those solar companies here in our backyard and all he did was graph really plot prices against Production volume in this industry. So think of this as total megawatts installed and both on both prices and Quantities that is megawatts produced are on a logarithmic scale But the thing that's standing about this curve is It fits beautifully as you can see in its logarithmic form. It's almost a straight line And there was this little blip here that was typically attributed to a Change or a shortage of polysilicon a number of years, but then things got pretty much back to that curve very quickly So when that was presented here in 2011 you know people were saying this is spectacular You know we came from 33 dollars per watt to a dollar to a dollar and 81 in just Those 30 years, but this got to end. This has to level off well Here's what happened ever since Here's pretty much the curve up to 2010 this was the last graph and this is what has been happening in the last Three to four years if you by now we also have some of the 2014 data And this has sort of held steady in the first part of 2014 and recently has sort of fallen off again But the important thing to take away We have actually now beaten sort of this 80% learning curve So things have gotten even faster Than what was predicted even though people were worried that ultimately this industry would slow down So that of course raises the question. Well, what's happening here? another thing that has been happening is there has been a lot of Entry into this industry from China Largely which have Chinese players have really upped the capacity in that industry And so people have been trying to say well, perhaps those price reductions are not so much a question of cost but more a question of Price pressure because this industry expanded too quickly and people got into to Had sort of two rosy expectations in terms of making those investments so that's something that in terms of the research we're trying to do here is to Disentangle this and try to really divide to what extent are the prices that we have seen a Consequence of continued cost reductions and to what extent is this really a function of Basically excessive capacity for the industry for a number of years and If you do that you basically get sort of a new line here, that's the green line That is a prediction of what we call an economically sustainable price This is what the industry would have charged based on the cost figures that we have examined If they had not been sort of too much optimism and people wouldn't have jumped in too quickly into this industry, okay? So you put all of this together And you do something similar over on the so-called balance of system cost what I just talked about was just the module part and You get to the following consideration in this and this is then where I'm going to wrap up There is Good reason to believe that cost not just prices but also costs are going to continue to fall at a particular pace That's pretty impressive But as I tried to indicate early on by 2016 we're not far enough on this learning curve So this raises the question could you do something more in between that is could you say well in 2016? We're not going to step down the investment tax credit from 30 to 10% But we're going to go somewhere in between my red line here And then you would play this one more time for the period 2020 to 2024 and Then ultimately you would go to zero So the calculation here is in terms of taxpayers and Congress as a proposal You give the industry a little bit more in the next five years when it really needs it But on the other hand there are reasons to believe it doesn't need all those subsidies the continued subsidies at 10% investment tax credit and Accelerated appreciation forever because the tax the tax code at the moment says those remaining subsidies will be in place forever So there's in my mind a possibility of a deal here to be made where the industry gets a little bit more and now when it Needs it, but you're cutting it back to zero in the very long run and that's works out if you do the numbers I think Lee showed to me that I'm sort of out of time. Let me just leave this graph here I know this has a lot of colorful bars looks a little bit just like the physics experiment, but think of it this way if on the Red line we see what the investment tax credit these again levelized cost for California at a utility scale This is what would have happened if the 30% investment tax credit had remained in place the alternative put solar Basically makes it uncompetitive for a number of years and the alternative path that we are sort of sketching here Would basically mitigate this.  Wholesale prices in the state of California, which basically those types of investments would have to be would have to be Most importantly the projections for 2025 if at that point you took all of this away We're projecting that in another 10 years Solar at this scale would really reach great parity. That is if you took all the incentives away both federal and state It should be able to beat those prices that are forecast for 2025. Okay, so that was a quick tour of some of the work that we're doing over at the business school and Largely as you could see a cost policy and economic angle to renewable energy So I'd be happy to entertain some questions Two questions. I guess I stepped over time. Go ahead They're wondering under a ICS phase scenario If if I had the magic wand and I got to choose as I would always go for basically what the California Solar initiative did which was cash rebates. I think those are the cleanest to supplement these things Obviously a short answer to a complicated question over there That's a good point and so we have in all of this sort of basically been I've been listening to my engineering colleagues 25 years is sort of the usual Framework that but I've also heard people say that there is after 25 years likely to be still a considerable residual value That makes the numbers a little better, but on the other hand from an economic cost perspective Because you discount the future You know what you get in those last five years between years 26 and 30 isn't really worth all that much anymore But nonetheless noted this can change things a little bit on the margin And I've heard some people sort of say when things looked a little dire that they were banking that Ultimately it would actually be longer than than just 25 years One more Good Yeah, and have to get out of that fan here. Yeah I mean Yeah, good point obviously I've been focusing on the US California in particular because California has been also Proactive and that's why we've seen a lot of growth here different countries have adopted different policy support mechanisms Germany the feed-in tariff that was mentioned a moment ago Spain had those also for a number of years I think there's an active debate, you know, which of these mechanisms are more effective But one thing that was clearly seeing in Germany at the moment when I showed you the second slide Germany first jumped on the gas pedal now really went off it because it cut back those feed-in tariffs and The consequence was Germany has really slowed down now in terms of these things So basically in all the countries in which we have seen sort of fast growth over the last couple of years There has been some kind of not necessarily a tax mechanism But another policy mechanism in place solo on its own even under ideal conditions does not seem to be able to do this yet Okay


Many of us are now teaching from home because of the pandemic. Having an adjustable mic stand is essential for recording lectures or making videos. The microphones are so sensitive that you really have to place them in the right position for good audio. The Blue Snowball is a basic plug and play microphone that connects to your computer with a USB cable. This microphone comes with a small metal stand and you could use it but it didn't work for me. I didn't have a tall mic stand but I had a camera tripod. I was looking for an easy and inexpensive way to mount my Blue Snowball microphone and pop filter on a height adjustable stand. In this video I'm going to show you how to attach a Blue Snowball microphone to a camera tripod. It's very simple. All you need is a cam weight cold shoe mount with a 5 eighth inch screw adapter. This is a standard adapter that is used to mount a microphone to the top of a camera. Unscrew the original metal stand from the microphone and insert the adapter screw and tighten it. Then attach the tripod mounting plate to the other end. Once you're done put the mounting plate back on the tripod. There you have it. An easy and inexpensive option for a height adjustable microphone stand. Hope you find this useful. Thank you.


Hello everybody! E here. Welcome back to another Retro Review, and once again we are doing Dean Koontz. Today we are talking about his novel, LISPERS. This book is about a woman who was attacked and assaulted by a man, and then he supposedly dies, he's supposed to be dead, and of course he's not. Dean Koontz has done this plot, I don't know how many times. I think this is the first time in this one, this is the first time he did it, was with this one. Me and Deely have pinpointed the first Golden Retriever book, I just want to set your heart to ease this kid, anyways. But we pinpointed that, but I think this is the first time that you're dealing with a killer who is supposed to be dead, but keeps coming back somehow. I don't remember much else about this book, other than the horror element, which was cockroaches, and it seemed a very weird mixture of the serial killer and the cockroaches. It didn't fit for me, even though he explains it in the book, it felt tacked on, if that makes sense. It felt like an afterthought, more than a fully realized, thematic thing, I guess it is.  Not everything has to have a purpose, that's not what I'm getting at, but I look for a little bit more when it comes to things like that. It is icky, don't get me wrong, it's icky, and so are the sex scenes.  I can't remember if it's this one with the ribbons of semen. I think it is, either way he likes to write ribbons of semen unspooling, it's very... That's more disturbing than the cockroaches, if I'm honest. With the book being as long as it is, I do remember feeling like it was never going to end, but I did want to finish it. I believe I ended up giving it three stars. If looking back on it now, the farther I get away from this book, the more I don't like it. There's also, yet again, another bad guy that has mommy issues, and I know Dean Coons had problems, he had a terrible mother. She abused him all throughout his childhood, and it's odd that his villains, I guess one of the things, if you want to go psychological with this and you want to deep dive into Coons, I think maybe he's writing these characters not only from a place that he knows, but a place that he might have gone.  But this time, I do remember this time being a little more uncomfortable with it, a little more author intrusion than maybe before. Again, I am looking at this book, this is a retro review, I'm looking at this book at least a year removed from reading it, and I've also read an awful lot of other Coons. So if I am mistaken in any of these things, or if you guys would like to have a respectful conversation about maybe why you feel I'm wrong about the themes or these things, definitely do that down there in the doobly-doo. If you're rude, I'll just delete you, that kind of thing, you know how we do around here. With this one, do I recommend it? I don't know, it's one of Coons' longer books and the longer his books go on, the worse they become. He uses a lot of filler, like just driving around, he uses sex scenes. It says a lot of uncomfortable material that's not supposed to be uncomfortable.  That's the best, that is the best way that I can put it. And that's one of the things that I'm noticing more and more, and I'm glad that he finally got away from it. Now, for those of you still hanging around, I want to make this video a little bit longer. I want to discuss something else as I build up to the servants of Twilight that I'm going to be reviewing here on the channel and me and Dealey will be reviewing later on on our individual Goodreads accounts. But it's the progression of his ideas. It seems like every single idea beforehand has an element that leads into the next book. This one has an overview, not really an overview, but there was a book that he did about reincarnation called, well I guess that's a spoiler. But that's not a huge spoiler. I think the theme of it is, oh man it's going to bother me because I already said it. But the mask has a theme of reincarnation. And then coming into this one you have the, there's a bit of reincarnation in this one also supposedly. And that's what one character thinks anyway. You have an actual book about reincarnation and then you have a book about maybe reincarnation. Stephen King does this also. He has the dark half and secret window, secret garden. And those two books complement each other as different points of view where you have the supernatural aspect and you have the could-happen aspect. And I've always loved that about King. He'll usually write a novel, not usually, but he'll write a novel and then follow it up with a novella that is thematically the same but different story wise. Or that kind of thing. With Coons, I'm starting to see the same thing. In the House of Thunder there's a deserted town and then he wrote Phantoms. In, let's see here, in The Servants of Twilight which we will talk about soon there is a mention that all I'm going to say is Rats. And then right after Servants of Twilight he published Darkfall, which the main antagonist in that book is Rats. That's all I'm going to say about that. I mean, with the, I'm trying to stay away from spoilers here. I'm trying to stay with the stuff that is actually mentioned on the, either on the dust jackets or the descriptions or whatever. The thing is, I can't remember all the descriptions. And I want to talk about this stuff. So, in Darkfall it's not just rats. And there's another thematic quality to The Servants of Twilight that leads me to believe that he was writing one book and he said, oh, hang on, let me turn around, let me write this down, this idea down and I will, I will expand upon it in another book. I know he does this because he said that's how he got the idea for Odd Thomas. He was writing something completely different and Odd Thomas is like, I see ghosts, they don't talk, I don't know why they don't talk. So he wrote that down and then he finished that book and then he went on to Odd Thomas. So I know he does that. But it's cool to see, even though I didn't care too much for this one, it is very cool to see that you can see the, maybe not the full architecture, but you can see at least some of the plans that are going into the next book. And if nothing else, that is one of the best finds I've had so far during reading Dean Coons' books. And I plan to go back and make an entire list of all the books to seemingly lead into one another. Now there are some time continuities, like there's a long time between the House of Thunder and Phantoms, but he rewrote the House of Thunder just before releasing Phantoms. So, sorry, he rewrote and re-released the House of Thunder just before Phantoms came out. So that's where we are right now. This is a more in-depth retro review. This will probably be the, I know this is the last retro review. I'm all caught up on the back catalog.  But yeah, have you read Whispers? I'd love to talk to you about it. Again, if you disagree with me, that's fine. I don't care. Just don't be rude about it. Leave your comments down there in the doobly-doo. But until next time, I have been E, you have been U. This has been another Dean Coons retro review. I'll talk to you guys later. Bye-bye. He's bringing me a Dean Coons retro review. Big dummy. Oh, and for you guys worrying about the stuff disappearing back here on the wall, it'll eventually come, let me get my ding-dong out of the way, it'll eventually come back. But there's a holiday coming up in holidays and the whole reason I did this, you will see. Did this is so that I can prepare and have space to do other things. Ooh. Bye.


Hey guys, it's Tate, A.K. The Foot Accountant. Welcome back to the channel. I wanna talk about what's coming today on Thursday in FIFA 21 stuff we might be able to expect from the market with rewards, of course, being today. Also, content coming today, we'll talk about that. First, I wanna take a quick look back at yesterday and just, again, just remember how that was one day for the books. Yesterday, Wednesday with the whole, the foot web app, that whole issue going on with the debug mode with being able to see the settings behind that. That was insane. That was crazy. EA have not said anything about that as far as I'm concerned. I really don't expect them to say anything about that because that for them is just a flat mess up on their side of things. So we'll see if we have any other remunerations about that today from EA Sports. But again, it is Thursday and that means rewards day. Of course, if you are interested in completing that Doherty SBC as I probably will be doing for the Spurs First Owner Club, I'm probably gonna end up getting hard and Doherty and the team, both of these guys here in the club pretty soon just for the Spurs First Owner. But that was our St. Patrick's Day content yesterday on Wednesday. I don't really think that we're gonna be seeing any other content released around St. Patrick's Day after the fact. I'm also kind of, I don't know if I would say impressed, but we have a legit like hub here with like a lot of graphics and a loading screen for St. Patrick's Day, which is, I mean, technically a one day promo, right? So I'm not sure if this is gonna stay in here for a while or if this is how EA is gonna try to, I guess, entice us to be hyped about the content on the game. But what we're really, really hoping for today is a loading screen for foot birthday because again, tomorrow, Friday, is the legit anniversary of FIFA Ultimate Teams first day back in 2009. So it's just written in the stars that foot birthday should be coming, but unfortunately, it's looking like right now that hope is pretty glimpsed. So today is our last chance and maybe getting a glimmer of hope of that promo with some sort of loading screen, some sort of pat code being added as of right now. There is nothing. So right now we are on thin ice and we are not seeing any hints for foot birthday, which could mean another very quiet weekend on FIFA if that is the case. Hopefully that is not the case, but we will kind of, of course, get involved with that when the time comes. Now I want to talk about two major items today. I already mentioned them. First one is Player of the Month, League One, and also the Europa League Road to the final games that are being played today on Thursday. Two big, big things coming today. Now first thing I want to look at is where you can find the announcement for League One Player of the Month. This website or this Twitter page right here at UNFP always tweets out the winners of the Player of the Month's pronto, like right away. And I want to kind of note this time, right? This Bulaia was tweeted out a month ago on 1.04 pm, which is 6.04 pm UK time. So they tweeted out this stuff actually after the SBC was loaded into the game. Now I don't know if that's going to be different today. Of course we have got the nominees, Ben-Yeder, Mbappe, and DePie, but we are expecting the League One Player of the Month SBC today. Today that SBC should be dropping. So that would be another big time SBC that could be coming into FIFA all the team today. Of course with a lot of market movements. Now of course watch like Mbappe's special cards. I would watch DePie's special cards and Ben-Yeder as well. If the guys, if there's panic selling any of those, the guys that do not win, for sure I would think you'd see a small bounce back on those. Especially if it's like a Ben-Yeder headliner or whatever. But that's one sort of big part of content that we could see coming today. And then also I forgot to mention this right away, but Icon Player SBCs. Now we have had Balak, Costa, Schmeichel, Nedved, Puyol, and Clivered all released in the past two weeks. Two Thursdays in a row in the past two weeks we have had Icon Moments Player SBCs. I really, really hope that this trend continues. EA Sports, if you would please drop another set of three Icon Moments SBCs today that would be fantastic, right? Now I'm kinda hoping this happens. Hoping this comes out today. You know it's kinda like EA for the last two weeks has been operating on what they used to do for Icon SBCs. They used to do like a throwback Thursday concept and hopefully that is kinda what they're doing right now. So we possibly could see three more Icon Moments SBCs released today. And that would be really hype if they did that. Again, it's a lot about SBCs today, right? Play them with Mbappe, big time SBC coming out. Maybe some Icon SBCs. I would expect some sort of like maybe a pack supply SBC as well. And then we will get a new set of Marquis matchups SBCs coming out today as well. So some pack supply for everything that is in packs today with the normal Marquis matchups. Now besides that, all the things that are happening today we've got rewards of course, and we've got Europa League Road to the Final. We're Europa League Road to the Final with this game right here being the one that everybody has their eyes on. That is right. We have Milan versus Manchester United and this Kessie card is up. This guy's 480,000 coins at the moment. I think people are really expecting Milan to go through. Now of course, it's a very, very close one, right? First leg was a one-to-one, but Milan have that away goal advantage, I believe. And now again, this game is being played at Milan. So depending on how this game goes today, you're gonna see a lot of market movements with this Kessie card with the Rebetch Road to the Final and with Rashford. Now the odds have kind of flipped from where it was the other way around. Heading into the first leg, you had this Rashford card that was chilling at about 1.2 million coins and you had that Kessie card that was chilling at about, I don't think it's like 400,000 coins or 420K or something like that. And now this Rashford is down about 100K. He was lower and Kessie is up like 50,000, 60,000 coins. So people are favoring Milan right now. So what I would 100% do today is keep an eye on these Roads to the Final items because they're gonna be crazy to trade with. Now, of course, we have got four games happening early today. Four games at 5.55 PM UK, which would be 1.55 PM my time with the time change Arsenal, Olympiaco. So you've got Road to the Final, Obamieng. You've got Tottenham in there, of course. So Road to the Final, Sosoko. You've got Roma and Shakhtar, Donetsk in the first set. So you've got Road to the Final, Perez. Then you've got Milan and Manchester United, who we just talked about. And then that's technically the only live cards that are in the second set of games because, of course, Promes and Kubo are not live. So the live items are affected the most in the first three games today. That will be with Obamieng, Sosoko, and the Roma right back, Mr. Bruno Perez. So keeping an eye on these items today, right? If a team is a heavy favorite, I'm not expecting too many price fluctuations. This Obamieng is way high as it is. Now, again, there is gonna be a draw involved on Friday, I believe, for the Champions League and for the Europa League as we head into the next round of the tournament. So there's gonna be more price fluctuations on these Road to the Finals based off of the teams and the draws that they get for that next round. So that's gonna be something that we keep an eye on. But this stuff is really gonna come back into perspective today. Really gonna start getting hyped again and all of that. So 100%, we'll be doing that on stream, looking at those cards live during the game. So that is one thing to keep an eye on today. That's where a lot of the hype is going to be today on the market. Also, obviously, since it's Thursday, Rewards Day, the hype is gonna be on the rewards. Right now, team week right now, I was trying to flip these guys a little bit earlier. I'm actually taking some of the losses because these guys have gotten rare, but their prices aren't going up when they're getting rare tonight. They're literally just chilling, right? So I'm taking a lot of tax losses. Lautaro, I had a couple, even 450. I was hoping to get out at like 470, 480, and he just keeps getting undercut, which is interesting. I think the whole timeframe yesterday and Wednesday with the UEFA Marquis match-ups being released late, might have hurt these guys a little bit in terms of going back up in price. But of course, these guys are gonna get supplied a lot today with rewards. I'm really curious about this Waman card because if you're awake for rewards today, maybe when you're watching this video, 100% watch the supply on Jota, Martinez, De Bruyne, Tierney, and Waman. Because again, those are very, very meta cards that a lot of people wanna use in their teams, especially this guy, 14,000 upvotes, man. This has to be a record for one of the most highly-upvoted players in footbin history in the short amount of time. He's being hyped up by a lot of other YouTubers and just in the FIFA community, the five-star skills and the 98 pace, and honestly, 99 agility, 92 dribbling, 90 finishing as well. This card's kinda cracked. This is giving me crazy, lasano, super sub-vibes if he is really, really that good in game. So, since there's a lot of demand here, he's gonna get packed a lot during rewards today. Watch that guy for a lot of undercuts and being packed from Team of the Week packs, and then as people list those up and stuff, potentially a big time to buy after an hour or two or three hours after the rewards do drop this morning on Thursday. Same thing with a lot of those meta cards that I was just mentioning, right? Jota, De Bruyne, Laptaro, and Tierney. One thing I would take a look at is SBC fodder informs, right? This goalkeeper right here, he's a max price of 30K, so I'm not sure what EA is doing with this, but that is an error on their part. Again, another reason not to like price ranges, but Weghorst and Coopminers are both basically discard values from the cheapest 86 rated informs in the game and think about what we have coming out today. Mbappe Player of the Month, or whoever it is for League One, probably gonna require some informs, right? If there are more Icon SBCs, probably gonna require some more informs. And of course, as we head later into this game in the next couple of weeks, informs just rise out of packs anyway. Definitely keep an eye on these cards today, whether you're buying close to discard ones down here, like for these 81 rated cards, as close to about discard as you can get, or if you're buying 84s as close to like 20, 25K as you can get, and then 86 is maybe in like the low to mid 40s, 100% keep an eye on those cards today. They're gonna get supplied during rewards listed up, and especially on open bid, they're gonna get packed. And with more SBCs coming, that could be a spot of the market where you wanna watch today as well. Same thing with SBC fodder, right? We talk about supply and rewards day, 86 has went down a lot today with the supply from the away from market matchups, down to 388 points, now back up to 400. People may be doing some SBCs because prices have dropped a little bit. If we take a look at some of the popular players here, some of the SBCs that have dropped in price, I was just looking at, I think Messi's player of the month card is down like 50 to 60,000 coins. Cavani's only 400K right now, so that is a little bit cheaper than he was earlier, just at the actual SBC price value, which we kind of just followed those. Busquets has won 60, that's down like 10, 15,000 coins. So some of these SBCs have gotten a little bit cheaper with fodder dropping. I might expect a little bit of that to happen again during rewards, just because I do think there will be some people that open packs, also there will be some people who don't open packs and will be saving those packs for a potential promo later on this weekend, which leads me to talk about something else. Are we gonna get foot birthday this Friday? That is the million dollar question. Are we gonna get foot birthday and what's it gonna be like if we don't? Well, if we don't, this game is already feeling like it's on the out. This is one of the worst weeks for EA sports ever. And it's almost just like EA, you need to drop a promo. Like please drop some content for us. I mean, I've seen multiple big time content creators. I'm not gonna drop any names, but I've seen multiple big time content creators tonight tweeting out about how we need content in FIFA. There's not a lot to do. EA sports drop us something, right? So I mean, that's what we're really looking for right now in FIFA is just something to do. And I feel like a lot of people, EA has set themselves up for failure when they do this. When they don't release content for a while, we're sitting here like expecting it because it's been continually pushed out. Every week there's a promo or, you know, these two week promos come out every two weeks. And now we haven't had one for a week and a half, almost two weeks. And if they do that again, that's gonna be pretty crazy. And I think it might push some people over the edge, honestly, in this game. But that's like the number one thing that everybody is looking forward to today. Some sort of foot birthday loading screen, some sort of foot birthday hint, clue or anything about a promo that could be happening this weekend. Now, if they don't do foot birthday this weekend, even though it would make the most sense in the world to drop that promo, I guess they could drop still some sort of like best of promo, but again, I just feel like we're scratching for things at this point and just hoping for something because we just want something, right? And that's what everybody wants right now in FIFA. We want a promo and we just have not been getting it. We have not been getting that stuff, that content from EA that we truly want. But again, today with the market, I do expect a little bit of a rise. Once I sell these informs, I'm gonna be surfing around and looking for some cards that I think could rise a little bit today because of those weekend league plus objectives. Now, I know there's just not a lot of hype in this game right now, so you're probably gonna have to pick and choose which spots you wanna be involved in. Now, there were some what if upgrades that happened earlier today. And some of these cards are down a decent amount. This is prospect numero uno who was down a lot after his upgrade, who was actually just bounced back. But this Sancho card, 1.05 mil, he was literally down to a million coins for a long while right before rewards, 1.05. And then there's nothing to 1.1, really. So Sancho is actually looking interesting right now. Only a few cards to 1.1. So the bounce back is happening on that card right there. I was looking at Odegaard, who was like 480,000 coins. Pre-upgrade, he's now down to about 440K where he's been chilling. But I do think you might see some of these guys rebound. It's what we saw last week. After the upgrades happened, they dropped down and they actually rose back up later because people were like, hey, that card looks pretty sick. Now, one person that is in a lot of people's eyes right now is this Berticce card because coming in at 120,000 coins, this card is miles better than informed Jordi Alba who was released last week and is about 30K cheaper. So this card, in my opinion, once the supply kind of dries up a little bit and maybe some reviews get out and it gets talked about a little bit more. 1.15 for this card. I'm gonna pick that up because this guy was like 123,124,000 coins when the upgrade was about to come out. And I think this card is too cheap. I really think this card is a little bit too cheap right now. 1.11 on an undercut right there for Berticce. I might have to snag one of these even though I'm on a low coin amount just because this is probably one of the best, if not the best left back in the La Liga and of course, besides Frill and Mendy. I mean, you're probably playing this guy at center back, right? That's the thing to do this year. High-medium work rates with the pace. This guy at center back with those statistics right there is gonna be a really, really solid card considering this game's meta. So I do think you will see some people trying to play this guy at center back actually which makes him very interesting play. I do think there's a possibility if we don't get a big promo this weekend that some of these what-if cards, people will just buy them up and try them. Same thing with icons and icon moments, right? Because icon moments, people still wanna try some of those cards out. There's still demand for those on this market. So kind of like what we saw last weekend if there is no promo, you might see some of these cards, some of the really rare and meta stuff if we don't get some insane content start to go up. Now I knew this was gonna rise today, this Keen, he was about a mil, about to about 1.1 or back up to about 1.1. That was a GG if you were able to flip any of those. But yeah, a lot of stuff today, I do think we'll have a small rise in the market on some of these out-of-pack special cards just because, you know, we can league right now, that is something that people are playing for the actual week and league player picks, even though we didn't get a Ronaldo or a Messi or even a Benzema this week's team of the week, pretty bad team of the week. But still, there's a little bit of hype there and I do think you will see people go out and play some week and league or they'll just honestly stop playing. It's gonna be one of those two things and my opinion going on right now. So obviously there's not a ton to talk about in terms of like actual stuff to be prepared for on FIFA. Just get on the bids again, right? Bids are your best friend and don't overthink the market in these times, right? Focus on the stuff that is hyped. Like I kind of overthought it today with some of these forums trying to flip these guys. And when I just know that, hey, flipping these cards probably wasn't the best decision because there's not that much hype. They were very rare right away. Like I got these drutas right around 220K and yes, I would love to sell them at 240 but I don't think he's gonna get back up there. I just feel like a lot of this stuff was just too expensive today and there wasn't enough hype to keep it higher. So I'm gonna take my L here and move on and continue to make trades and not get stuck in a rut, right? That's the biggest thing. If you get stuck in a rut losing coins, it can really impact your mentality. So I'm not gonna do that. Move on, make some more coins. So hopefully we get some more information today related to foot birthday and promo. At least something, right? Just do best of or something this Friday is what we're hoping for in FIFA. So again, stuff we might see today, of course, rewards, good luck with your red picks and stuff like that. You might see icon moments, SBCs, another throwback Thursday type thing, player of the month in Bape and of course Europa League wrote to the final action with those live items moving around a decent amount live. We'll be looking at those on stream, of course, link below, link below in the description. If you enjoyed this video, hit a thumbs up on it. Comment down below if you have any questions and subscribe if you're new. It's been Nate the Foot Account and I will catch you guys later. Peace out.


Cool. Now we're into our spotlights on awesome things that have shipped in the past month, starting with Lotus. I think we still maybe are missing a Jenna version sees on a plane. I can hop in here. This is highlighting the most recent ship version of Lotus 1.15.1, which has experimental FEM support and also the indexer provider on by default, and the upcoming 1.15.2, which has a lot of things that have been heavily requested by the storage provider community. Window post workers. These are actually window and winning post workers, which help you kind of scale your proven process. Enhanced to the ceiling scheduler and a lot of improvements to snap deals which make them doing those in the live network much, much easier and much better UX for storage providers. So lots in these latest Lotus feature releases to enjoy on to West for the computer for data summit. Thanks Molly. Can you hear me okay. Awesome. Thank you so much know we had we were very fortunate to have a few days in Paris early this month to bring together a number of service providers and number of technology partners, a small group of us from the back of y'all team to really figure out what has been done in this space previously what's the history and one give us a good start just kind of giving a sense of the history of compute over data. We learned from other partners that it tried to implement their own ad hoc solutions to to distribute compute over data. We were lucky to have other folks from the crypto econ team and a number of other groups to kind of weigh in on considerations we should have as we start to build this. But really this was the first time for everyone to get together and sort of sort of community around this compute over data project. So after a series of sort of prepared lectures and day one day to is more of an informal on conference session. There's a lot of considerations that we need to start planning for related to security and reproducibility of the data sets verification of the data and so we're talking about different trade off to the architecture it was a lot of fun and we had real fortunate to have some really smart people there with us. But the biggest takeaway is that we definitely have the interest of the storage providers and that'll be critical for the compute layer. As we build out back to y'all. We want to really think about a lot of the architecture was built around the concept of plugability so if we do verification we want to allow to plug in their own verification we want to support as many different run times as possible. Things like was really growing a popularity. And so I think we have a good kind of sense of the initial considerations that we want to build out for the next couple months and as you can see here the goal is just to get the system up and running so we can do nice demos. Leading into the next few months we're going to be focusing more on outbound and getting user validation of the system so we'll be highlighting each month trying to get one notable research academic user and system. And as you can see we've got some longer term goals here for the next few months after that but we are off to the races and if anyone would like to contribute or find out more information. We do have a notion summary link there, all of our code is also public on the file point page so we'd love to have your opinions and feedback as we build it out. Awesome ZX and Alex Crypto Econ Lab Summit. Okay, this is Alex for crypto econ lab. Just want to review what we did on our crypto econ lab summit it was the first time that we had all met in person. Our lab is now, when we add one more person will have grown 200% in the first three months of the year. So, a lot of onboarding and keeping busy there. And now that we have this new capacity to split our work streams. We had a previously had everybody working on everything approach. A lot of that was due to the fact that some of us were new to the area and needed to catch up. But now I think we can split things into different work friends and they're listed right here. We have a new hierarchy consensus, etc, working on project Atlas in a way to marry file coin with geospatial processing which seems to be a very natural marriage there. I won't go into the details there one thing we did do is to have our first ever crypto econ day summit at Dev Connect. We had 60 attendees and 11 talks. We scheduled this pretty quickly. And I think we can do a much better job going forward. We're looking to now do a quarterly file coin economic stay. And so at major conferences. So we're working on that. And with that, I will turn it back. I'm turning there on using summits like this as an opportunity to get to know people who might want to join the team. I feel like it's a good lesson for other other teams as well. Thank you. Passing to Raul. Go ahead. This is Raul from the FEM team. The FEM team had a long and needed Kolo announced time for three weeks. It's ending. It's actually ending tomorrow we're still here. It's been crucial to work through some critical items for the for the upcoming M1 milestone and also to flesh out the scope and work breakdown for M2. As a result, the gas parameters for 532 are almost finalized and probably an update to the draft focus coming coming in tomorrow. We also made a ton of progress with various hardening work streams for M1 including the ones listed here. We also worked through the NV16 testing and deployment timeline with the Lotus team and the Infra teams had many product conversations around DVM and native scoping and the development experience prioritization there. And also had the opportunity to connect with several collaborators, including the FESHA team to discuss technical design details for the file coin EVM implementation. Awesome Patrick retrieval markets. Cool. Yes, we have, we've had a retrieval markets and will specifically sat in Kolo this week in Amsterdam as well. One week of the sat in team being here on Tuesday, we had a retrieval markets workshop intro to sat in. We had four speakers and over 30 people watching or attending the event. We had a lot of learnings to what Alex mentioned for the crypto equine day. I learned a lot about how to put on events in the last minute, and there's lots of learnings to take in doing it again in the future. We've also had the team my L team joins the last two days, which has been great. It's great to have the sat in and my L team in the same place. And even though they're building their own networks, they've been breaking bread together and sharing stories of building retrieval networks. And it's all been very happy. And major takeaways is that we've got a much clearer route towards launch for sat in. And we, it was also great to hang out with some of the crypto economics team earlier in the week and make progress in that space too. As Jake mentioned as well, we had a meeting with the bedrock team. We're X retrieval markets and we covered a lot of interesting things. So it's been a great week and things are much more clear for the future. Awesome. Great looking roadmap for the next couple of months as well. Over to Petar for advice. So I want to make a quick announcement of a developer tool that we've built called advice, which is an extensible RPC protocol compiler based on IPO D. This tool is now production ready at its first milestone. And it's generally meant to streamline the process of defining formally future protocols as well as legacy ones. It has a lot of features which you can read about on the GitHub repo, and it's quite flexible. Our current adopters soon to be in production are a few projects some in the IPFS ecosystem so hydra and IPFS itself, as well as store the store the index from the file coin ecosystem. Feel free to reach out if you want to learn more about it. Thank you.