 This tutorial will demonstrate how to use the OpenTelemetry plugin for Pixi. One of Pixi's unique features is that it collects stores and queries all telemetry data locally in your cluster. Retention time depends on the level of traffic in your cluster, but will generally be on the order of hours. For many use cases, several hours of data is enough to debug issues with your Kubernetes applications. For long-term visibility, Pixi offers a plugin system that can be used to export Pixi data to an external storage provider. The OpenTelemetry plugin makes it easy for you to export Pixi data to any OpenTelemetry collector. Everything I'm going to show you today is available in a tutorial that I'll link below. You can also get to this tutorial by going to Pixi's plugin repo and then following the tutorial link in this table of available plugins. Let's go to that tutorial link now. In this demo, I'm going to deploy an example OpenTelemetry collector to my cluster. Then I'm going to show you how to enable the OpenTelemetry plugin and then configure which data is going to be exported. In a second video, I'll show you how to write your own plugin script so that you can export custom data. Let's deploy the OpenTelemetry collector. If you're following the tutorial, you can click the link here and it'll take you to our demo collector. Basically, we're just going to grab this YAML file and then we're going to apply it with kubectl. Let's just peek at our cluster really quickly. I have a mini kubectl cluster up and running. It's got Pixi deployed and Pixi is in the PL and PX operator namespace. I also have a demo application so that our cluster has some traffic in it and that's in the sock shop namespace. Our collector is up and running. To set up our plugin, we're going to go back to Pixi's live UI and go to the top right-hand corner to the admin page. On this page, we're going to quickly enable the OpenTelemetry plugin. This plugin requires one piece of information, which is the custom export URL. Let me just open back this repo. In this repo, in the directions for deploying the OpenTelemetry collector, it provides this path that we're going to use to configure our plugin. This is the path to our OpenTelemetry collector in our cluster. We're going to save that. Oh, this demo collector does not support secure connections. I'm going to disable that really quickly. Press Save. Then we need to go to this long-term data export page to configure what data is being exported. There's also a shortcut up here on the left sidebar. I'm going to click that button. This has a list of the preset scripts that are provided by the OpenTelemetry plugin. We welcome more contributions here. This only has a few scripts to get started. We have all these scripts enabled by default once we enable the plugin. You can't edit these scripts, but you can change which clusters they'll be run on if you have multiple clusters with Pixie deployed. You can also change how frequently it runs. These scripts are written in Pixel, which is Pixie's query language. They also use Pixie's hotel methods to export the Pixie data in the OpenTelemetry format. Let's exit out of there. At this point, we should be exporting data to our OpenTelemetry collector. We can check on that by going to the logs. Here you can see that we're regularly exporting metrics. This OpenTelemetry collector example that we've deployed, it's basically just printing out any data it gets to its logs. We can see that it's getting data here. This is just a quick demo to show you how you can export Pixie data in the OpenTelemetry format. In the next demo, I will show you how you can create a custom script so that you can send whatever data you want to your OpenTelemetry collector.