Skip to content
Hoody.com

The notification server exposes two unauthenticated endpoints for operational visibility: a structured health probe and a Prometheus-compatible metrics scrape. Use them from container orchestrators, load balancers, and monitoring agents to verify the service is reachable and to collect runtime telemetry.

All endpoints live on the notification service subdomain of the container’s runtime URL. No authentication is required.

Returns a standardized 9-field health document describing the running notification process. This endpoint is unauthenticated and always responds with HTTP 200 when the service is reachable. Use it from readiness/liveness probes and from uptime monitors.

This endpoint takes no parameters.

Terminal window
curl https://{projectId}-{containerId}-n-1.{server}.containers.hoody.com/api/v1/notifications/health
NameTypeRequiredDescription
statusstringYesOne of: ok. Indicates the service is healthy.
servicestringYesService identifier reported by the process.
builtstringNoExecutable mtime as an RFC3339 string.
startedstringYesProcess start time as an RFC3339 string.
memoryobjectNoProcess memory snapshot.
fdsintegerNoCount of open file descriptors.
pidintegerYesHost process ID.
ipstringYesLocal IP address the process bound to.
userAgentstringNoRuntime user agent string.

The memory object contains:

NameTypeRequiredDescription
rssintegerYesResident set size in bytes.
heapintegerNoLanguage runtime heap in bytes (null for Rust).

Returns runtime metrics in Prometheus text exposition format. Use this endpoint from a Prometheus scraper or any OpenMetrics-compatible collector to ingest counters, gauges, and histograms emitted by the notification server.

This endpoint takes no parameters.

Terminal window
curl https://{projectId}-{containerId}-n-1.{server}.containers.hoody.com/api/v1/notifications/metrics