TaliLink Monitoring

Read-only observation · no ability to change anything

Auto-refreshing every 20s

Live activity

Distinct people who made an authenticated request in the last 5 minutes.

Not measurable yet

TaliLink issues stateless JWTs, so there is no session table to count. Knowing who is currently using the platform requires the API to log who made each request — which it does not do yet.

What would unlock it

  • A request-logging interceptor in the TaliLink API that emits one structured line per authenticated request
  • That line carrying the user id and role, so staff and candidates can be told apart

Right now

Talents active

Not instrumented

TaliLink does not report this yet. Shipping the metrics endpoints will fill it in.

Staff active

Not instrumented

TaliLink does not report this yet. Shipping the metrics endpoints will fill it in.

Requests in window

Not instrumented

TaliLink does not report this yet. Shipping the metrics endpoints will fill it in.

Last 12 hours

Active people over time

Talents and staff, counted per snapshot

Nothing recorded for this metric yet.

Traffic as a proxy

Until per-user logging ships, request volume is the best available signal that people are actually on the platform.

Requests at the load balancer