Whether the RevDeBug server uses a secure connection
Connection timeout in seconds
Maximum wait before reconnect attempt (reached with exponential backoff)
Authentication token for server access
Name of the application that will be displayed in the RevDeBug server
If this is not present then Application is set to script name
Should be set to a git hash of current release commit
Human readable version string, e.g. "1.0", etc...)
Logging level: info, warn, error, off)
Maximum number of concurrent pending recordings sending to allow
Whether async task code isolation blocks are enabled or no, will allow giving async tasks contexts their own record buffers so their crash recordings will not include non-task code, default enabled
Can be "Continuous", "OnEvent" or "Off" (case insensitive) (if mode is off then can not be enabled from remote server and just acts like normal Python).
0 .. 2, 0 = fastest least detail, 1 = fast know type stringifiers and repr for others, 2 = same as 1 but known mutable objects are shown with repr if Mutable flag not set (dangerous because value may not be correct)
0 or 1, if set then tuples, lists, dicts, sets and bytearrays will be stringified immediately on record to be able to display the correct value at point of record
maximum depth to recurse into objects for stringification, range [-1, 16]
0 or 1, whether APM is enabled or not
port of APM OAP server, 0 means default port for protocol - grpc: 11800, http: 80 or 443
http status codes to be excluded from auto exception recordings for servers (span will still be recorded)
http status codes to be excluded from auto exception recordings for clients (span will still be recorded)
Application name as will be displayed in APM RevDeBug. Empty inherits from solution
The name patterns in CSV pattern, plugins whose name matches one of the pattern won't be installed
If the operation name of the first span is included in this set, this segment should be ignored.
You can setup multiple URL path patterns, The endpoints match these patterns wouldn't be traced. the current matching rules follow Ant Path match style , like /path/*, /path/**, /path/?.
The maximum queue backlog size for sending the segment data to backend, segments beyond this are silently dropped
Comma-delimited list of http methods to ignore (GET, POST, HEAD, OPTIONS, etc...)
':' delimited list of absolute or relative (to .cfg) paths or files to enable or disable recording (using '+' or '-' prefix, no prefix is same as '+').