Skip to content
Hoody.com

The Files service exposes a standard health endpoint for liveness probes, observability scripts, and platform-level diagnostics. Use these endpoints to verify that a container’s Files service is running, inspect build and start timestamps, and capture caller metadata (IP and User-Agent) along with runtime resource usage such as open file descriptors and resident memory.

Service health check. Returns service identity, build and start timestamps, resource usage, and caller metadata.

This endpoint takes no parameters.

Terminal window
curl -X GET "https://{projectId}-{containerId}-files-1.{server}.containers.hoody.com/api/v1/files/health" \
-H "Authorization: Bearer <token>"

Service is healthy.

{
"status": "ok",
"service": "hoody-files",
"built": "2026-01-12T08:30:00.000Z",
"started": "2026-01-15T14:22:11.482Z",
"memory": {
"heap": null,
"rss": 48234496
},
"fds": 18,
"pid": 24853,
"ip": "203.0.113.42",
"userAgent": "curl/8.5.0"
}
FieldTypeDescription
statusstringService status indicator. Typical value: ok.
servicestringService identifier. Typical value: hoody-files.
builtstring | nullBuild timestamp of the service binary.
startedstringTimestamp at which the service process started.
memoryobjectCurrent process memory usage.
memory.heapnullAlways null for native services.
memory.rssinteger | nullResident set size in bytes.
fdsinteger | nullOpen file descriptor count.
pidintegerProcess identifier of the running service.
ipstringCaller IP address. Empty string when the request arrives over a Unix socket.
userAgentstringUser-Agent header from the incoming request.