We've confirmed that all systems are back to normal at 1/24, 21:55 UTC. Our logs show the incident started on 1/24, 20:40 UTC and that during 1 hour 15 min that it took to resolve the issue customers in Central India experienced data loss in heartbeat events.
Root Cause: The failure was due to incorrect configuration value during migration of heartbeat datatype.
Incident Timeline: 1 Hour & 15 minutes -1/24, 20:40 UTC through 1/24, 21:55 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.