You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/time-series-insights/time-series-insights-environment-mitigate-latency.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ You are most likely to experience latency and throttling when you:
25
25
- Add an event source that contains old data that may exceed your allotted ingress rate (Time Series Insights will need to catch up).
26
26
- Add more event sources to an environment, resulting in a spike from additional events (which could exceed your environment’s capacity).
27
27
- 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 event 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.
Copy file name to clipboardExpand all lines: articles/time-series-insights/time-series-insights-environment-planning.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,9 +74,7 @@ You can adjust retention and toggle between the two modes on the environment’s
74
74
75
75
### Environment planning
76
76
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.
80
78
81
79
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.
Copy file name to clipboardExpand all lines: includes/time-series-insights-ga-limits.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,27 +15,27 @@ The following summarizes key limits in General Availability.
15
15
16
16
### SKU ingress rates and capacities
17
17
18
-
S1 and S2 SKU ingress rates and capacities provide flexibility when configuring a new Time Series Insights environment.
18
+
S1 and S2 SKU ingress rates and capacities provide flexibility when configuring a new Time Series Insights environment. Your SKU capacity indicates your daily ingress rate based on number of events or bytes stored, whichever comes first. Note that ingress is measured *per minute*, and **throttling** is applied using the token bucket algorithm. Ingress is measured in 1-KB blocks. For example a 0.8-KB actual event would be measured as one event, and a 2.6-KB event is counted as three events.
| 1 | 10 GB (10 million events) | 300 GB (300 million events) per month |
28
-
| 10 | 100 GB (100 million events) | 3 TB (3 billion events) per month |
27
+
| 1 | 10 GB (10 million events) per day | 300 GB (300 million events) per month |
28
+
| 10 | 100 GB (100 million events) per day | 3 TB (3 billion events) per month |
29
29
30
30
> [!NOTE]
31
31
> Capacities scale linearly, so an S1 SKU with capacity 2 supports 2 GB (2 million) events per day ingress rate and 60 GB (60 million events) per month.
32
32
33
33
S2 SKU environments support substantially more events per month and have a significantly higher ingress capacity.
34
34
35
-
| SKU | Event count per month | Event size per month | Event count per minute | Event size per minute |
35
+
| SKU | Event count per month | Event count per minute | Event size per minute |
0 commit comments