Skip to content

Commit e750e87

Browse files
author
Lyrana Hughes
committed
cleaning up env planning section
1 parent fbbad4b commit e750e87

File tree

2 files changed

+2
-4
lines changed

2 files changed

+2
-4
lines changed

articles/time-series-insights/time-series-insights-environment-mitigate-latency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ You are most likely to experience latency and throttling when you:
2525
- Add an event source that contains old data that may exceed your allotted ingress rate (Time Series Insights will need to catch up).
2626
- Add more event sources to an environment, resulting in a spike from additional events (which could exceed your environment’s capacity).
2727
- Push large amounts of historical events to an event source, resulting in a lag (Time Series Insights will need to catch up).
28-
- Join reference data with telemetry, resulting in larger event size. From a throttling perspective, an ingressed data packet with a packet size of 32 KB is treated as 32 events, each sized 1 KB. The maximum allowed packet size is 32 KB; data packets larger than 32 KB are truncated.
28+
- Join reference data with telemetry, resulting in larger event size. The maximum allowed packet size is 32 KB; data packets larger than 32 KB are truncated.
2929

3030
## Video
3131

articles/time-series-insights/time-series-insights-environment-planning.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -74,9 +74,7 @@ You can adjust retention and toggle between the two modes on the environment’s
7474

7575
### Environment planning
7676

77-
The second area to focus on for planning your Time Series Insights environment is ingress capacity. Ingress capacity is a derivative of the per-minute allocation.
78-
79-
From a throttling perspective, an ingressed data packet that has a packet size of 32 KB is treated as 32 events, each 1 KB in size. The maximum allowed event size is 32 KB. Data packets larger than 32 KB are truncated.
77+
The second area to focus on for planning your Time Series Insights environment is ingress capacity. The daily ingress storage and event capacity is measured per minute, in 1-KB blocks. The maximum allowed packet size is 32 KB. Data packets larger than 32 KB are truncated.
8078

8179
You can increase the capacity of an S1 or S2 SKU to 10 units in a single environment. You can't migrate from an S1 environment to an S2. You can't migrate from an S2 environment to an S1.
8280

0 commit comments

Comments
 (0)