Incidents | Console | Teradata Vantage on Azure - 2.2 - Incidents - Teradata Vantage on Azure

Teradata Vantageā„¢ on Azure Getting Started Guide

Product
Teradata Vantage on Azure
Release Number
2.2
Published
January 2021
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
paq1604950717165.ditamap
dita:ditavalPath
dse1605632705402.ditaval
Severity Impact Urgency Definition
1 Critical High Mission-critical production system is down, corrupted, or severely degraded or unusable and requires immediate attention to return the system to service.
If you submit an S1 incident, you must agree to allow Teradata to contact appropriate escalation personnel. If the appropriate personnel are not available, Teradata changes the incident from S1 to S2 and responds accordingly.
2 Significant High Production system is up and operational, but the incident has severe, ongoing, daily impact to operations; a non-mission critical system is down and requires expedited engagement and urgent resolution.
3 Critical Medium Incident has medium impact to operations; resolution efforts can occur over the next several days.
Low
Significant Medium
Minor High
4 Significant Low Incident has low or no impact to operations; resolution efforts can occur over the next several weeks.

For information on incident response times, see the table in Premier Cloud Support.