You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
Describe the results you received:
I can create recurrent downtime through Rest API but no information how to create one shot downtime.
Describe the results you expected:
I would like to know if it's possible to create downtime on the fly ? For example when running application maintenance update we want to send Centreon dowtime to service or service group involved in application update.
Since application update can be done at every moment, it can't be a reccurent downtime...
Any solution ?
Additional information you think important (e.g. issue happens only occasionally):
Thanks
The text was updated successfully, but these errors were encountered:
BUG REPORT INFORMATION
Centreon Web version:
2.8.6
Centreon Engine version:
1.7.2
Centreon Broker version:
3.0.5
OS:
CentOS release 6.9 (Final)
Additional environment details (AWS, VirtualBox, physical, etc.):
VMWare Virtual Machine
Steps to reproduce the issue:
https://documentation.centreon.com/docs/centreon/en/2.8.x/api/clapi/objects/index.html
https://documentation.centreon.com/docs/centreon/en/2.8.x/api/api_rest/index.html#downtimes
Describe the results you received:
I can create recurrent downtime through Rest API but no information how to create one shot downtime.
Describe the results you expected:
I would like to know if it's possible to create downtime on the fly ? For example when running application maintenance update we want to send Centreon dowtime to service or service group involved in application update.
Since application update can be done at every moment, it can't be a reccurent downtime...
Any solution ?
Additional information you think important (e.g. issue happens only occasionally):
Thanks
The text was updated successfully, but these errors were encountered: