lhg ddlZddlmZddlmZdZdZdZGddeZGd d eZ erddl Z dd lm Z dd lm Z dd lm Z ddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZmZmZmZmZmZmZmZm Z m!Z!m"Z"m#Z#edide e$de e$de e%de e%de ede e%de e$de e$d e e d!e e$d"e e%d#e e%d$e e e&e#ee"ge%fd%e e%d&e e%d'e e eege efd(Z'dZ(dZ)d)Z*gd*Z+Gd+d,e&eZ,Gd-d.Z-Gd/d0Z.Gd1d2Z/Gd3d4Z0Gd5d6Z1d7Z2e2Z3[2d8Z4y)9N)Enum) TYPE_CHECKINGidFceZdZdZdZy) EndpointTypez The type of an endpoint. This is an enum, rather than a constant, for historical reasons (the old /store endpoint). The enum also preserve future compatibility, in case we ever have a new endpoint. envelopeN)__name__ __module__ __qualname____doc__ENVELOPEc/var/www/pru.catia.catastroantioquia-mas.com/tasa/lib/python3.12/site-packages/sentry_sdk/consts.pyrrs HrrceZdZdZdZy)CompressionAlgogzipbrN)r r r GZIPBROTLIrrrrrs D Frr)Optional)Callable)Union)List)Type)Dict)Any)Sequence)Tuple)Literal) TypedDict) BreadcrumbProcessorContinuousProfilerModeEventEventProcessorHintLogMeasurementUnit ProfilerMode TracesSamplerTransactionProcessor MetricTags MetricValue Experiments max_spans max_flagsrecord_sql_paramscontinuous_profiling_auto_startcontinuous_profiling_modeotel_powered_performance transport_zlib_compression_leveltransport_compression_leveltransport_compression_algotransport_num_poolstransport_http2enable_metricsbefore_emit_metricmetric_code_locations enable_logsbefore_send_log)totalz.*)falsenooffn0c"eZdZdZdZdZdZdZy) SPANTEMPLATEdefaultai_agentai_toolai_chatc|jSN)value)selfs r__str__zSPANTEMPLATE.__str__ms zzrN)r r r DEFAULTAI_AGENTAI_TOOLAI_CHATrOrrrrFrFgsGHGGrrFceZdZdZdZy) INSTRUMENTERsentryotelN)r r r SENTRYOTELrrrrUrUrs F DrrUc0eZdZdZdZ dZ dZ dZ dZ dZ dZ d Z d Z d Z d Z d Z dZ dZ dZ dZ dZ dZ dZ dZ dZ dZ dZ dZ dZ dZ dZ dZ dZ dZ! d Z" d!Z# d"Z$ d#Z% d$Z& d%Z' d&Z( d'Z) d(Z* d)Z+ d*Z, d+Z- d,Z. d-Z/ d.Z0 d/Z1 d0Z2 d1Z3 d2Z4 d3Z5 d4Z6 d5Z7 d6Z8 d7Z9 d8Z: d9Z; d:Z< d;Z= d d=Z? d>Z@ d?ZA d@ZB dAZC dBZD dCZE dDZF dEZG dFZH dGZI dHZJ dIZK dJZL dKZM dLZN dMZO dNZP dOZQ dPZR dQZS dRZT dSZU dTZV dUZW dVZX dWZY dXZZ dYZ[ dZZ\ d[Z] d\Z^y])^SPANDATAz Additional information describing the type of the span. See: https://develop.sentry.dev/sdk/performance/span-data-conventions/ z ai.citationsz ai.documentszai.finish_reasonzai.frequency_penaltyzai.function_callzai.generation_idzai.input_messagesz ai.logit_biasz ai.metadataz ai.model_idzai.pipeline.namez ai.preamblezai.presence_penaltyzai.raw_promptingzai.response_formatz ai.responseszai.search_querieszai.is_search_requiredzai.search_resultszai.seedz ai.streamingzai.tagszai.temperaturezai.textszai.top_kzai.top_pz ai.tool_callszai.toolsz ai.warningsz cache.hitzcache.item_sizez cache.keyz code.filepathz code.functionz code.linenozcode.namespacezdb.mongodb.collectionzdb.namez db.operationz db.systemzdb.userzgen_ai.agent.namez gen_ai.choicezgen_ai.operation.namezgen_ai.pipeline.namezgen_ai.response.finish_reasonszgen_ai.response.idzgen_ai.response.modelzgen_ai.response.streamingzgen_ai.response.textzgen_ai.response.tool_callszgen_ai.request.available_toolsz gen_ai.request.frequency_penaltyzgen_ai.request.max_tokenszgen_ai.request.messageszgen_ai.request.modelzgen_ai.request.presence_penaltyzgen_ai.request.seedzgen_ai.request.temperaturezgen_ai.request.top_kzgen_ai.request.top_pz gen_ai.systemzgen_ai.tool.descriptionzgen_ai.tool.inputzgen_ai.tool.namezgen_ai.tool.outputzgen_ai.tool.typezgen_ai.usage.input_tokensz gen_ai.usage.input_tokens.cachedzgen_ai.usage.output_tokensz$gen_ai.usage.output_tokens.reasoningzgen_ai.usage.total_tokenszgen_ai.user.messagez http.fragmentz http.methodz http.queryzhttp.response.status_codezmessaging.destination.namezmessaging.message.idz!messaging.message.receive.latencyzmessaging.message.retry.countzmessaging.systemznetwork.peer.addressznetwork.peer.port profiler_idzserver.addressz server.portzserver.socket.addresszserver.socket.portz thread.idz thread.nameN)_r r r r AI_CITATIONS AI_DOCUMENTSAI_FINISH_REASONAI_FREQUENCY_PENALTYAI_FUNCTION_CALLAI_GENERATION_IDAI_INPUT_MESSAGES AI_LOGIT_BIAS AI_METADATA AI_MODEL_IDAI_PIPELINE_NAME AI_PREAMBLEAI_PRESENCE_PENALTYAI_RAW_PROMPTINGAI_RESPONSE_FORMAT AI_RESPONSESAI_SEARCH_QUERIESAI_SEARCH_REQUIREDAI_SEARCH_RESULTSAI_SEED AI_STREAMINGAI_TAGSAI_TEMPERATUREAI_TEXTSAI_TOP_KAI_TOP_P AI_TOOL_CALLSAI_TOOLS AI_WARNINGS CACHE_HITCACHE_ITEM_SIZE CACHE_KEY CODE_FILEPATH CODE_FUNCTION CODE_LINENOCODE_NAMESPACEDB_MONGODB_COLLECTIONDB_NAME DB_OPERATION DB_SYSTEMDB_USERGEN_AI_AGENT_NAME GEN_AI_CHOICEGEN_AI_OPERATION_NAMEGEN_AI_PIPELINE_NAMEGEN_AI_RESPONSE_FINISH_REASONSGEN_AI_RESPONSE_IDGEN_AI_RESPONSE_MODELGEN_AI_RESPONSE_STREAMINGGEN_AI_RESPONSE_TEXTGEN_AI_RESPONSE_TOOL_CALLSGEN_AI_REQUEST_AVAILABLE_TOOLS GEN_AI_REQUEST_FREQUENCY_PENALTYGEN_AI_REQUEST_MAX_TOKENSGEN_AI_REQUEST_MESSAGESGEN_AI_REQUEST_MODELGEN_AI_REQUEST_PRESENCE_PENALTYGEN_AI_REQUEST_SEEDGEN_AI_REQUEST_TEMPERATUREGEN_AI_REQUEST_TOP_KGEN_AI_REQUEST_TOP_P GEN_AI_SYSTEMGEN_AI_TOOL_DESCRIPTIONGEN_AI_TOOL_INPUTGEN_AI_TOOL_NAMEGEN_AI_TOOL_OUTPUTGEN_AI_TOOL_TYPEGEN_AI_USAGE_INPUT_TOKENS GEN_AI_USAGE_INPUT_TOKENS_CACHEDGEN_AI_USAGE_OUTPUT_TOKENS$GEN_AI_USAGE_OUTPUT_TOKENS_REASONINGGEN_AI_USAGE_TOTAL_TOKENSGEN_AI_USER_MESSAGE HTTP_FRAGMENT HTTP_METHOD HTTP_QUERYHTTP_STATUS_CODEMESSAGING_DESTINATION_NAMEMESSAGING_MESSAGE_ID!MESSAGING_MESSAGE_RECEIVE_LATENCYMESSAGING_MESSAGE_RETRY_COUNTMESSAGING_SYSTEMNETWORK_PEER_ADDRESSNETWORK_PEER_PORT PROFILER_IDSERVER_ADDRESS SERVER_PORTSERVER_SOCKET_ADDRESSSERVER_SOCKET_PORT THREAD_ID THREAD_NAMErrrr[r[ws "L"L*2**,$M K K* K0*."L,1,G"LG&NHHH$MH KI (O I $M $M  K &N 4 G "L I G , $M 4 2 &F" . 4 !< 2 "> &F" (J$ !< 8 2 'H# 0 "> 2 2 $M 8 , * . * !< (J$ "> ,R( !< 0 $M  K J 3 "> 2)L%%D!*2 ,  K &N  K 4 . I  Krr[cTeZdZdZdZdZdZdZdZdZ dZ d Z d Z d Z d Zd ZdZdZdZdZdZy) SPANSTATUSzv The status of a Sentry span. See: https://develop.sentry.dev/sdk/event-payloads/contexts/#trace-context abortedalready_exists cancelled data_lossdeadline_exceededfailed_preconditioninternal_errorinvalid_argument not_foundok out_of_rangepermission_deniedresource_exhaustedunauthenticated unavailable unimplemented unknown_errorN)r r r r ABORTEDALREADY_EXISTS CANCELLED DATA_LOSSDEADLINE_EXCEEDEDFAILED_PRECONDITIONINTERNAL_ERRORINVALID_ARGUMENT NOT_FOUNDOK OUT_OF_RANGEPERMISSION_DENIEDRESOURCE_EXHAUSTEDUNAUTHENTICATED UNAVAILABLE UNIMPLEMENTED UNKNOWN_ERRORrrrrrsc G%NII+/%N)I B!L+-'OK#M#MrrceZdZdZdZdZdZdZdZdZ dZ d Z d Z d Z d Zd ZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZ dZ!d Z"d!Z#d"Z$d#Z%d$Z&d%Z'd&Z(d'Z)d(Z*d)Z+d*Z,d+Z-d,Z.d-Z/d.Z0d/Z1d0Z2d1Z3d2Z4d3Z5d4Z6d5Z7d6Z8d7Z9d8Z:d9Z;d:Zd=Z?y>)?OPzai.messages.create.anthropicz cache.getz cache.putz!ai.chat_completions.create.coherezai.embeddings.create.coheredbzdb.redisz event.djangofunctionz function.awsz function.gcpz gen_ai.chatzgen_ai.embeddingszgen_ai.execute_toolzgen_ai.handoffzgen_ai.pipelinezgen_ai.invoke_agentzgen_ai.responseszgraphql.executezgraphql.mutationz graphql.parsezgraphql.resolvezgraphql.subscriptionz graphql.queryzgraphql.validatez grpc.clientz grpc.serverz http.clientzhttp.client.streamz http.serverzmiddleware.djangozmiddleware.litestarzmiddleware.litestar.receivezmiddleware.litestar.sendzmiddleware.starlettezmiddleware.starlette.receivezmiddleware.starlette.sendzmiddleware.starlitezmiddleware.starlite.receivezmiddleware.starlite.sendz*ai.chat_completions.create.huggingface_hubz queue.processz queue.publishzqueue.submit.arqzqueue.task.arqzqueue.submit.celeryzqueue.task.celeryz queue.task.rqzqueue.submit.hueyzqueue.task.hueyzqueue.submit.rayzqueue.task.ray subprocesszsubprocess.waitzsubprocess.communicateztemplate.renderz view.renderzview.response.renderzwebsocket.serverzsocket.connectionz socket.dnsN)@r r r ANTHROPIC_MESSAGES_CREATE CACHE_GET CACHE_PUTCOHERE_CHAT_COMPLETIONS_CREATECOHERE_EMBEDDINGS_CREATEDBDB_REDIS EVENT_DJANGOFUNCTION FUNCTION_AWS FUNCTION_GCP GEN_AI_CHATGEN_AI_EMBEDDINGSGEN_AI_EXECUTE_TOOLGEN_AI_HANDOFFGEN_AI_PIPELINEGEN_AI_INVOKE_AGENTGEN_AI_RESPONSESGRAPHQL_EXECUTEGRAPHQL_MUTATION GRAPHQL_PARSEGRAPHQL_RESOLVEGRAPHQL_SUBSCRIPTION GRAPHQL_QUERYGRAPHQL_VALIDATE GRPC_CLIENT GRPC_SERVER HTTP_CLIENTHTTP_CLIENT_STREAM HTTP_SERVERMIDDLEWARE_DJANGOMIDDLEWARE_LITESTARMIDDLEWARE_LITESTAR_RECEIVEMIDDLEWARE_LITESTAR_SENDMIDDLEWARE_STARLETTEMIDDLEWARE_STARLETTE_RECEIVEMIDDLEWARE_STARLETTE_SENDMIDDLEWARE_STARLITEMIDDLEWARE_STARLITE_RECEIVEMIDDLEWARE_STARLITE_SEND'HUGGINGFACE_HUB_CHAT_COMPLETIONS_CREATE QUEUE_PROCESS QUEUE_PUBLISHQUEUE_SUBMIT_ARQQUEUE_TASK_ARQQUEUE_SUBMIT_CELERYQUEUE_TASK_CELERY QUEUE_TASK_RQQUEUE_SUBMIT_HUEYQUEUE_TASK_HUEYQUEUE_SUBMIT_RAYQUEUE_TASK_RAY SUBPROCESSSUBPROCESS_WAITSUBPROCESS_COMMUNICATETEMPLATE_RENDER VIEW_RENDERVIEW_RESPONSE_RENDERWEBSOCKET_SERVERSOCKET_CONNECTION SOCKET_DNSrrrrrsV >II%H"< BH!LH!L!LK+/%N'O/)'O)#M'O1#M)KKK-K+/"?91#A ;/"?94,$M#M)%N/+#M+'O)%NJ'O5'OK1)+Jrrc?eZdZ d eddddgggdddeddddgddddddddddddddddddddidej dddddeggdedddddddde e ddd =d Z y) ClientConstructorNTg?mediumFmanualr)=max_breadcrumbsrelease environment server_nameshutdown_timeout integrationsin_app_includein_app_excludedefault_integrationsdist transporttransport_queue_size sample_ratesend_default_pii http_proxy https_proxy ignore_errorsmax_request_body_sizesocket_options keep_alive before_sendbefore_breadcrumbdebugattach_stacktraceca_certspropagate_tracestraces_sample_ratetraces_samplerprofiles_sample_rateprofiles_sampler profiler_modeprofile_lifecycleprofile_session_sample_rateauto_enabling_integrationsdisabled_integrationsauto_session_trackingsend_client_reports _experiments proxy_headers instrumenterbefore_send_transaction project_rootenable_tracinginclude_local_variablesinclude_source_contexttrace_propagation_targetsfunctions_to_traceevent_scrubbermax_value_lengthenable_backpressure_handling error_samplerenable_db_query_sourcedb_query_source_threshold_ms spotlight cert_filekey_file custom_repradd_full_stackmax_stack_framesr=r>c=y)aOInitialize the Sentry SDK with the given parameters. All parameters described here can be used in a call to `sentry_sdk.init()`. :param dsn: The DSN tells the SDK where to send the events. If this option is not set, the SDK will just not send any data. The `dsn` config option takes precedence over the environment variable. Learn more about `DSN utilization `_. :param debug: Turns debug mode on or off. When `True`, the SDK will attempt to print out debugging information. This can be useful if something goes wrong with event sending. The default is always `False`. It's generally not recommended to turn it on in production because of the increase in log output. The `debug` config option takes precedence over the environment variable. :param release: Sets the release. If not set, the SDK will try to automatically configure a release out of the box but it's a better idea to manually set it to guarantee that the release is in sync with your deploy integrations. Release names are strings, but some formats are detected by Sentry and might be rendered differently. See `the releases documentation `_ to learn how the SDK tries to automatically configure a release. The `release` config option takes precedence over the environment variable. Learn more about how to send release data so Sentry can tell you about regressions between releases and identify the potential source in `the product documentation `_. :param environment: Sets the environment. This string is freeform and set to `production` by default. A release can be associated with more than one environment to separate them in the UI (think `staging` vs `production` or similar). The `environment` config option takes precedence over the environment variable. :param dist: The distribution of the application. Distributions are used to disambiguate build or deployment variants of the same release of an application. The dist can be for example a build number. :param sample_rate: Configures the sample rate for error events, in the range of `0.0` to `1.0`. The default is `1.0`, which means that 100% of error events will be sent. If set to `0.1`, only 10% of error events will be sent. Events are picked randomly. :param error_sampler: Dynamically configures the sample rate for error events on a per-event basis. This configuration option accepts a function, which takes two parameters (the `event` and the `hint`), and which returns a boolean (indicating whether the event should be sent to Sentry) or a floating-point number between `0.0` and `1.0`, inclusive. The number indicates the probability the event is sent to Sentry; the SDK will randomly decide whether to send the event with the given probability. If this configuration option is specified, the `sample_rate` option is ignored. :param ignore_errors: A list of exception class names that shouldn't be sent to Sentry. Errors that are an instance of these exceptions or a subclass of them, will be filtered out before they're sent to Sentry. By default, all errors are sent. :param max_breadcrumbs: This variable controls the total amount of breadcrumbs that should be captured. This defaults to `100`, but you can set this to any number. However, you should be aware that Sentry has a `maximum payload size `_ and any events exceeding that payload size will be dropped. :param attach_stacktrace: When enabled, stack traces are automatically attached to all messages logged. Stack traces are always attached to exceptions; however, when this option is set, stack traces are also sent with messages. This option means that stack traces appear next to all log messages. Grouping in Sentry is different for events with stack traces and without. As a result, you will get new groups as you enable or disable this flag for certain events. :param send_default_pii: If this flag is enabled, `certain personally identifiable information (PII) `_ is added by active integrations. If you enable this option, be sure to manually remove what you don't want to send using our features for managing `Sensitive Data `_. :param event_scrubber: Scrubs the event payload for sensitive information such as cookies, sessions, and passwords from a `denylist`. It can additionally be used to scrub from another `pii_denylist` if `send_default_pii` is disabled. See how to `configure the scrubber here `_. :param include_source_context: When enabled, source context will be included in events sent to Sentry. This source context includes the five lines of code above and below the line of code where an error happened. :param include_local_variables: When enabled, the SDK will capture a snapshot of local variables to send with the event to help with debugging. :param add_full_stack: When capturing errors, Sentry stack traces typically only include frames that start the moment an error occurs. But if the `add_full_stack` option is enabled (set to `True`), all frames from the start of execution will be included in the stack trace sent to Sentry. :param max_stack_frames: This option limits the number of stack frames that will be captured when `add_full_stack` is enabled. :param server_name: This option can be used to supply a server name. When provided, the name of the server is sent along and persisted in the event. For many integrations, the server name actually corresponds to the device hostname, even in situations where the machine is not actually a server. :param project_root: The full path to the root directory of your application. The `project_root` is used to mark frames in a stack trace either as being in your application or outside of the application. :param in_app_include: A list of string prefixes of module names that belong to the app. This option takes precedence over `in_app_exclude`. Sentry differentiates stack frames that are directly related to your application ("in application") from stack frames that come from other packages such as the standard library, frameworks, or other dependencies. The application package is automatically marked as `inApp`. The difference is visible in [sentry.io](https://sentry.io), where only the "in application" frames are displayed by default. :param in_app_exclude: A list of string prefixes of module names that do not belong to the app, but rather to third-party packages. Modules considered not part of the app will be hidden from stack traces by default. This option can be overridden using `in_app_include`. :param max_request_body_size: This parameter controls whether integrations should capture HTTP request bodies. It can be set to one of the following values: - `never`: Request bodies are never sent. - `small`: Only small request bodies will be captured. The cutoff for small depends on the SDK (typically 4KB). - `medium`: Medium and small requests will be captured (typically 10KB). - `always`: The SDK will always capture the request body as long as Sentry can make sense of it. Please note that the Sentry server [limits HTTP request body size](https://develop.sentry.dev/sdk/ expected-features/data-handling/#variable-size). The server always enforces its size limit, regardless of how you configure this option. :param max_value_length: The number of characters after which the values containing text in the event payload will be truncated. WARNING: If the value you set for this is exceptionally large, the event may exceed 1 MiB and will be dropped by Sentry. :param ca_certs: A path to an alternative CA bundle file in PEM-format. :param send_client_reports: Set this boolean to `False` to disable sending of client reports. Client reports allow the client to send status reports about itself to Sentry, such as information about events that were dropped before being sent. :param integrations: List of integrations to enable in addition to `auto-enabling integrations (overview) `_. This setting can be used to override the default config options for a specific auto-enabling integration or to add an integration that is not auto-enabled. :param disabled_integrations: List of integrations that will be disabled. This setting can be used to explicitly turn off specific `auto-enabling integrations (list) `_ or `default `_ integrations. :param auto_enabling_integrations: Configures whether `auto-enabling integrations (configuration) `_ should be enabled. When set to `False`, no auto-enabling integrations will be enabled by default, even if the corresponding framework/library is detected. :param default_integrations: Configures whether `default integrations `_ should be enabled. Setting `default_integrations` to `False` disables all default integrations **as well as all auto-enabling integrations**, unless they are specifically added in the `integrations` option, described above. :param before_send: This function is called with an SDK-specific message or error event object, and can return a modified event object, or `null` to skip reporting the event. This can be used, for instance, for manual PII stripping before sending. By the time `before_send` is executed, all scope data has already been applied to the event. Further modification of the scope won't have any effect. :param before_send_transaction: This function is called with an SDK-specific transaction event object, and can return a modified transaction event object, or `null` to skip reporting the event. One way this might be used is for manual PII stripping before sending. :param before_breadcrumb: This function is called with an SDK-specific breadcrumb object before the breadcrumb is added to the scope. When nothing is returned from the function, the breadcrumb is dropped. To pass the breadcrumb through, return the first argument, which contains the breadcrumb object. The callback typically gets a second argument (called a "hint") which contains the original object from which the breadcrumb was created to further customize what the breadcrumb should look like. :param transport: Switches out the transport used to send events. How this works depends on the SDK. It can, for instance, be used to capture events for unit-testing or to send it through some more complex setup that requires proxy authentication. :param transport_queue_size: The maximum number of events that will be queued before the transport is forced to flush. :param http_proxy: When set, a proxy can be configured that should be used for outbound requests. This is also used for HTTPS requests unless a separate `https_proxy` is configured. However, not all SDKs support a separate HTTPS proxy. SDKs will attempt to default to the system-wide configured proxy, if possible. For instance, on Unix systems, the `http_proxy` environment variable will be picked up. :param https_proxy: Configures a separate proxy for outgoing HTTPS requests. This value might not be supported by all SDKs. When not supported the `http-proxy` value is also used for HTTPS requests at all times. :param proxy_headers: A dict containing additional proxy headers (usually for authentication) to be forwarded to `urllib3`'s `ProxyManager `_. :param shutdown_timeout: Controls how many seconds to wait before shutting down. Sentry SDKs send events from a background queue. This queue is given a certain amount to drain pending events. The default is SDK specific but typically around two seconds. Setting this value too low may cause problems for sending events from command line applications. Setting the value too high will cause the application to block for a long time for users experiencing network connectivity problems. :param keep_alive: Determines whether to keep the connection alive between requests. This can be useful in environments where you encounter frequent network issues such as connection resets. :param cert_file: Path to the client certificate to use. If set, supersedes the `CLIENT_CERT_FILE` environment variable. :param key_file: Path to the key file to use. If set, supersedes the `CLIENT_KEY_FILE` environment variable. :param socket_options: An optional list of socket options to use. These provide fine-grained, low-level control over the way the SDK connects to Sentry. If provided, the options will override the default `urllib3` `socket options `_. :param traces_sample_rate: A number between `0` and `1`, controlling the percentage chance a given transaction will be sent to Sentry. (`0` represents 0% while `1` represents 100%.) Applies equally to all transactions created in the app. Either this or `traces_sampler` must be defined to enable tracing. If `traces_sample_rate` is `0`, this means that no new traces will be created. However, if you have another service (for example a JS frontend) that makes requests to your service that include trace information, those traces will be continued and thus transactions will be sent to Sentry. If you want to disable all tracing you need to set `traces_sample_rate=None`. In this case, no new traces will be started and no incoming traces will be continued. :param traces_sampler: A function responsible for determining the percentage chance a given transaction will be sent to Sentry. It will automatically be passed information about the transaction and the context in which it's being created, and must return a number between `0` (0% chance of being sent) and `1` (100% chance of being sent). Can also be used for filtering transactions, by returning `0` for those that are unwanted. Either this or `traces_sample_rate` must be defined to enable tracing. :param trace_propagation_targets: An optional property that controls which downstream services receive tracing data, in the form of a `sentry-trace` and a `baggage` header attached to any outgoing HTTP requests. The option may contain a list of strings or regex against which the URLs of outgoing requests are matched. If one of the entries in the list matches the URL of an outgoing request, trace data will be attached to that request. String entries do not have to be full matches, meaning the URL of a request is matched when it _contains_ a string provided through the option. If `trace_propagation_targets` is not provided, trace data is attached to every outgoing request from the instrumented client. :param functions_to_trace: An optional list of functions that should be set up for tracing. For each function in the list, a span will be created when the function is executed. Functions in the list are represented as strings containing the fully qualified name of the function. This is a convenient option, making it possible to have one central place for configuring what functions to trace, instead of having custom instrumentation scattered all over your code base. To learn more, see the `Custom Instrumentation `_ documentation. :param enable_backpressure_handling: When enabled, a new monitor thread will be spawned to perform health checks on the SDK. If the system is unhealthy, the SDK will keep halving the `traces_sample_rate` set by you in 10 second intervals until recovery. This down sampling helps ensure that the system stays stable and reduces SDK overhead under high load. This option is enabled by default. :param enable_db_query_source: When enabled, the source location will be added to database queries. :param db_query_source_threshold_ms: The threshold in milliseconds for adding the source location to database queries. The query location will be added to the query for queries slower than the specified threshold. :param custom_repr: A custom `repr `_ function to run while serializing an object. Use this to control how your custom objects and classes are visible in Sentry. Return a string for that repr value to be used or `None` to continue serializing how Sentry would have done it anyway. :param profiles_sample_rate: A number between `0` and `1`, controlling the percentage chance a given sampled transaction will be profiled. (`0` represents 0% while `1` represents 100%.) Applies equally to all transactions created in the app. This is relative to the tracing sample rate - e.g. `0.5` means 50% of sampled transactions will be profiled. :param profiles_sampler: :param profiler_mode: :param profile_lifecycle: :param profile_session_sample_rate: :param enable_tracing: :param propagate_traces: :param auto_session_tracking: :param spotlight: :param instrumenter: :param enable_logs: Set `enable_logs` to True to enable the SDK to emit Sentry logs. Defaults to False. :param before_send_log: An optional function to modify or filter out logs before they're sent to Sentry. Any modifications to the log in this function will be retained. If the function returns None, the log will not be sent to Sentry. :param _experiments: Nr)?rNdsnr#r$r%r&r'r(r)r*r+r,r-r.r/r0r1r2r3r4r5r6r7r8r9r:r;r<r=r>r?r@rArBrCrDrErFrGrHrIrJrKrLrMrNrOrPrQrRrSrTrUrVrWrXrYrZr[r\r]r=r>s? r__init__zClientConstructor.__init__TsR rrL) r r r DEFAULT_MAX_BREADCRUMBSDEFAULT_QUEUE_SIZErUrX MATCH_ALLDEFAULT_MAX_VALUE_LENGTHDEFAULT_ADD_FULL_STACKDEFAULT_MAX_STACK_FRAMESr`rrrrrRs I 0! /&!"$(#'"" !(( $ $# # 1%)#%(-1EI rrc $ddl}|jtj}|jxsd}|j xsi}t tjt|jt| d||jS)Nrr) inspectgetfullargspecrr`defaultskwonlydefaultsdict itertoolschainzipargslenitems)rharjrks r_get_default_optionsrt s{099:AzzRH%%+N  H ~'(( 3  "  rz2.35.2)5rmenumrtypingrrdrfrerr sentry_sdkrrrrrrrrrtyping_extensionsr r!sentry_sdk._typesr"r#r$r%r&r'r(r)r*r+r,r-intboolstrr.rbrarc FALSE_VALUESrFrUr[rrrrtDEFAULT_OPTIONSVERSIONrrrrs3 #4d )+    & # #  $  .x~  (2H)I  '   /   *8C=  )(?*C  "8C=  x~  htn  !(#{OZH$NO# $Xd^! " 8D># $ x#thsm1K(LM% (-K2   3 z z z$$4??HK K \  '( r