https://pizza.rs/tags/auto_date_histogram/Recent content in Auto_date_histogram on INFINI PizzaHugoenhttps://pizza.rs/docs/references/aggregation/bucket/auto-date-histogram/Mon, 01 Jan 0001 00:00:00 +0000https://pizza.rs/docs/references/aggregation/bucket/auto-date-histogram/<h1 id="auto-date-histogram-aggregation"> Auto date histogram aggregation <a class="anchor" href="#auto-date-histogram-aggregation">#</a> </h1> <p>A multi-bucket aggregation like <a href="https://pizza.rs/docs/references/aggregation/bucket/date-histogram/"><code>date_histogram</code></a>, but you choose the NUMBER of buckets and the engine picks the interval that best fits. It solves the cold-start problem of time charts: when you do not know whether the data spans minutes or years, you state the resolution you want on screen and let the ladder decide the unit.</p> <h2 id="how-it-works"> How it works <a class="anchor" href="#how-it-works">#</a> </h2> <p>The engine reads every date value (epoch milliseconds), takes the data extent <code>max − min</code>, and divides by the <code>buckets</code> target to get a rough per-bucket width. That width is matched against a fixed ladder, and the smallest interval that covers it wins: <code>1s</code>, <code>1m</code>, <code>5m</code>, <code>10m</code>, <code>30m</code>, <code>1h</code>, <code>6h</code>, <code>12h</code>, <code>1d</code>, <code>1w</code> as fixed intervals; beyond a week the calendar units <code>month</code>, <code>quarter</code>, <code>year</code> (and multi-year multiples for very long extents). The pick is one closed-form step, not an iterative search.</p>