Merge pull request #107500 from lyrana/troubleshoot-updates-key

Troubleshoot updates key

Author: v-shils

articles/time-series-insights/media/diagnose-and-solve-problems/update-hub-key-step-1.png

@@ -95,6 +95,22 @@ To fix the lag:
 
 2. When the lag is caught up, decrease the SKU capacity to your normal ingress rate.
 
+## Problem: data was showing previously but is no longer showing
+
+TSI is no longer ingesting data but events are still streaming into Iot Hub or Event Hub
+
+### Cause A: your hub access key was regenerated and your environment needs updating
+
+This problem occurs when the key provided when creating your event source is no longer valid. You would see telemetry in your hub but no Ingress Received Messages in Time Series Insights. If you are unsure whether or not the key was regenerated you can search your Event Hubs' Activity log for "Create or Update Namespace Authorization Rules" or search "Create or update IotHub Resource" for IoT hub.
+
+To update your Time Series Insights environment with the new key open your hub resource in the Azure portal and copy the new key. Navigate to your TSI resource and click on Event Sources. 
+
+   [![Update key.](media/diagnose-and-solve-problems/update-hub-key-step-1.png)](media/diagnose-and-solve-problems/update-hub-key-step-1.png#lightbox)
+
+Select the event source(s) that have from which ingestion has stopped, paste in the new key and click Save.
+
+   [![Update key.](media/diagnose-and-solve-problems/update-hub-key-step-2.png)](media/diagnose-and-solve-problems/update-hub-key-step-2.png#lightbox)
+
 ## Problem: my event source's timestamp property name setting doesn't work
 
 Ensure that the timestamp property name and value conform to the following rules:

articles/time-series-insights/media/diagnose-and-solve-problems/update-hub-key-step-2.png

@@ -68,6 +68,20 @@ You might be sending data without the Time Series ID.
     > [!NOTE]
     > At this time, Time Series Insights supports a maximum ingestion rate of 6 Mbps.
 
+## Problem: Data was showing, but now ingestion has stopped
+
+- Your event source key may have been regenerate and your Preview environment needs the new event source key.
+
+This problem occurs when the key provided when creating your event source is no longer valid. You would see telemetry in your hub but no Ingress Received Messages in Time Series Insights. If you are unsure whether or not the key was regenerated you can search your Event Hubs' Activity log for "Create or Update Namespace Authorization Rules" or search "Create or update IotHub Resource" for IoT hub. 
+
+To update your Time Series Insights Preview environment with the new key open your hub resource in the Azure portal and copy the new key. Navigate to your TSI resource and click on Event Sources. 
+
+   [![Update key.](media/preview-troubleshoot/update-hub-key-step-1.png)](media/preview-troubleshoot/update-hub-key-step-1.png#lightbox)
+
+Select the event source(s) that have from which ingestion has stopped, paste in the new key and click Save.
+
+   [![Update key.](media/preview-troubleshoot/update-hub-key-step-2.png)](media/preview-troubleshoot/update-hub-key-step-2.png#lightbox)
+
 ## Problem: My event source's Timestamp property name doesn't work
 
 Ensure that the name and value conform to the following rules: