<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/711a7e514b5f461b878acdb09b9a1d3b&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/711a7e514b5f461b878acdb09b9a1d3b-1687795117805.gif</thumbnail_url><duration>357.66666666666714</duration><title>A Walk Through Lunar&apos;s Remedy Statistics Feature 🚀</title><description>Hey, I&apos;m going to walk you through Lunar&apos;s Remedies Statistics feature and show you how it can be beneficial for your work. In this video, I will be demonstrating how to remediate and solve problems with Lunar Proxy using the strategy-based throttling remedy. I will be using Lunar&apos;s Sandbox to get some data kicking in our system and then I will be watching the remedy stats command that is our focus here today. I will be turning the strategy-based throttling remedy on and applying my policies to see the benefit of what we just did. We will be looking at the affected count, affected ratio, and the ratio of the remedy by endpoint and status code. Finally, I will be showing you the Remedy Stats action section that allows us a bird&apos;s eye view on all the generated or modified statistics that are system generated. This video is a step-by-step guide to help you understand how to use Lunar&apos;s Remedies Statistics feature and how it can be useful for your work.</description></oembed>