Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
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
6 changes: 3 additions & 3 deletions src/platforms/android/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -413,7 +413,7 @@ Most SDKs generally support configuring tags by configuring the scope:
Sentry.setTag("tagKey", "tagValue");
```

For more information, see [Tagging Events](enriching-events/context/#tags) in Context.
For more information, see [Tagging Events](/platforms/android/enriching-events/tags/).

### Setting the Level

Expand All @@ -430,7 +430,7 @@ Sentry uses a fingerprint to decide how to group errors into issues.

For some very advanced use cases, you can override the Sentry default grouping using the `fingerprint` attribute. In supported SDKs, this attribute can be passed with the event information and should be a list of strings.

For code samples, see [Grouping & Fingerprints](data-management/event-grouping/#use-cases).
For more details, see [Issue Grouping](/platforms/android/data-management/event-grouping/).

For more information, see [Aggregate Errors with Custom Fingerprints](https://blog.sentry.io/2018/01/18/setting-up-custom-fingerprints).

Expand Down Expand Up @@ -775,7 +775,7 @@ Java_io_sentry_demo_NativeDemo_crash(JNIEnv *env, jclass cls) {
}
```

To symbolicate the stack trace from native code, we need to have access to the debug symbols of your application. Please check the full documentation on [uploading files](/workflow/debug-files/#uploading-files) to learn more about the upload of the debug symbols.
To symbolicate the stack trace from native code, we need to have access to the debug symbols of your application. Please check the full documentation on [Uploading Files](/platforms/android/data-management/debug-files/#uploading-files) to learn more about the upload of the debug symbols.

Example of uploading all your .so files:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Depending on the information available, the following data can be used for each

This grouping usually works well, but two specific situations can throw it off if not dealt with:

- Minimized JavaScript sourcecode will destroy the grouping in really bad ways. Because of this you should ensure that Sentry can access your [Source Maps](/platforms/javascript/#source-maps).
- Minimized JavaScript sourcecode will destroy the grouping in really bad ways. Because of this you should ensure that Sentry can access your [Source Maps](/platforms/javascript/sourcemaps/).
- If you modify your stack trace by introducing a new level through the use of decorators, your stack trace will change and so will the grouping. To handle this, many SDKs support hiding irrelevant stack trace frames. (For example, the Python SDK will skip all stack frames with a local variable called `__traceback_hide__` set to _True_).

### Grouping By Exception
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ Select known parts of the schema using the following:
- `$logentry`: Matches the `logentry` attribute of an event. Alias for `logentry`
- `$thread`: Matches a single thread instance. Alias for `threads.values.*`
- `$breadcrumb`: Matches a single breadcrumb. Alias for `breadcrumbs.values.*`
- `$span`: Matches a [trace span](/performance-monitoring/distributed-tracing/#traces-transactions-and-spans). Alias for `spans.*`
- `$span`: Matches a [trace span](/product/performance/distributed-tracing/#spans). Alias for `spans.*`
- `$sdk`: Matches the SDK context. Alias for `sdk`

### Escaping Special Characters
Expand Down