LCj-UdZddlZddlZddlmZddlmZddlmZeZ eddZ ee e d <Gd d ejZdd Zde d ej fdZy)u Structured logging configuration. Why JSON logs: on a production VPS, you (or a log aggregator like Loki/ Grafana) need to filter and search logs reliably. Plain text logs are fine for local dev (human-readable), but production needs machine-parseable fields: timestamp, level, request_id, latency_ms, etc. Every request gets a request_id that flows through all log lines for that request — this is what lets you trace a single farmer's query through validation -> models -> LLM -> response in the logs. N) ContextVar) jsonlogger) get_settings request_id-)defaultrequest_id_ctxc0eZdZdejdefdZy)RequestIdFilterrecordreturnc6tj|_y)NT)r getr)selfr s DC:\Crop_Prediction\Backend\crop-ai-system\app\core\logging_config.pyfilterzRequestIdFilter.filters*..0N)__name__ __module__ __qualname__logging LogRecordboolrrrr r sW..4rr r ctj}|jtj|j j tjtj}|jttjrtjdddd}ntjd}|j!||j#|tjdjtj$tjdjtj$y) Nz=%(asctime)s %(levelname)s %(name)s %(request_id)s %(message)s timestamplevel)asctime levelname) rename_fieldszG%(asctime)s | %(levelname)-8s | %(request_id)s | %(name)s | %(message)szuvicorn.accesshttpx)r getLoggersetLevelsettings LOG_LEVELhandlersclear StreamHandlersysstdout addFilterr LOG_JSONr JsonFormatter Formatter setFormatter addHandlerWARNING) root_loggerhandler formatters r setup_loggingr5#s##%K++, ##CJJ/G o'(,, K&1H %% U  #7# &'00A g''8rnamec,tj|S)N)rr")r6s r get_loggerr8?s   T ""r)r N)__doc__rr) contextvarsrpythonjsonloggerrapp.core.configrr$r str__annotations__Filterr r5Loggerr8rrrrAse  "'( > #-\3"G 3Ggnn 98#S#W^^#r