Skip to content
Open
Changes from 2 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
11 changes: 11 additions & 0 deletions content/en/docs/refguide/runtime/tracing-in-runtime.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,17 @@ Tracing can be enabled from the `App Settings` -> `Configuration` dialog. In the

{{< figure src="/attachments/refguide/runtime/tracing-in-runtime/tracing-configuration.png" >}}

### Filtering

For filtering out specific traces, `mendix.tracing.filter` system property can be used. The specified spans and their sub-spans will be filtered out. `matchType` specifies how the name of the span is matched. Currently only `partial` is supported for `matchType` which checks if the span name contains the provided value.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this introduced in 11.5, or did we just forget to document it before?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes introduced in 11.5, we also backported to 10.24.12

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will you make a PR for 10.24.12 to update the documentation there as well?
(Once we have fixed the text on this PR!)

```json
[
{
"type": "drop", "matchType": "partial", "spanName": "Loop"
}
]
```

### Testing

To test the tracing you can use [Jaeger](https://www.jaegertracing.io/). For example, the all-in-one binary or Docker image. Jaeger will listen to the above endpoint by default.
Expand Down