Merge pull request #10099 from emirmx/document-call-depth-loop-count-limit-options

Document new call depth and loop iteration limiting options for tracing

Author: MarkvanMents

content/en/docs/refguide/runtime/tracing-in-runtime.md

@@ -52,6 +52,8 @@ The Java Agent can be configured through system properties, which can be added t
 | `otel.exporter.otlp.traces.certificate` | The path to the file containing trusted certificates to use when verifying a trace server's TLS credentials. The file should contain one or more X.509 certificates in PEM format. | By default the host platform's trusted root certificates are used. |
 | `otel.exporter.otlp.traces.client.key` | The path to the file containing the private client key to use when verifying a trace client's TLS credentials. The file should contain one private key in PKCS8 PEM format. | By default no client key file is used. |
 | `otel.exporter.otlp.traces.client.certificate` | The path to the file containing trusted certificates to use when verifying a trace client's TLS credentials. The file should contain one or more X.509 certificates in PEM format. | By default no certificate file is used. |
+| `mendix.tracing.max.microflow.depth` | Specifies the maximum nesting level of microflow calls for which the system will generate tracing spans. *Introduced in Mendix 11.2.0*. | 10 |
+| `mendix.tracing.max.loop.iteration` | Defines the maximum number of loop iterations for which individual tracing spans will be generated within a single microflow loop. *Introduced in Mendix 11.2.0*. | 10 |
 
 ## Enabling Tracing for Deployed Applications
 
@@ -93,4 +95,4 @@ docker run MyMendixApp \
 
 {{% alert color="info" %}}
 Replace `MyServiceName` with a meaningful identifier for your service and `collector-host` and `port` with the host and port of your OpenTelemetry collector.
-{{% /alert %}}
+{{% /alert %}}