threshold.subject_unknown

A threshold watches a route, action, query, schedule or subscriber its domain doesn't have.

Area 16, Built-in services; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

A threshold says when something your app does is too slow or failing too often, and the rules generated from it alert on that one thing. One that names nothing would never be judged, so a misspelt name would leave the route or action it meant unwatched without anyone noticing. A domain's monitoring.jadpo watches only its own domain, so each domain's file is the whole of what watches it.

What it looks like

counting names an action that isn't declared:

/// How many visitors have come.type VisitorCount = Int {    min: 0}/// How many visitors have come so far.action count_visitors() -> VisitorCount {    return 1}thresholds {    /// Counting the visitors stays quick.    counting: {        watches: count_visitor        p95: 50ms    }}

   |14 |         watches: count_visitor   |                  ^^^^^^^^^^^^^ nothing to watch

(agent) at the end of the next: line means your coding agent can make the fix itself.

How to fix it

If the name is misspelt, name what the threshold watches:

    counting: {        watches: count_visitors        p95: 50ms    }

counting now watches count_visitors, and the rules made from it alert when that action's 95th percentile passes 50 ms.

A route is named by its method and its path as jadpo routes prints it, as a route test names one: route: { method: HttpMethod.post path: "/hello" }. Another domain's route or action is watched from that domain's own monitoring.jadpo.

Related

• Monitoring thresholds
• Writing a threshold