Home / Product / Health and monitoring

See the backend clearly

Know whether the backend is reachable—and whether the product paths people need still work.

Use health, runtime statistics, structured logs, rotation controls, and optional profiles as the starting point for meaningful operational visibility.

01Detect basic availabilityCheck whether the runtime responds at all.
02Investigate with contextCollect structured logs and runtime statistics.
03Observe real customer pathsAdd checks for the capabilities your product actually depends on.
Why it matters

A green health check can coexist with a broken customer experience.

Check sign-in, database capacity, storage reachability, and queue age alongside process health. Run workflow checks for authentication, protected reads, file delivery, email, schedules, and integrations.

Daptin provides a health endpoint, runtime statistics, structured logging with rotation options, and optional CPU or heap profiles. These surfaces reveal the process and help operators investigate.

A complete monitoring plan builds on them with synthetic paths: authenticate, read a permissioned record, fetch an asset, run a safe action, and check every protocol or queue the product promises.

01

Start with a clear liveness signal

Know whether the service can answer at all.

02

Keep investigation evidence

Use logs and statistics to understand resource and request behavior.

03

Measure what customers experience

Turn the application's important journeys into external checks.

See what customers experience

Turn availability signals into clear operating decisions.

Check whether Daptin can serve customers, watch traffic and capacity, investigate failed requests and routines, and practice restoring business information with uploaded files.

Diagram showing customer availability, traffic and capacity, request and problem history, operating actions, backups, and restoration practice.
See experience, capacity, history, and recovery togetherSend traffic only to ready services, add capacity as demand grows, let accepted requests finish before restart, and restore related information together.Open diagram for full-size view
How it fits

Part of one connected backend.

Health and monitoring does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Probe

Check the process from outside its own runtime.

Step 2Collect

Centralize logs and relevant runtime statistics.

Step 3Exercise

Test representative identity, data, file, action, and service paths.

Step 4Alert

Alert operators when workflow completion, latency, queue age, or capacity crosses its configured threshold.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Customer portal check

Sign in as a test user and read one protected record.

File-path check

Fetch a known asset through its real storage and permission path.

Mail operations

Check sign-in, database access, file storage, queues, listeners, and schedules alongside process health.

Know the boundary

What Daptin leaves in your hands.

Send Daptin health, statistics, logs, and profiling signals to the monitoring, incident, log, and service-level systems your team operates. Restrict profiling endpoints and redact credentials, tokens, and customer secrets from logs.

Understand the operating responsibility →

Build from one foundation

Track sign-in, database access, storage reachability, queue age, listeners, and scheduled work.

Run Daptin locally, explore the live administration surface, and follow one complete application path.