Opsview 6.8.x End of Support

With the release of Opsview 6.11.0 on February 2025, versions 6.8.x have reached their End of Support (EOS) status, according to our Support policy. This means that versions 6.8.x will no longer receive code fixes or security updates.

The documentation for version 6.8.9 and earlier versions will remain accessible for the time being, but it will no longer be updated or receive backports. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.

Acknowledge - Request Format

URL: /rest/acknowledge. This requires authentication.

Requires ACTIONSOME or ACTIONALL access.

• GET — lists all hosts and services that can be acknowledged based on state and user permissions.
• POST — submit an acknowledgement.
• PUT — not implemented.
• DELETE — remove the acknowledgement as matched by the object selection.

Access Control Copied

• ACTIONALL allows setting acknowledgements to any object in Opsview.
• ACTIONSOME allows setting of acknowledgements to host or services based on the access object selection.

Note

If a user has ACTIONALL, but only VIEWSOME, the user could set acknowledgements for objects that they cannot view.

Object Selection Copied

Acknowledgements are set against host or service objects. You can choose hosts or services using the same URL parameters as the status API, with the following rules:

• No parameters means that no objects are found (status API returns everything if no parameters is passed).
• Service objects will be returned if you have added a filtering on a parameter which looks for services, otherwise host objects are returned.
• No errors are raised if objects are not found.

Alternatively you can search for objects using the following parameters, based on the object type you are searching for:

• hosts:
  • hst.hostid (same as hostid - this parameter takes priority)
  • hst.hostname
  • hst.hostgroupid (this is only for the host group that the host belongs too - this is not based on the host group hierarchy)
  • hst.hostgroupname (only for host’s hostgroup, not the hierarchy)
• services:
  • svc.serviceid (same as serviceid - this parameter takes priority)
  • svc.hs (same as hs)
  • svc.hostgroupid
  • svc.hostgroupname
  • svc.hostid
  • svc.hostname (can use % as wildcard)
  • svc.servicename (can use % as wildcard)
  • svc.keywordid
  • svc.keywordname
  • svc.servicegroupname
  • svc.servicecheckid

Note

Host and services will only be found if you have the appropriate access to the object.

The basic rule is that if you are searching for multiple fields of the same type of object, then the search fields are AND’d together, but multiple values of the same field are OR’d together. Duplicated host or services are ignored.

If you request a specific object (using hst.hostname, hst.hostid, svc.hs, svc.serviceid) and that object does not exist, an error is raised:

In no objects are found, an error is returned:

For example, URL parameters of:

This would select the service hostA::service1, the service with id=45, and all services called HTTP or Disk:% on hostB or hostC.