Incidents 2020 – /IOTCONNECT™
| Incident Number | 2020.01 |
|---|---|
| Date | 13-Nov-20 |
| Issue | Unable to login to Portal |
| Priority | High |
| Issued By | Internal Support Team & Customers |
| Impact | /IOTCONNECT™ Portal. Device Data were not impacted |
| Root Cause | Node Server hosting UI services was crashed |
| Resolution | Rebuilt service and restart in All VM to back things to normal |
| Incident Number | 2020.02 |
|---|---|
| Date | 21-Oct-20 |
| Issue | Stream Issue |
| Priority | High |
| Issued By | Internal Support Team(MS Support Ticket#120102123001615) |
| Impact | Historical, Custom connectors & metering data insertion |
| Root Cause | Stream job getting failed due to one of the Cosmos’ partitionKey limit reached to 20GB |
| Resolution | Removed data of the partitionKey from the cosmos under the limit and restored missing data during this period |
| Incident Number | 2020.03 |
|---|---|
| Date | 18-Sep-20 |
| Issue | Stream Issue |
| Priority | High |
| Issued By | Internal Support Team |
| Impact | Historical, Custom connectors & metering data insertion |
| Root Cause | Stream job getting failed due to Cosmos SAS Key changed of customer |
| Resolution | Updated valid data to the cosmos config and backup & restore of missing data during this period |
| Incident Number | 2020.04 |
|---|---|
| Date | 2-Jul-20 |
| Issue | VM Carsh |
| Priority | High |
| Issued By | Internal Support Team |
| Impact | Device Data Processing and Rule Evalution |
| Root Cause | Hard Drive of VMS were disconnected due to Router Prapogation |
| Resolution | MS Support team rebuilt VM and attached HDD backup |