Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Choose a timeperiod #31

Open
Nemental opened this issue Apr 18, 2019 · 2 comments
Open

Choose a timeperiod #31

Nemental opened this issue Apr 18, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@Nemental
Copy link

Some hosts or services don't use the 24/7 period. An example would be 8/5, so from 9am to 5pm Mon-Fri. Incidents that don't happen during this period won't be considered in the calculation.

@lippserd
Copy link
Member

Hi,

Thanks for the request. This absolutely makes sense and was planned anyway.

Best,
Eric

@lippserd lippserd transferred this issue from Icinga/icingaweb2-module-reporting Apr 9, 2020
@lippserd lippserd added this to the 1.0.0 milestone Apr 9, 2020
@lippserd lippserd added the enhancement New feature or request label Apr 9, 2020
@lippserd lippserd removed this from the 1.0.0 milestone Jul 11, 2023
@LandmannWo
Copy link

+1. Reporting on SLAs often requires to be able to distinguish SLA operating hours for different hosts/services. In an ideal world the SLA can be assigned to an object (host/service) and the report is considering it (so different object-bound timeperiods within the same report) and not "only" as a report parameter. But the latter would be a good start if the first is a lot more complicated.
Any chance for this to be considered anytime soon?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants