Data Dictionary
There are two types of data sources reported by Open Canvas: Cases data source and Azure events data. There are three instances where these data fields can be found and below, you can see the fields defined and how they related to each instance.
Cases Data Source
Visuals
| Field Display Name | Axis | Value | Legend | OrderBy | Data Example | Data Definition |
|---|---|---|---|---|---|---|
| RequestId | ✔️ | ✔️ | 211220006000XXXX | Support Request (SR) ID | ||
| State | ✔️ | ✔️ | ✔️ | Open | SR open/closed state | |
| Status | ✔️ | ✔️ | ✔️ | Duplicate, Disconnect, Initial Contact Pending, Request to Revolve, Resolved, Resolved by Customer, Transferred from External, Troubleshooting, Un-Resovled | The state of an active case. | |
| InitialSeverity | ✔️ | ✔️ | ✔️ | 4 | SR severity set by the support request submitter Severity values in the data source are 1-4, and the Severity Name fields map those values to the Unified Enterprises offering's severity names. 1. = "1 - Critical business system down" 2. = "A Critical business system degraded" 3. = "B - Moderate business impact" 4. = "C - Minor business impact" |
|
| InitialSeverityName | ✔️ | ✔️ | ✔️ | C - Minor Business impact | SR severity set by the support request submitter | |
| Severity | ✔️ | ✔️ | ✔️ | 3 | Current severity of the SR. Severity values in the data source are 1-4, and the Severity Name fields map those values to the Unified Enterprises offering's severity names. 1. = "1 - Critical business system down" 2. = "A Critical business system degraded" 3. = "B - Moderate business impact" 4. = "C - Minor business impact" |
|
| CurrentSeverity | ✔️ | ✔️ | ✔️ | B - Moderate Business impact | Current severity of the SR | |
| MaxSeverity | ✔️ | ✔️ | ✔️ | 2 | Highest severity assigned to the SR during its lifecycle. | |
| MaxSeverityName | ✔️ | ✔️ | ✔️ | A - Critical business system degraded | Highest severity assigned to the SR during its lifecycle. Severity values in the data source are 1-4, and the Severity Name fields map those values to the Unified Enterprise offering’s severity names. 1. = "1 - Critical business system down" 2. = "A Critical business system degraded" 3. = "B - Moderate business impact" 4. = "C - Minor business impact" |
|
| IsCritSit | ✔️ | ✔️ | TRUE | Flag that SR has a Critical Situation (CritSit) severity (Sev1 or SevA) | ||
| Country | ✔️ | ✔️ | ✔️ | United States | Country/region of the support request submitter | |
| Product | ✔️ | ✔️ | ✔️ | Virtual Machine Scale Sets | The Microsoft product the SR is related to | |
| ProductFamily | ✔️ | ✔️ | ✔️ | Azure | A grouping of related Microsoft products | |
| Cloud | ✔️ | ✔️ | ✔️ | Azure | Simplified groupings of related Microsoft products (Azure, D365, M365, Onprem or Others) | |
| Created | ✔️ | ✔️ | ✔️ | 12/14/2021 09:55:09 | SR created timestamp | |
| Closed | ✔️ | ✔️ | ✔️ | 1/7/2022 22:52 | SR closed timestamp | |
| LastEmailInteraction | ✔️ | 12/14/2021 09:55:09 | Last SR email interaction timestamp | |||
| CreatedYear | ✔️ | ✔️ | ✔️ | 2021 | Calendar year from the Created timestamp | |
| CreatedMonth | ✔️ | ✔️ | ✔️ | May | Calendar month from the Created timestamp | |
| CreatedDay | ✔️ | ✔️ | ✔️ | Thu | Day of the week from the Created timestamp | |
| CreatedHour | ✔️ | ✔️ | ✔️ | 9:00 | Hour of the day from the Created timestamp | |
| ImpactStartMonth | ✔️ | ✔️ | ✔️ | 2021-06 | Calendar month from the Created timestamp (used to create month-to-months visuals) | |
| DaysOpen | ✔️ | ✔️ | 4.84 | Number of days SR has been open | ||
| DaysWithoutContact | ✔️ | ✔️ | 1.03 | Time (days) since last email communication from Microsoft Support | ||
| DaysToResolution | ✔️ | ✔️ | 5.68 | Time (days) from support request creation to resolution | ||
| CritElapsedTime | ✔️ | ✔️ | Time a support request has been in a CritSit severity | |||
| ReopenedCount | ✔️ | ✔️ | ✔️ | ✔️ | 0 | Number of times a SR was closed and then reopened |
| SubscriptionId | ✔️ | ✔️ | ✔️ | ✔️ | 11cf11de-11b1-b11a-111d1fd1111 | Azure Subscription ID |
| PackageId | ✔️ | ✔️ | ✔️ | ✔️ | 158111111 | Agreement's package ID that the SR is entitled against |
Grids
| Field Display Name | OrderBy | Select | Data Example | Data Definition |
|---|---|---|---|---|
| RequestId | ✔️ | ✔️ | 211220006000XXXX | Support Request (SR) ID |
| State | ✔️ | ✔️ | Open | SR open/cloased state |
| Status | ✔️ | ✔️ | Duplicate, Disconnect, Initial Contact Pending, Request to Revolve, Resolved, Resolved by Customer, Transferred from External, Troubleshooting, Un-Resovled | The state of an active case. |
| InitialSeverity | ✔️ | ✔️ | 4 | SR severity set by the support request submitter Severity values in the data source are 1-4, and the Severity Name fields map those values to the Unified Enterprises offering's severity names. 1. = "1 - Critical business system down" 2. = "A Critical business system degraded" 3. = "B - Moderate business impact" 4. = "C - Minor business impact" |
| InitialSeverityName | ✔️ | ✔️ | C - Minor business impact | SR severity set by the support request submitter |
| Severity | ✔️ | ✔️ | 3 | Current severity of the SR. Severity values in the data source are 1-4, and the Severity Name fields map those values to the Unified Enterprises offering's severity names. 1. = "1 - Critical business system down" 2. = "A Critical business system degraded" 3. = "B - Moderate business impact" 4. = "C - Minor business impact" |
| CurrentSeverity | ✔️ | ✔️ | B - Moderate business impact | Current severity of the SR |
| MaxSeverity | ✔️ | ✔️ | 2 | Highest severity assigned to the SR during its lifecycle |
| MaxSeverityName | ✔️ | ✔️ | A - Critical business system degraded | Highest severity assigned to the SR during its lifecycle. Severity values in the data source are 1-4, and the Severity Name fields map those values to the Unified Enterprises offering's severity names. 1. = "1 - Critical business system down" 2. = "A Critical business system degraded" 3. = "B - Moderate business impact" 4. = "C - Minor business impact" |
| IsCritSit | ✔️ | ✔️ | TRUE | Flag that SR has a Critical Situation (CritSit) severity (Sev1 or SevA) |
| Country | ✔️ | ✔️ | United States | Country/region of the support request submitter |
| Product | ✔️ | ✔️ | Virtual Machine Scale Sets | |
| ProductFamily | ✔️ | ✔️ | Azure | A grouping of related Microsoft products |
| Cloud | ✔️ | ✔️ | Azure | Simplified groupings of related Microsoft products (Azure, D365, M365, Onprem or Others) |
| Created | ✔️ | ✔️ | 12/14/2021 09:55:09 | SR created timestamp |
| Closed | ✔️ | ✔️ | 1/7/2022 22:52 | SR closed timestamp |
| LastEmailInteraction | ✔️ | ✔️ | 12/14/2021 09:55:09 | Last SR email interaction timestamp |
| CreatedYear | ✔️ | ✔️ | 2021 | Calendar year from the Created timestamp |
| CreatedMonth | ✔️ | ✔️ | May | Calendar month from the Created timestamp |
| CreatedDay | ✔️ | ✔️ | Thu | Day of the week from the Created timestamp |
| CreatedHour | ✔️ | ✔️ | 9:00 | Hour of the day from the Created timestamp |
| ImpactStartMonth | ✔️ | 2021-06 | Calendar month from the Created timestamp (used to create month-to-months visuals) | |
| DaysOpen | ✔️ | ✔️ | 4.84 | Number of days SR has been open |
| DaysWithoutContact | ✔️ | ✔️ | 1.03 | Time (days) since last email communication from Microsft Support |
| DaysToResolution | ✔️ | ✔️ | 5.68 | Time (days) from support request creation to resolution |
| CritElapsedTime | ✔️ | ✔️ | Time a support request has been in a CritSit severity | |
| ReopenedCount | ✔️ | ✔️ | 0 | |
| SubscriptionId | ✔️ | ✔️ | 11cf11de-11b1-b11a-111d1fd1111 | Azure Subscription ID |
| PackageId | ✔️ | ✔️ | 158111111 | Agreement's package ID that the SR is entitled against |
| Case Title | ✔️ | ✔️ | SQL Server performance issue | The title of the case with PII redactions |
| Case Type | ✔️ | ✔️ | Advisory/Incident | Defines the nature of the case, whether a problem/incident or advisory |
| Is associated with Service Impacting Event | ✔️ | ✔️ | True/False | Defines whether a case has been tagged as associated with a known cloud service impacting event |
| Support Topic | ✔️ | ✔️ | Azure App Configuration | The third level down in the support area path beyond Product Family and Product |
| Tenant ID | ✔️ | ✔️ | x0xxx10-00x0-0x01-0xxx-x0x0x01xx100 | The case is associated with this Tenant ID |
Filters
| Field Display Name | Filter | Data Example | Data Definition |
|---|---|---|---|
| RequestId | 211220006000XXXX | Support Request (SR) ID | |
| State | ✔️ | Open | SR open/closed state |
| Status | ✔️ | Duplicate, Disconnect, Initial Contact Pending, Request to Revolve, Resolved, Resolved by Customer, Transferred from External, Troubleshooting, Un-Resovled. | The state of an active case. |
| InitialSeverity | ✔️ | 4 | SR severity set by the support request submitter Severity values in the data source are 1-4, and the Severity Name fields map those values to the Unified Enterprises offering's severity names. 1. = "1 - Critical business system down" 2. = "A Critical business system degraded" 3. = "B - Moderate business impact" 4. = "C - Minor business impact" |
| InitialSeverityName | C - Minor Business impact | SR severity set by the support request submitter | |
| Severity | ✔️ | 3 | Current severity of the SR |
| CurrentSeverity | B - Moderate Business impact | Current severity of the SR. Severity values in the data source are 1-4, and the Severity Name fields map those values to the Unified Enterprise offering’s severity names. 1. = "1 - Critical business system down" 2. = "A Critical business system degraded" 3. = "B - Moderate business impact" 4. = "C - Minor business impact" |
|
| MaxSeverity | ✔️ | 2 | Highest severity assigned to the SR during its lifecycle. |
| MaxSeverityName | A - Critical business system degraded | Highest severity assigned to the SR during its lifecycle. Severity values in the data source are 1-4, and the Severity Name fields map those values to the Unified Enterprise offering’s severity names. 1. = "1 - Critical business system down" 2. = "A Critical business system degraded" 3. = "B - Moderate business impact" 4. = "C - Minor business impact" |
|
| IsCritSit | TRUE | Flag that SR has a Critical Situation (CritSit) severity (Sev1 or SevA) | |
| Country | ✔️ | United States | Country/region of the support request submitter |
| Product | ✔️ | Virtual Machine Scale Sets | |
| ProductFamily | ✔️ | Azure | A grouping of related Microsoft products |
| Cloud | ✔️ | Azure | Simplified groupings of related Microsoft products (Azure, D365, M365, Onprem or Others) |
| Created | 12/14/2021 09:55:09 | SR created timestamp | |
| Closed | 1/7/2022 22:52 | SR closed timestamp | |
| LastEmailInteraction | 12/14/2021 09:55:09 | Last SR email interaction timestamp | |
| CreatedYear | 2021 | Calendar year from the Created timestamp | |
| CreatedMonth | May | Calendar month from the Created timestamp | |
| CreatedDay | Thu | Day of the week from the Created timestamp | |
| CreatedHour | 9:00 | Hour of the day from the Created timestamp | |
| ImpactStartMonth | 2021-06 | Calendar month from the Created timestamp (used to create month-to-months visuals) | |
| DaysOpen | ✔️ | 4.84 | Number of days SR has been open |
| DaysWithoutContact | ✔️ | 1.03 | Time (days) since last email communication from Microsoft Support |
| DaysToResolution | 5.68 | Time (days) from support request creation to resolution | |
| CritElapsedTime | Time a support request has been in a CritSit severity | ||
| ReopenedCount | 0 | ||
| SubscriptionId | 11cf11de-11b1-b11a-111d1fd1111 | Azure Subscription ID | |
| PackageId | 158111111 | Agreement's package ID that the SR is entitled against | |
| Case Title | ✔️ | SQL Server performance issue | The title of the support request with PII redactions |
| Case Type | ✔️ | Advisory/Incident | Defines the nature of the case whether a problem/incident or advisory |
| Is associated with Service Impacting Event | ✔️ | True/False | Defines whether a case has been tagged as associated with a known cloud service impacting event |
| Support Topic | ✔️ | Azure App Configuration | The third level down in the support area path beyond Product Family and Product |
| Tenant ID | ✔️ | x0xxx10-00x0-0x01-0xxx-x0x0x01xx100 | The case is associated with this Tenant ID |
Azure Events Data Source
Visuals
| Field Display Name | Axis | Value | Legend | OrderBy | Data Example |
|---|---|---|---|---|---|
| TrackingId | ✔️ | ✔️ | 9MCT-XXX | ||
| Id | /subscriptions/d8f9e0d3-7XXX-4a40-a4f0-XXXXXXXXXXXX/providers/Microsoft.ResourceHealth/events/DXXX-XXX | ||||
| Title | ✔️ | SQL Server IaaS Extension Registration for Windows | |||
| EventType | ✔️ | ✔️ | ✔️ | ✔️ | PlannedMaintenance |
| ImpactStartDate | ✔️ | 2/15/2022 10:29:39 PM | |||
| ImpactStartDay | ✔️ | ✔️ | ✔️ | Mon | |
| ImpactStartMonth | ✔️ | ✔️ | ✔️ | 2022-02 | |
| ImpactStartYear | ✔️ | ✔️ | ✔️ | 2022 | |
| ImpactMitigationDate | ✔️ | 2/20/2022 12:00:00 AM | |||
| Status | ✔️ | ✔️ | ✔️ | Active | |
| Priority | ✔️ | ✔️ | 20 | ||
| ExternalIncidentId | 2881XXXXX | ||||
| Level | ✔️ | ✔️ | ✔️ | Warning | |
| EventLevel | ✔️ | ✔️ | ✔️ | Informational | |
| PlatformInitiated | ✔️ | ✔️ | ✔️ | True | |
| Header | Your service might have been impacted by an Azure service issue | ||||
| EventSource | ✔️ | ✔️ | ✔️ | ServiceHealth | |
| ImpactedRegions | ✔️ | ✔️ | 1 | ||
| ImpactedRegion | ✔️ | ✔️ | ✔️ | Global | |
| ImpactedService | ✔️ | ✔️ | ✔️ | Virtual Machines | |
| DaysToResolution | ✔️ | ✔️ | 30 | ||
| MinutesToResolution | ✔️ | ✔️ | 43200 | ||
| EventDate | ✔️ | 2/20/2022 3:12:06 AM | |||
| ImpactedSubscriptionCount | ✔️ | ✔️ | 4 | ||
| ImpactedSubscriptions | ✔️ | ✔️ | 0XXXXe10-ceaX-XXa1-XXXc-f102bdXXXXXX, etc. | ||
| ImpactedSubscriptionDisplay | ✔️ | ✔️ | 0XXXXe10-ceaX-XXa1-XXXc-f102bdXXXXXX, etc. |
Grids
| Field Display Name | OrderBy | Select | Data Example |
|---|---|---|---|
| TrackingId | ✔️ | ✔️ | 9MCT-XXX |
| Id | ✔️ | /subscriptions/d8f9e0d3-7XXX-4a40-a4f0-XXXXXXXXXXXX/providers/Microsoft.ResourceHealth/events/DXXX-XXX | |
| Title | ✔️ | ✔️ | SQL Server IaaS Extension Registration for Windows |
| EventType | ✔️ | ✔️ | PlannedMaintenance |
| ImpactStartDate | ✔️ | ✔️ | 2/15/2022 10:29:39 PM |
| ImpactStartDay | ✔️ | ✔️ | Mon |
| ImpactStartMonth | ✔️ | ✔️ | 2022-02 |
| ImpactStartYear | ✔️ | ✔️ | 2022 |
| ImpactMitigationDate | ✔️ | ✔️ | 2/20/2022 12:00:00 AM |
| Status | ✔️ | ✔️ | Active |
| Priority | ✔️ | ✔️ | 20 |
| ExternalIncidentId | ✔️ | 2881XXXXX | |
| Level | ✔️ | ✔️ | Warning |
| EventLevel | ✔️ | ✔️ | Informational |
| PlatformInitiated | ✔️ | ✔️ | True |
| Header | ✔️ | Your service might have been impacted by an Azure service issue | |
| EventSource | ✔️ | ✔️ | ServiceHealth |
| ImpactedRegions | ✔️ | ✔️ | 1 |
| ImpactedRegion | ✔️ | ✔️ | Global |
| ImpactedService | ✔️ | ✔️ | Virtual Machines |
| DaysToResolution | ✔️ | ✔️ | 30 |
| MinutesToResolution | ✔️ | ✔️ | 43200 |
| EventDate | ✔️ | ✔️ | 2/20/2022 3:12:06 AM |
| ImpactedSubscriptionCount | ✔️ | ✔️ | 4 |
| ImpactedSubscriptions | ✔️ | ✔️ | 0XXXXe10-ceaX-XXa1-XXXc-f102bdXXXXXX, etc. |
| ImpactedSubscriptionDisplay | ✔️ | ✔️ | 0XXXXe10-ceaX-XXa1-XXXc-f102bdXXXXXX, etc. |
Filters
| Field Display Name | Filter | Data Example |
|---|---|---|
| TrackingId | ✔️ | 9MCT-XXX |
| Id | /subscriptions/d8f9e0d3-7XXX-4a40-a4f0-XXXXXXXXXXXX/providers/Microsoft.ResourceHealth/events/DXXX-XXX | |
| Title | SQL Server IaaS Extension Registration for Windows | |
| EventType | ✔️ | PlannedMaintenance |
| ImpactStartDate | 2/15/2022 10:29:39 PM | |
| ImpactStartDay | ✔️ | Mon |
| ImpactStartMonth | ✔️ | 2022-02 |
| ImpactStartYear | ✔️ | 2022 |
| ImpactMitigationDate | 2/20/2022 12:00:00 AM | |
| Status | ✔️ | Active |
| Priority | ✔️ | 20 |
| ExternalIncidentId | 2881XXXXX | |
| Level | ✔️ | Warning |
| EventLevel | ✔️ | Informational |
| PlatformInitiated | True | |
| Header | Your service might have been impacted by an Azure service issue | |
| EventSource | ✔️ | ServiceHealth |
| ImpactedRegions | 1 | |
| ImpactedRegion | ✔️ | Global |
| ImpactedService | ✔️ | Virtual Machines |
| DaysToResolution | 30 | |
| MinutesToResolution | 43200 | |
| EventDate | ✔️ | 2/20/2022 3:12:06 AM |
| ImpactedSubscriptionCount | ✔️ | 4 |
| ImpactedSubscriptions | ✔️ | 0XXXXe10-ceaX-XXa1-XXXc-f102bdXXXXXX, etc. |
| ImpactedSubscriptionDisplay | ✔️ | 0XXXXe10-ceaX-XXa1-XXXc-f102bdXXXXXX, etc. |
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for