orangeqs.juice.schemas.logging#
Schemas for Logging Configuration.
Module Contents#
Classes#
Log Event Point. |
|
Logging Configuration of a single Service. |
|
Centralized logging configuration for all Juice services. |
API#
- class orangeqs.juice.schemas.logging.LogEvent(/, **data: Any)#
Bases:
orangeqs.juice.database.PointLog Event Point.
- class orangeqs.juice.schemas.logging.ServiceLoggingConfig(/, **data: Any)#
Bases:
orangeqs.juice.settings.BaseConfigurableLogging Configuration of a single Service.
- class orangeqs.juice.schemas.logging.ServiceLoggingConfigs(/, **data: Any)#
Bases:
orangeqs.juice.settings.ConfigurableCentralized logging configuration for all Juice services.
By default, all services inherit the same logging settings, which can be customized for individual services as needed. Each service logs to both InfluxDB2 and stdout, with handlers set to capture messages at
INFOlevel and above by default.You can review logs via the dashboard or by using
Client.display_service_logsWARNING: A service must be restarted for changes to its logging configuration to take effect.
- services: collections.defaultdict[str, Annotated[orangeqs.juice.schemas.logging.ServiceLoggingConfig, Field(default_factory=ServiceLoggingConfig)]]#
‘Field(…)’
Logging configuration for each service.