Hi Fabricio, usage.aggregation.timezone: GMT usage.execution.timezone: "" usage.stats.job.aggregation.range: 1440 usage.stats.job.exec.time: 00:15
The CS version is 4.20.1 Thanks for your help in advance best regards On Mon, Sep 1, 2025 at 2:04 PM Fabricio Duarte < [email protected]> wrote: > Hi Francisco, > > What CloudStack version are you using? Also, could you provide what > value do the global settings `usage.aggregation.timezone`, > `usage.execution.timezone`, `usage.stats.job.aggregation.range` and > `usage.stats.job.exec.time` have? > > On 9/1/25 05:50, Francisco Arencibia Quesada wrote: > > Hi all, > > > > We are facing an issue with the list usageRecords command in a CloudStack > > environment. > > > > Running: > > > > cloudmonkey list usageRecords startdate="2025-08-24T00:00:00+0200" > > enddate="2025-08-25T23:59:59+0200" > > > > → returns data. > > > > But running: > > > > cloudmonkey list usageRecords startdate="2025-08-25T00:00:00+0200" > > enddate="2025-08-25T23:59:59+0200" > > > > → returns nothing. > > > > On other CloudStack environments with the same version and configuration, > > both queries work as expected. > > > > We already checked: > > > > - > > > > Locale configuration on the management server: > > > > locale -k LC_NUMERIC | egrep 'decimal_point|thousands_sep' > > decimal_point="." > > thousands_sep="," > > > > (previously thousands_sep was empty, we fixed it but the problem > > remains). > > - > > > > Compared cloudstack-usage configuration with another environment > where > > usage records are returned correctly. > > > > Has anyone experienced this behavior before, or know if it could be > related > > to how CloudStack interprets dates in the list usageRecords API call? > > > > Thanks in advance, > > -- > > *Francisco Arencibia Quesada.* > > *DevOps Engineer* > > > -- *Francisco Arencibia Quesada.* *DevOps Engineer*
