Home / Companies / Honeycomb / Blog / Post Details
Content Deep Dive

​​Calculating Sampling’s Impact on SLOs and More

Blog post from Honeycomb

Post Details
Company
Date Published
Author
Max Aguirre
Word Count
990
Language
English
Hacker News Points
-
Summary

Mall food courts and Honeycomb share a fondness for sampling, a practice that Honeycomb not only recommends to its customers but also uses internally, particularly through its Refinery tail-based sampling proxy. Sampling, which is inherently lossy, requires careful consideration to ensure that an organization's critical measurements, such as Service Level Objectives (SLOs) and triggers, are not adversely impacted. To manage this, the Heinrich Hartmann Sampling Error Calculator can be used to estimate the margin of error introduced by sampling. The process involves analyzing data, such as the sample rate and request rate, and adjusting parameters to calculate relative error counts for both compliance and budget burndown. The findings help determine the reliability of alerts and guide decisions on alert trustworthiness. If the margin of error is too high, adjustments in sampling rates, SLI formulas, or trigger targets may be needed. The text underscores the importance of balancing trace integrity and cost efficiency while adapting to changes in business goals and instrumentation, emphasizing the need for ongoing evaluation and refinement of sampling practices.