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
@@ -9,26 +9,26 @@ Learn more about performance monitoring in:
9
9
10
10
-[Homepage]({% link _documentation/performance/performance-homepage.md %}): displays a high-level report of application health, including problematic transactions and both Apdex and Throughput graphs
11
11
-[Distributed Tracing]({% link _documentation/performance/distributed-tracing.md %}): diagnose problems and view interactions across your software systems
12
-
-[Metrics]({% link _documentation/performance/performance-metrics.md %}): provides insight into user experience of your application based on custom thresholds
12
+
-[Metrics]({% link _documentation/performance/metrics.md %}): provides insight into user experience of your application based on custom thresholds
13
13
-[Discover]({% link _documentation/performance/discover/index.md %}): view data across environments with pre-built queries. Customers subscribed to the Team or Business plan can use Discover to view comprehensive information sent to Sentry.
14
14
15
15
## Install
16
16
17
-
{% include components/platform_content.html content_dir='getting-started' %}
17
+
{% include components/platform_content.html content_dir='configuration' %}
18
18
19
19
## Navigating Performance Data
20
20
21
21
Sentry provides several tools to explore your application's performance data and uncover problems.
22
22
23
23
The **Performance homepage** is our center for monitoring how your application is doing. Here, you can view a list of all your endpoints and transactions and view a summary of any transaction in your application. Learn more about the [Homepage]({% link _documentation/performance/performance-homepage.md %}).
24
24
25
-
[{% asset performance/performance-homepage-main-example.png alt="Example of Performance in Product UI" %}]({% asset performance/performance-homepage-main-example.png @path %})
25
+
[{% asset performance/perf-homepage.png alt="Example of Performance in Product UI" %}]({% asset performance/perf-homepage.png @path %})
26
26
27
27
**Discover** is our custom business intelligence query builder that can help you answer questions about your data and analyze metrics. Learn more about [Discover]({% link _documentation/performance/discover/index.md %}).
**Transaction Details** lets you examine an individual transaction event in detail. Here spans are visualized to help you identify slow HTTP requests, slow database queries, and other bottlenecks. You can also jump to other transactions within the trace, and identify associated errors. Learn more about [Distributed Tracing]({% link _documentation/performance/distributed-tracing.md %}) and the [Transaction Details page]({% link _documentation/performance/distributed-tracing.md %}#transaction-detail-viewpage).
Copy file name to clipboardExpand all lines: src/collections/_documentation/performance/distributed-tracing.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -271,13 +271,13 @@ This view also includes a timeseries graph, aggregating all results of the query
271
271
272
272
_Note:_ Currently, only transaction data - the transaction name and any attributes the transaction inherits from its root span - is searchable. Data contained in spans other than the root span is not indexed and therefore cannot be searched.
273
273
274
-
For more details about the transaction list view, see the full documentation on [Discover's Query Builder]({%- link _documentation/performance/discover/query-builder.md -%}), and for more about transaction metrics, see [Performance Metrics]({%- link _documentation/performance/performance-metrics.md -%}#transaction-metrics).
274
+
For more details about the transaction list view, see the full documentation on [Discover's Query Builder]({%- link _documentation/performance/discover/query-builder.md -%}), and for more about transaction metrics, see [Performance Metrics]({%- link _documentation/performance/metrics.md -%}#transaction-metrics).
275
275
276
276
### Transaction Detail View
277
277
278
278
When you open a transaction event in Discover (by clicking on the icon at the left side of the row), you'll see the **span view** at the top of the page. Other information the SDK captured as part of the transaction event (such as the transaction's tags and automatically collected breadcrumbs) is displayed underneath and to the right of the span view.
279
279
280
-
[{% asset performance/discover-span.png alt="Discover span showing the map of the transactions (aka minimap) and the black dashed handlebars for adjusting the window selection." %}]({% asset performance/discover-span.png @path %})
280
+
[{% asset performance/perf-event-detail.png alt="Discover span showing the map of the transactions (aka minimap) and the black dashed handlebars for adjusting the window selection." %}]({% asset performance/perf-event-detail.png @path %})
281
281
282
282
#### Using the Span View
283
283
@@ -297,7 +297,7 @@ _Viewing Span Details_
297
297
298
298
Clicking on a row in the span view expands the details of that span. From here, you can see all attached properties, such as tags and data.
299
299
300
-
[{% asset performance/span-detail-view.png alt="Span detail view shows the span id, trace id, parent span id, and other data such as tags." %}]({% asset performance/span-detail-view.png @path %})
300
+
[{% asset performance/span-details.png alt="Span detail view shows the span id, trace id, parent span id, and other data such as tags." %}]({% asset performance/span-details.png @path %})
Copy file name to clipboardExpand all lines: src/collections/_documentation/performance/performance-homepage.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -11,15 +11,15 @@ Sentry's Performance features are currently in beta. For more details about acce
11
11
level="warning"
12
12
%}
13
13
14
-
The Performance Homepage offers [Apdex]({%- link _documentation/performance/performance-metrics.md -%}#apdex) and [Throughput]({%- link _documentation/performance/performance-metrics.md -%}#throughput-total-rpm-rps) graphs as well as a list of the most problematic transactions to display a high-level report of their overall application health.
14
+
The Performance Homepage offers [Apdex]({%- link _documentation/performance/metrics.md -%}#apdex) and [Throughput]({%- link _documentation/performance/metrics.md -%}#throughput-total-rpm-rps) graphs as well as a list of the most problematic transactions to display a high-level report of their overall application health.
15
15
16
16
## Apdex & Throughput Graphs
17
-
The [Apdex]({%- link _documentation/performance/performance-metrics.md -%}#apdex) graph displays the ratio of response times in an application measured against a threshold. This information is displayed as an aggregate to provide a sense of how long a customer has waited. For example, if the Apdex score dips significantly during a given time period, you may want to investigate that time period for a potential performance bottleneck.
17
+
The [Apdex]({%- link _documentation/performance/metrics.md -%}#apdex) graph displays the ratio of response times in an application measured against a threshold. This information is displayed as an aggregate to provide a sense of how long a customer has waited. For example, if the Apdex score dips significantly during a given time period, you may want to investigate that time period for a potential performance bottleneck.
18
18
19
19
The Throughput graph indicates the number of transactions over a given time range. You can quickly visualize the traffic patterns in your application and see if a spike in throughput might be correlated with a dip in your Apdex score.
20
20
21
21
## Transaction Table
22
-
Underneath the graphs, view a list of your transactions with the capability to filter down on which transactions you want to view. In this table, sort on the provided columns to understand key characteristics of your transactions like [P95]({%- link _documentation/performance/performance-metrics.md -%}#p95-threshold) duration time, [Average Transaction Duration]({%- link _documentation/performance/performance-metrics.md -%}#average-transaction-duration) time, or [Throughput]({%- link _documentation/performance/performance-metrics.md -%}#throughput-total-rpm-rps).
22
+
Underneath the graphs, view a list of your transactions with the capability to filter down on which transactions you want to view. In this table, sort on the provided columns to understand key characteristics of your transactions like [P95]({%- link _documentation/performance/metrics.md -%}#p95-threshold) duration time, [Average Transaction Duration]({%- link _documentation/performance/metrics.md -%}#average-transaction-duration) time, or [Throughput]({%- link _documentation/performance/metrics.md -%}#throughput-total-rpm-rps).
23
23
24
24
## My Key Transactions
25
25
"My Key Transactions" are transactions that you bookmark and can view in a separate dedicated tab. You may want to bookmark a Transaction as a "Key Transaction" if you monitor performance on a particular transaction or group of transactions. You can set a Transaction as a "Key Transaction" on the Transaction Summary page. The "All Transactions" view also displays these transactions.
@@ -30,7 +30,7 @@ Navigate to the Transaction Summary page by clicking on any transaction on the P
30
30
31
31
## Transaction Summary Graphs
32
32
Duration Breakdown
33
-
: By graphing P50, [P75]({%- link _documentation/performance/performance-metrics.md -%}#p75-threshold), [P95]({%- link _documentation/performance/performance-metrics.md -%}#p95-threshold), [P99]({%- link _documentation/performance/performance-metrics.md -%}#p99-threshold), and P100 durations distinctly, you can utilize this display to see their transaction performance over time. Toggle the display of each segment by clicking on the legend (including Releases). Also, zoom in on specific slices to investigate spikes or possible performance regressions from a release.
33
+
: By graphing P50, [P75]({%- link _documentation/performance/metrics.md -%}#p75-threshold), [P95]({%- link _documentation/performance/metrics.md -%}#p95-threshold), [P99]({%- link _documentation/performance/metrics.md -%}#p99-threshold), and P100 durations distinctly, you can utilize this display to see their transaction performance over time. Toggle the display of each segment by clicking on the legend (including Releases). Also, zoom in on specific slices to investigate spikes or possible performance regressions from a release.
34
34
35
35
Latency Histogram
36
36
: Visualize the frequency of transactions that occur within each response time segment. This histogram view can help you understand the shape of transaction response times and quickly see outliers. Click on specific segments to drill down for more granularity.
@@ -39,7 +39,7 @@ Apdex / Throughput Graphs
39
39
: See the same graphs from the Performance homepage isolated to a specific transaction. Zoom in to investigate spikes and see potential correlations between Apdex and Throughput.
40
40
41
41
Duration Percentiles
42
-
: This graph shows the [average transaction duration]({%- link _documentation/performance/performance-metrics.md -%}#average-transaction-duration) across distinct percentiles. For example, see how different the P50 and P99 response time durations are for a given transaction and understand the rate of increase between segments.
42
+
: This graph shows the [average transaction duration]({%- link _documentation/performance/metrics.md -%}#average-transaction-duration) across distinct percentiles. For example, see how different the P50 and P99 response time durations are for a given transaction and understand the rate of increase between segments.
43
43
44
44
## Sidebar
45
45
The sidebar contains a Tag Summary, [Apdex/Throughput](#apdex--throughput-graphs) graphs, error rate graphs, and more statistics about the transaction. This information updates dynamically if you change any of the selections in the global header or when you drill in on a latency segment (applicable when viewing the Latency Histogram).
0 commit comments