Nagios Support Forum

Hi Team,

We enable the schedule down time for x host by the some test1 user.
If we enable the schedule down time on X host by another user test2 it's allowing the schedule downtime, Why it is not considering duplicate host. Is there any time period calculation going for ex: test 1 user enabled the schedule down time on X host from 7:00AM to 10:00AM
test 2 user enabled the schedule down time on X host from 7:05AM to 10:05AM .

What version of XI are you on? What OS?

Could you send me a screenshot of what it looks like now?

Are you only asking why it's allowing two entries for a scheduled downtime on the same host? Just different times that fall closely together?

HI Team,

We are using nagios xi 5.4.0.
Sorry we can't give the screen shot because schedule time expired so we are not able see which are enabled.

I am asking why its accepted duplicate entry
for ex: We have enabled the scheulde down time for the x host by user1 from 10AM to 12 AM and on the same host user2 has enabled. when user 2 is enabled how its accepting the same host because already user1 has enabled.

Thanks for clarifying!

The duplication of scheduled downtime is completely normal. For example, a team could be having different maintenance times on the same host or host groups.

So allowing a user to schedule different downtimes even if they overlap each other is perfectly normal and should make sense in that logic.

In your example, they are very close in time. So the real downtime for that host is from 7:00AM to 10:05AM.

Which is completely normal.

I hope this helps!

Thanks team , then how schedule down time will work if user 1 has enabled on x host 10:00AM to 11:00AM again user 2 has enabled on same host 10:00AM to 11:40AM.

How the schedule down time work , Is it work for 10:00AM to 11:00AM or 10:00AM to 11:40AM. There is time difference as 40 min. Does it calculate next 40 min schedule down also?

@Gonela, It will extend the downtime by 40 minutes. So the total downtime would be from 10:00 am to 11:40 am.

thanks team.

@npolovenko, Not a problem.