Skip to content

Commit 89d94a6

Browse files
author
Lyrana Hughes
committed
updating preview troubleshoot docs
1 parent 14dea1b commit 89d94a6

File tree

3 files changed

+14
-0
lines changed

3 files changed

+14
-0
lines changed
45 KB
Loading
30.5 KB
Loading

articles/time-series-insights/time-series-insights-update-how-to-troubleshoot.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,20 @@ You might be sending data without the Time Series ID.
6868
> [!NOTE]
6969
> At this time, Time Series Insights supports a maximum ingestion rate of 6 Mbps.
7070
71+
## Problem: Data was showing, but now ingestion has stopped
72+
73+
- Your event source key may have been regenerate and your Preview environment needs the new event source key.
74+
75+
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.
76+
77+
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.
78+
79+
[![Update key.](media/preview-troubleshoot/update-hub-key-step-1.png)](media/preview-troubleshoot/update-hub-key-step-1#lightbox)
80+
81+
Select the event source(s) that have from which ingestion has stopped, paste in the new key and click Save.
82+
83+
[![Update key.](media/preview-troubleshoot/update-hub-key-step-2.png)](media/preview-troubleshoot/update-hub-key-step-2#lightbox)
84+
7185
## Problem: My event source's Timestamp property name doesn't work
7286

7387
Ensure that the name and value conform to the following rules:

0 commit comments

Comments
 (0)