Skip to content

Commit 029e0cf

Browse files
pthippeswamyfauhse
andauthored
Apply suggestions from code review
Co-authored-by: Fabian Uhse <[email protected]>
1 parent 0fac846 commit 029e0cf

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/storage-discovery/egress-insights.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.author: pthippeswamy
1111

1212
# Understand egress insights in Azure Storage Discovery
1313

14-
Data egress - the transfer of data out of your Azure Blob Storage accounts - is a significant cost driver for many organizations. Understanding where egress occurs, how it trends over time, and which storage accounts contribute the most helps you make informed decisions about cost optimization and architecture improvements.
14+
Understanding the data egress - the transfer of data out of your storage accounts - can reveal cost and safety insights. Understanding where egress occurs, how it trends over time, and which storage accounts contribute the most helps you make informed decisions about cost optimization and architecture improvements.
1515

1616
Azure Storage Discovery surfaces egress insights as part of the **Activity** report in your Discovery workspace. These insights give you enterprise-wide visibility into egress patterns without requiring custom queries, log analytics, or additional tooling.
1717

@@ -35,11 +35,11 @@ At the top of the Activity report, overview tiles show aggregate metrics for you
3535

3636
## Egress trends
3737

38-
The **Trends** chart in the Activity report shows how egress volume changes over time. This visualization helps you:
38+
The **Trends** chart in the Activity report shows how egress volume changes over time:
3939

4040
- **Identify spikes**: Spot sudden increases in egress that might indicate unexpected data transfers or workload changes.
4141
- **Track patterns**: Observe recurring egress patterns tied to business cycles, batch processing, or scheduled data pipelines.
42-
- **Monitor optimization efforts**: After making changes like moving workloads closer to data or adjusting caching, track whether egress decreases over time.
42+
- **Monitor optimization efforts**: After making changes like moving workloads closer to data or adjusting caching, you can track how your actions change egress over time.
4343

4444
You can group egress trends by dimensions such as:
4545

0 commit comments

Comments
 (0)