Examine the current CloudI services and their configuration to log any service configuration values that look like a mistake.
.Copyright © 2023 Michael Truog
Version: 2.0.7 Oct 26 2023 16:18:17 ------------------------------------------------------------------------
Behaviours: cloudi_service.
Authors: Michael Truog (mjtruog at protonmail dot com).
Examine the current CloudI services and their configuration to log any service configuration values that look like a mistake.
This service's logic exists separate from the CloudI configuration logic because the dynamic nature of CloudI services requires flexibility. Only CloudI service configuration that is clearly invalid creates an error when the service attempts to start. However, service configuration values may only become used after a CloudI service is updated. A CloudI service could have configuration values for sending service requests without the logic for sending service requests until after the service is updated. A CloudI service could delay its subscription to service name patterns to delay its ability to receive CloudI service requests while still having service configuration values only valid for receiving service requests.
Run this service to identify service configuration inconsistencies and use the CloudI log output to modify the service configuration if unexpected problems are discovered.cloudi_service_handle_info/3 | |
cloudi_service_init/4 | |
cloudi_service_terminate/3 |
cloudi_service_handle_info(X1, State, Dispatcher) -> any()
cloudi_service_init(Args, Prefix, Timeout, Dispatcher) -> any()
cloudi_service_terminate(Reason, Timeout, State) -> any()
Generated by EDoc