Incidents 2019 – IoTConnect
Incident Number | 2019.01 |
---|---|
Date | 14-Sep-19 |
Issue | DNS Prapogation Issue |
Priority | High |
Issued By | Internal Support Team & Customers |
Impact | All Micro Services. No impact on Device Data |
Root Cause | DNS Resolution issue in all Azure VMs and Azure App Services |
Resolution | Microsoft Team help to fix these issues form Azure VM standpoint. |
Incident Number | 2019.02 |
---|---|
Date | 23-Jul-19 |
Issue | Database connection pool exceeded. Request number increases due to database connectivity issue |
Priority | High |
Issued By | Internal Support Team |
Impact | Agent micro Service. Device Initial Connectivity. No impact on Device Data |
Root Cause | Request getting failed due to dB issue |
Resolution | Scale out the app service to create more concurrent database connection |
Incident Number | 2019.03 |
---|---|
Date | 13-Jul-19 |
Issue | An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full SQL Database from app service. |
Priority | High |
Issued By | Internal Support Team & Customers |
Impact | Agent micro Service. Device Initial Connectivity. No impact on Device Data |
Root Cause | It’s due to azure app service existed with outbound port usages. |
Resolution | Increase the resources of app service |
Incident Number | 2019.04 |
---|---|
Date | 18-May-19 |
Issue | Device get disconnected after 2 hours for specific account of platform. |
Priority | Medium |
Issued By | Customers |
Impact | Device Connectivity |
Root Cause | For security reason device password expiry was 2 hrs |
Resolution | Increased password expiry for specific account |
Incident Number | 2019.05 |
---|---|
Date | 27-Apr-19 |
Issue | Device Telemetry was not getting display in platform |
Priority | Medium |
Issued By | Customers |
Impact | Live Telemetry |
Root Cause | RabbitMQ broker exhausted with open socket connection |
Resolution | Increase number of socket connection and added more cluster to RabbitMQ |