If these properties are manually configured, use only
falsefor boolean values.
The behaviour of the Scope Agent can be modified using environment variables or a configuration file
scope.yml in the source root of the project.
These configuration settings can also be provided via CLI flags. Check out the CLI reference documentation for details.
Disabling Scope instrumentation
Scope auto instruments your code and tests by default. You can disable this behaviour.
Changing service name
You can specify the name of the service when sending data to Scope. Scope uses
default as fallback.
Setting Scope as Global Tracer
If you set Scope as OpenTracing Global Tracer, your own spans will be captured and shown as part of the Scope trace view for a certain test.
Change testing mode
This variable indicates whether the agent is running tests (
true) or it is being used for runtime instrumentation (
SCOPE_TESTING_MODE is not specified, the agent sets to
Adding agent metadata
You can send arbitrary metadata for every test associated with certain commit which will be shown in Scope.
Additionally, it is possible to set an environment variable as metadata value for a certain key, whose final value will be evaluated at runtime.
Include DB statements values in DB span tags
You can include DB statement values in the related DB spans.
By default, Scope Python Agent will not send DB statement values as they are considered sensitive information.
Include HTTP payloads in HTTP span tags
You can include HTTP payloads in the related HTTP spans, truncated to the first 512 bytes.
By default, Scope Python Agent will not send HTTP payloads as they are considered sensitive information.
Include additional HTTP Headers in HTTP span tags
You can include additional HTTP Headers in HTTP span tags.
By default, Scope Python agent will send common HTTP headers, filtering the content of those which can contain sensitive information:
Note that the content of every header configured explicitly to be shown in the HTTP span tags will not be redacted.