Function check_environment
This page is for NeMo Fabric, version v0.6.0.
For other versions, use one of these documentation indexes:
- Latest (v0.6.0) (default): https://docs.nvidia.com/nemo/fabric/latest/llms.txt
- dev: https://docs.nvidia.com/nemo/fabric/dev/llms.txt
- v0.6.0: https://docs.nvidia.com/nemo/fabric/v0.6.0/llms.txt
- v0.5.0: https://docs.nvidia.com/nemo/fabric/v0.5.0/llms.txt
- v0.4.0: https://docs.nvidia.com/nemo/fabric/v0.4.0/llms.txt
- v0.3.0: https://docs.nvidia.com/nemo/fabric/v0.3.0/llms.txt
- v0.2.0: https://docs.nvidia.com/nemo/fabric/v0.2.0/llms.txt
- v0.1.1: https://docs.nvidia.com/nemo/fabric/v0.1.1/llms.txt
- v0.1.0: https://docs.nvidia.com/nemo/fabric/v0.1.0/llms.txt
Generated from cargo doc --no-deps -p nemo-fabric-core.
pub fn check_environment(
environment: &EnvironmentHandle,
request: &CheckRequest,
) -> Result<CheckReport>
Check server or runtime health through a supplied environment.
Local runtime checks use the adapter health channel. OpenShell checks use the sandbox command bridge. Local server checks return unsupported_scope. Use check_service for registered local services. Timeouts and ownership changes return unknown health evidence.
