Skip to content

Commit db4ffee

Browse files
committed
absolute urls fix
1 parent b516a0d commit db4ffee

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/time-series-insights/time-series-insights-update-storage-ingress.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ When planning your Time Series Insights environment, it's important to consider
111111

112112
A *partition* is an ordered sequence of events held in a hub. The partition count is set during the hub creation phase and cannot be changed.
113113

114-
For Event Hubs partitioning best practices, review [How many partitions do I need?](../event-hubs/event-hubs-faq#how-many-partitions-do-i-need)
114+
For Event Hubs partitioning best practices, review [How many partitions do I need?](https://docs.microsoft.com/azure/event-hubs/event-hubs-faq#how-many-partitions-do-i-need)
115115

116116
> [!NOTE]
117117
> Most IoT Hubs used with Azure Time Series Insights only need four partitions.
@@ -145,9 +145,9 @@ We recommend the following:
145145

146146
Refer to the following resources to learn more about optimizing hub throughput and partitions:
147147

148-
* [IoT Hub Scale](../iot-hub/iot-hub-scaling)
149-
* [Event Hub Scale](../event-hubs/event-hubs-scalability#throughput-units)
150-
* [Event Hub Partitions](../event-hubs/event-hubs-features#partitions)
148+
* [IoT Hub Scale](https://docs.microsoft.com/azure/iot-hub/iot-hub-scaling)
149+
* [Event Hub Scale](https://docs.microsoft.com/azure/event-hubs/event-hubs-scalability#throughput-units)
150+
* [Event Hub Partitions](https://docs.microsoft.com/azure/event-hubs/event-hubs-features#partitions)
151151

152152
### Data storage
153153

0 commit comments

Comments
 (0)