Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fixes
  • Loading branch information
marandaneto committed Dec 5, 2022
commit f49f8043e6029c33809a4feb703268d51a9e0ff1
Original file line number Diff line number Diff line change
Expand Up @@ -34,12 +34,12 @@ Learn more in our [Dio integration documentation](/platforms/dart/configuration/

### File I/O Instrumentation

The Sentry-specific file I/O implementation starts a span out of the active span, bound to the scope for each file I/O operation. The SDK sets the span `operation` to `file.copy`/`file.write`/`file.delete`/`file.open`/`file.read`/`file.rename` and `description` to `filename` (for example, `file.txt`).
The Sentry-specific file I/O implementation starts a span out of the active span, bound to the scope for each file I/O operation. The SDK sets the span `operation` to `file.copy`, `file.write`, `file.delete`, `file.open`, `file.read` or `file.rename`, and `description` to `filename` (for example, `file.txt`).

In addition, the span contains other useful information such as `file.size` (raw number of bytes), `file.path` (an absolute path to the file), and `file.async` (`true` if the called method returns a `Future`, or `false` if it's a `Sync` call) as part of the `data` payload.

The span finishes once the operation has been executed. The span `status` is set to `SpanStatus.ok` if successful or `SpanStatus.internalError` if there was any error.

When the operation throws an `Exception`, Sentry's SDK associates this exception to the running span. If you haven't set the SDK to swallow the exception and capture it, the span and SentryEvent will be linked when viewing it on the **Issue Details** page in [sentry.io](https://sentry.io).
When the operation throws an `Exception`, Sentry's SDK associates this exception to the running span. If you haven't set the SDK to swallow the exception and capture it, the span and `SentryEvent` will be linked when viewing it on the **Issue Details** page in [sentry.io](https://sentry.io).

For more information see our [file I/O integration](/platforms/dart/configuration/integrations/file/).
6 changes: 1 addition & 5 deletions src/platforms/dart/configuration/integrations/file.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,7 @@ sidebar_order: 5
description: "Learn more about the Sentry file I/O integration for the Dart SDK."
---

<Note>

This feature is currently in Beta. Beta features are still in-progress and may have bugs. We recognize the irony.

</Note>
<Include name="beta-note.mdx" />

The `sentry_file` library provides [File](https://api.dart.dev/stable/2.18.5/dart-io/File-class.html) support for Sentry wrapping the `File` class with a `SentryFile` wrapper. It is able to run performance monitoring for `File` operations.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -10,11 +10,7 @@ categories:

_(New in version 6.17.0)_

<Note>

This feature is currently in Beta. Beta features are still in-progress and may have bugs. We recognize the irony.

</Note>
<Include name="beta-note.mdx" />

The UI instrumentation, once enabled, captures transactions and adds breadcrumbs for a set of different user interactions, which include clicks, long clicks, taps, and so on. The SDK composes the transaction name from the `key` of the `Widget` that captured the user interaction (for example, `login_button`). The transaction operation is set to `ui.action.click`.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -216,12 +216,12 @@ The `enableStructuredDataTracing` feature is available in Beta. Beta features ar

### File I/O Instrumentation

The Sentry-specific file I/O implementation starts a span out of the active span, bound to the scope for each file I/O operation. The SDK sets the span `operation` to `file.copy`/`file.write`/`file.delete`/`file.open`/`file.read`/`file.rename` and `description` to `filename` (for example, `file.txt`).
The Sentry-specific file I/O implementation starts a span out of the active span, bound to the scope for each file I/O operation. The SDK sets the span `operation` to `file.copy`, `file.write`, `file.delete`, `file.open`, `file.read` or `file.rename`, and `description` to `filename` (for example, `file.txt`).

In addition, the span contains other useful information such as `file.size` (raw number of bytes), `file.path` (an absolute path to the file) and `file.async` (`true` if the called method returns a `Future`, or `false` if it's a `Sync` call) as part of the `data` payload.

The span finishes once the operation has been executed. The span `status` is set to `SpanStatus.ok` if successful or `SpanStatus.internalError` if there was any error.

When the operation throws an `Exception`, Sentry's SDK associates this exception to the running span. If you haven't set the SDK to swallow the exception and capture it, the span and SentryEvent will be linked when viewing it on the **Issue Details** page in [sentry.io](https://sentry.io).
When the operation throws an `Exception`, Sentry's SDK associates this exception to the running span. If you haven't set the SDK to swallow the exception and capture it, the span and `SentryEvent` will be linked when viewing it on the **Issue Details** page in [sentry.io](https://sentry.io).

Learn more about our [file I/O integration](/platforms/dart/configuration/integrations/file/).