Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
It is critical that you use the appropriate priority/impact not only for measurement and metrics purposes on our end but also for your ticket to be given the correct priority.

...


Please keep in mind to open only one issue per ticket.

Support reserves the right to correct a user misentered priority level.


Critical business impact

  • This represents a total loss of service, which cannot be resolved by restarting
  • No workaround is immediately available
  • Impact on business operations must be critical
  • Only available for existing production systems of Checkmk
  • Only available for stable CEE or MSE up to 30 months after the first stable release of that version

Significant business impact

  • Checkmk is usable, but significant functionality is severely impaired, and no acceptable workaround is available
  • The issue is critical to customer's business operations:
    • Critical component returning error / not responding, but the software overall remains operational
    • A degraded Checkmk performance with a serious negative business impact
    • Checkmk has service interruptions that can be temporarily resolved by restarting the service or via a workaround
  • Only available for existing production systems of Checkmk
  • Only available for stable CEE or MSE up to 30 months after the first stable release of that version

...