Severity Levels
When raising a support ticket, customers are prompted to select the severity of the issue they are experiencing. This helps our support team triage and assess the level of impact or importance the issue has on your organization.
At Cloudsmith, we employ a severity (SEV) rating system ranging from 1 to 5, where a lower number signifies a higher severity.
For example:
-
Critical: A critical incident with a very high impact. For example, the platform is unavailable or completely unusable for all users.
-
High: A major incident with significant impact. For example, a service is down for a subset of users, or a critical function within the platform is not functioning.
-
Medium: Moderate application functionality or performance loss, but a workaround is available. For example, delays or intermittent errors when pushing/pulling packages.
-
Low: An isolated non-critical issue affecting a small number of users or a subset of non-critical packages. For example, 2FA reset or documentation not matching functionality.
-
Lowest: Questions or clarifications around features, feature enablement or general inquiries. No impact on the operation of the platform.
A detailed overview of each severity is also displayed within the following table:
| Severity | Impact | Example |
|---|---|---|
| Critical (SEV 1) | • Widespread outage. • Platform completely inoperative. • All organization users severely. impacted and unable to perform normal functions. • No workaround exists. | • Broad impact platform outage. • Platform is completely unavailable via UI, CLI, and API. • Unable to push or pull any packages. |
| High (SEV 2) | • Major failure or degradation of platform availability or performance. • Platform is available but severely impacted. • Significant impact for multiple users. • Inconvenient workaround or no workaround exists. | • Service interruptions to some but not all platform features. • Severe delay or consistent failure in push/pull actions. • Issues are restricted to a single package format. • Platform is unavailable or severely degraded via UI, CLI or API. |
| Medium (SEV 3) | • Moderate application functionality or performance loss. • A temporary workaround exists. • Multiple users are impacted in their normal function. | • Moderate delay or intermittent failures when performing push/pull actions. • Issue with a single package (i.e. a single docker image). • Packages not fetched from upstream. • Package can be pushed by a user but not via a service account. |
| Low (SEV 4) | • Isolated issue, affecting a small number of users or small subset of noncritical packages. • Low impact on operations. • Reasonable workaround is available. | • Minor delays or occasional failure with package push/pull actions. • Noncritical functionality impacted. • Functionality does not match documentation. • 2FA reset. |
| Lowest (SEV 5) | • No platform impact. • General enquiries. • Feature setup. | • Feature request/setup. • Questions regarding functionality. • Beta feature enablement. • Custom domain creation. |
At Cloudsmith, we understand that our customers are the best judges of how an issue will impact their business. That's why we ask you to select the severity level when submitting a support ticket. However, we reserve the right to make the final determination of the severity level based on the information provided.
Our support team will review the issue, assess the impact on the customer's business, and assign a severity level based on our established guidelines. This helps us ensure that we are providing an appropriate level of support and allocating our resources effectively to address the issue.
Updated 4 months ago
