Severity defs

SUMMARY.md

@@ -203,6 +203,8 @@
 * [Bug Bounty Program](troubleshooting/bug-bounty-program.md)
 * [Capture a HAR File](troubleshooting/capture-a-har-file.md)
 * [Guidelines for a Successful Enterprise Support Engagement](troubleshooting/successful-enterprise-support-engagement-guidelines.md)
+* [Kubecost Severity Level Definitions](troubleshooting/kubecost-severity-definitions.md)
+
 
 ## Other Resources
 

install-and-configure/install/kubecostv2.md

@@ -2,10 +2,6 @@
 
 Kubecost v2 introduced massive functionality changes including changes to the backend architecture. This may require additional changes be made to your environment before upgrading from an older version of Kubecost to 2.0+. This article reviews several different common configurations and explains any necessary steps to take.
 
-{% hint style="danger" %}
-After upgrading to v2, it's possible saved reports may not properly display in the Kubecost UI. Follow [this solution](/using-kubecost/navigating-the-kubecost-ui/reports.md#saved-reports-not-appearing-in-kubecost-ui-after-upgrading-to-v2) if you experience this problem.
-{% endhint %}
-
 ## Single cluster users
 
 If you have a single cluster installation of Kubecost (i.e. one primary Kubecost instance on each cluster), then you can follow the standard upgrade process for Kubecost 2.0+.

integrations/integrating-kubecost-with-datadog.md

@@ -6,8 +6,7 @@ Datadog is a monitoring and security platform which teams use for cloud applicat
 
 Before you get started, you will need the following:
 
-* Install [kubectl](https://kubernetes.io/docs/tasks/tools/), [Helm](https://helm.sh/docs/intro/install/), and [GNU Wget](https://www.gnu.org/software/wget/)
-* Datadog account with API key and account permissions to create dashboards
+* Install [kubectl](https://kubernetes.io/docs/tasks/tools/), [Helm](https://helm.sh/docs/intro/install/), and GNU Wget]
 * Kubernetes cluster with permission to access and deploy new workloads
 
 ## Step 1: Install Datadog agent

troubleshooting/kubecost-severity-definitions.md

@@ -0,0 +1,12 @@
+# Kubecost Severity Level Definitions
+
+ Opening a support case at [email protected] or starting a thread in slack in your private slack channel (Enterprise customers only) can make it easier to share technical data, error messages, and system information with the Kubecost team. 
+
+## p0 (urgent)
+A problem that severely impacts your use of the software in a production environment (such as loss of production data or in which your Kubecost instance is no longer functioning. 
+
+## p1 (high)
+A problem where the software is functioning but your use in a production environment is severely reduced. The situation is causing a high impact to specific features in Kubecost and no workaround exists.
+
+## p3 (low)
+A problem that involves partial, non-critical loss of use of the software in a production environment or development environment. For production environments, there is a medium-to-low impact and a procedural workaround exists. For development environments, where the situation is causing issues that impact full functionality and inability to migrate to production.

using-kubecost/navigating-the-kubecost-ui/reports.md

@@ -294,12 +294,3 @@ data:
 
 Navigate to your Reports page in the Kubecost UI and ensure that the configured report parameters have been set by selecting the Report name.
 
-### Saved reports not appearing in Kubecost UI after upgrading to v2
-
-After upgrading Kubecost to v2, saved reports may not properly display in the Kubecost UI. To properly transfer over saved reports, download this [`copy-reports.sh` file](https://github.com/kubecost/kubecost-utilities/blob/main/copy-reports/copy-reports.sh), then run the following command:
-
-```
-bash copy-reports.sh
-```
-
-Saved reports should then populate in your upgraded Kubecost version.