o i"@sddlZddlZddlmZddlmZddlmZddlm Z ddlm Z ddl m Z ddl mZdd lmZddlmZdd lmZdd lmZdd lmZe eZGd dde jZeZdS)N)Iterable)Optional)config)agent)periodic) get_logger) RCCallback)RemoteConfigClient)REMOTE_CONFIG_AGENT_ENDPOINT) ServiceStatus) StopWatchc s"eZdZdZdZd,fdd Zd,ddZd,d d Zd,d d Zde fd dZ d,ddZ d-de ddfddZ d-de ddfddZ d,fdd Zdedede fddZgfdededeejddfddZdeddfd d!Zdeddfd"d#Zd$d%Zdedeefd&d'Zd.d(d)Zd,d*d+ZZS)/RemoteConfigPollerzRemote configuration worker. This implements a finite-state machine that allows checking the agent for the expected endpoint, which could be enabled after the client is started. TreturnNcs>tt|jtjdddt|_|j|_t |_ t |_ dS)NTF)intervalno_wait_at_start autorestart)superr __init__ddconfig_remote_config_poll_intervalr _client _agent_check_stateosgetpid _parent_iddict_capabilities_mapself __class__X/home/ubuntu/.local/lib/python3.10/site-packages/ddtrace/internal/remoteconfig/worker.pyrs   zRemoteConfigPoller.__init__cCsnzt}Wn tyd}Ynw|r0|dg}|r0t|vs&dt|vr0|j|_|dStddS)N endpoints/a2Agent is down or Remote Config is not enabled in the Agent Check your Agent version, you need an Agent running on 7.39.1 version or above. Check Your Remote Config environment variables on your Agent: DD_REMOTE_CONFIGURATION_ENABLED=true See: https://docs.datadoghq.com/agent/guide/how_remote_config_works/) rinfo Exceptiongetr _onlinerlogdebug)rr&r$r"r"r#r's   zRemoteConfigPoller._agent_checkcCsht}|js|j|_ WddSWdn1s wY|}td||jjdS)Nzrequest config in %.5fs to %s) r rrequestrrelapsedr*r+ agent_url)rswr-r"r"r#r)>s zRemoteConfigPoller._onlinecCs|SN)rrr"r"r#rHszRemoteConfigPoller.periodiccCs0tj}|r|jr|jtjkrdS|dSdS)NTF)r_remote_config_enabled_enablestatusr RUNNINGstart)rrc_env_enabledr"r"r#enableKs  zRemoteConfigPoller.enablecCsdd|_tdtt|j|jjr0|j tdttt |jj dSdS)z6Client Id needs to be refreshed when application forksFz7[%d][P: %d] Remote Config Poller fork. Refreshing statezC[%d][P: %d] Restarted global subscriber for registered products: %sN) r2r*r+rrgetppidrrenew_id_product_callbacksrestart_subscriberlistkeysrr"r"r# reset_at_forkWs  z RemoteConfigPoller.reset_at_forkFjoincCs&tdt|j|jj|ddS)z"Stop the global subscriber thread.z5[%s][P: %s] Remote Config Poller. Stopping subscriberr?N)r*r+rrrrstop_subscriberrr?r"r"r#rAgs z"RemoteConfigPoller.stop_subscribercCs6|j|d|j|jtjkrdS|j|ddS)Nr@)rArreset_productsr3r STOPPEDstoprBr"r"r#disableps   zRemoteConfigPoller.disablecs<||jtjks|jdurdStt|j|i|dSr0)rAr3r rD_workerrr _stop_service)rargskwargsr r"r#rHysz RemoteConfigPoller._stop_serviceproductcallbackcCs|j||S)a<Update the callback for a registered product. Some Products fork and restart their instances when application creates new process. In that case, we need to update the callback instance to ensure the instance of the child process receives correctly the Remote Configuration payloads. )rupdate_product_callback)rrKrLr"r"r#rMsz*RemoteConfigPoller.update_product_callback capabilitiescCszC|jjs ||j|||D]}|j|||kr(td||j|q||j|<q|j||j sA|j WdSWdSt yTtj dddYdSw)aRegister a product callback for remote configuration updates. Registration only registers the callback and capabilities. To include the product in client payloads (enable it), call enable_product() separately. Args: product: Product name (e.g., "ASM_FEATURES", "LIVE_DEBUGGING") callback: Callback function to invoke when payloads are received in child processes capabilities: list of capabilities to register for this product zFCapability %s already registered for product %s, skipping registrationzerror starting the RCM clientTexc_infoN) rr:r7register_callbackrr(r*erroradd_capabilitiesis_subscriber_runningstart_subscriberr'r+)rrKrLrN capabilityr"r"r#rQs(    z$RemoteConfigPoller.register_callbackcC|j|dS)a@Enable a product to be included in client payloads. When a product is enabled, it will be added to the 'products' list in payloads sent to the agent, indicating that this client wants to receive configurations for this product. Args: product: Product name to enable N)renable_productrrKr"r"r#rX z!RemoteConfigPoller.enable_productcCrW)a2Disable a product, removing it from client payloads. The product's callback remains registered and can still receive configurations, but the client will not request configurations for this product from the agent. Args: product: Product name to disable N)rdisable_productrYr"r"r#r[rZz"RemoteConfigPoller.disable_productcCsVtjrdSz|j||jjs|WdSWdSty*tjdddYdSw)zUnregister a product callback. This removes the callback but does not disable the product. To also disable the product, call disable_product() separately. Args: product: Product name to unregister Nz#error unregistering from RCM clientTrO) rc_config skip_shutdownrunregister_productr:rFr'r*r+rYr"r"r#unregister_callbacks   z&RemoteConfigPoller.unregister_callbackcCs|jj|S)z*Get the registered callback for a product.)rr:r(rYr"r"r#get_registeredsz!RemoteConfigPoller.get_registeredcCs ||Sr0)r7rr"r"r# __enter__szRemoteConfigPoller.__enter__cGs|jdddS)NTr@)rF)rrIr"r"r#__exit__szRemoteConfigPoller.__exit__)rN)F)rr )__name__ __module__ __qualname____doc__r2rrr)rboolr7r>rArFrHstrrrMrenumIntFlagrQrXr[r_rr`rarb __classcell__r"r"r r#r s:       +   r )rirtypingrrddtracerrddtrace.internalrrddtrace.internal.loggerrddtrace.internal.remoteconfigr$ddtrace.internal.remoteconfig.clientr r\'ddtrace.internal.remoteconfig.constantsr ddtrace.internal.servicer ddtrace.internal.utils.timer rcr*PeriodicServicer remoteconfig_pollerr"r"r"r#s$             ]