Icinga / Icinga/icingaweb2-module-reporting
Beginning of the month scheduler includes new month as well
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 71
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Hi Icinga2 Reporting team,
I'm making two reports with the timeframe of a month: one by a breadown of a day and the other one by a breadown of a month. Both scheduler are set to start at: 01.10.2022 00:00:00 and frequently by a month. The report by a breadown of a day correctly did report today at 01.10.2022 00:00:00 and included in the report: 01.11.2022 till 30.11.2022. The report by a breadown of a month did report today at 01.10.2022 00:00:00 as well and included in the report: 11.2022 till 12.2022. Why those the report with a breakdown of a month reports the previous month and the actual month?
Report breakdown by a day:

Report breakdown by a month:

I would expect the report breakdown by a month to be also only from 01.11.2022 till 30.11.2022 (just for the previous month).
Report by a breadown of a day settings:


Report by a breadown of a month settings:


Versions in use:
pdfexport 0.10.2
reporting 0.10.0
Icinga Web 2 Version | 2.11.2
PHP Version | 7.3.33
Is it a bug? Or config problem?
Many thanks in advance!
Best regards
David
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the monthly scheduler using the reported pdfexport 0.10.2, reporting 0.10.0, Icinga Web 2 2.11.2, and PHP 7.3.33 versions and compare its date range with the daily breakdown. Trace the scheduler's monthly breakdown date handling; done means a run starting on 01.10.2022 includes only 01.11.2022 through 30.11.2022, matching the stated expectation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100