# Report - Tag Historian Query Aggregation by Day

**URL:** <https://forum.inductiveautomation.com/t/report-tag-historian-query-aggregation-by-day/69948>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 16, 2023, 3:59pm UTC](https://forum.inductiveautomation.com/t/report-tag-historian-query-aggregation-by-day/69948 "2023-02-16T15:59:27Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [February 16, 2023, 8:57pm UTC](https://forum.inductiveautomation.com/t/report-tag-historian-query-aggregation-by-day/69948/3 "2023-02-16T20:57:59Z")

</div>

My gut is a day is hardcoded as 24 hours, like month and year are, see this post,

> [@Tag history binding periodic aggregation](https://forum.inductiveautomation.com/t/tag-history-binding-periodic-aggregation/69417/5):
>
> I mean, would you rather set a period of 604800 seconds, or 1 week? It's all ultimately milliseconds under the hood. The different units are just a convenience. Haha, sure sweat_smile My point was more on the semantic. I agree a week is 604800 seconds upside_down_face but what about month (and year to a greater extent)? Understood! Thanks for looking into the code! I think all this deserves to be documented.

---

_[View the full topic](https://forum.inductiveautomation.com/t/report-tag-historian-query-aggregation-by-day/69948)._