Skip to content

Next Steps After Install

With the server and at least one worker online, you can start enabling observability and building jobs.

Confirm baseline health

  • Sign in to the UI as an administrator and change the default password if you have not already.
  • Verify the built-in worker (or external workers) show Online in Workers.
  • Confirm liveness responds:
    • Default (self-signed TLS): curl -k https://<server-host>:3000/api/liveness
    • HTTP (only when the server runs with --disable-tls): curl http://<server-host>:3000/api/liveness
  • Run a simple “Hello, world” job and confirm the run completes without errors.

Capturing these checks up front gives stakeholders a clear “green light” that the environment is usable.

Enable worker metrics

New workers default to metrics collection being disabled. To turn it on:

  1. In the web UI, open Workers and select the worker you just registered.
  2. Open the Settings tab and choose Edit Worker Settings.
  3. Set Metrics interval (seconds) (for example 30).
  4. Save the changes and wait for the next worker update.

Harden for production

If you are moving beyond a single-host trial, review these topics before onboarding real datasets:

Explore the job editor

The job editor lets you build and test jobs from the browser. Highlights include:

  • YAML autocompletion and validation
  • Inline evaluation with sample input data
  • Step-by-step tracing to inspect action output
  • Contextual help for inputs, actions, and outputs

From the dashboard, choose Jobs → New job to open the editor and start authoring your first job.

Track adoption metrics

  • Record how many users successfully log in and run their first job (pilot completion rate).
  • Note how long it takes to enable worker metrics and dashboards (observability readiness).
  • Capture any blockers surfaced during the first week so they can feed into the production rollout plan.