Octri

monitoring test-event

Sends one test error through the real ingest path. It shows up in monitoring issues a few seconds later, which proves the whole connection works end to end.

It's a setup check, so it only works before the project receives its first real event. After that, the command is refused.

Signed in, the connection comes from your selected project. In CI, pass --url, --token and --environment, or set their environment variables, and no sign-in is needed. monitoring config prints the three values.

bash
octri monitoring test-event

Flags

--url <url>string

The monitoring service's address. Falls back to MONITORING_URL, then to your signed-in project.

--token <token>string

The project's ingest token. Falls back to MONITORING_TOKEN, then to your signed-in project.

--environment <env>string

The monitoring environment. Falls back to MONITORING_ENVIRONMENT, then to your signed-in project.

Examples

Send a test error

bash
octri monitoring test-event
Output
✔ Sending test event
✔ Test event delivered.
  octri monitoring issues: it should appear within a few seconds.