Oo Datalust

Datalust Seq

Operate Datalust Seq through your OOMOL-connected account. This skill calls the datalust connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Datalust Seq. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "datalust" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "datalust" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• create_saved_query — Create a saved Seq SQL query while preserving server-provided template defaults. [write]
• create_signal — Create a Seq signal while preserving server-provided template defaults. [write]
• delete_saved_query — Delete a saved Seq SQL query by its identifier. [destructive]
• delete_signal — Delete a Seq signal by its identifier. [destructive]
• execute_query — Execute a Seq SQL-style query and return its structured JSON result.
• get_event — Read one Seq event by its event identifier.
• get_saved_query — Read one saved Seq SQL query by its identifier.
• get_signal — Read one saved Seq signal by its identifier.
• ingest_event — Ingest one structured log event into Seq using compact log event format.
• ingest_events — Ingest a JSON array of structured log events as one newline-delimited CLEF batch.
• list_saved_queries — List saved Seq SQL queries visible to the API key.
• list_signals — List saved Seq signals visible to the API key.
• search_events — Search a page of Seq events using a filter, signal, time range, or cursor.
• update_saved_query — Update selected fields on a saved Seq SQL query while preserving unspecified fields. [write]
• update_signal — Update selected fields on a Seq signal while preserving unspecified fields. [write]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Datalust Seq state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — Datalust Seq is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  https://console.oomol.com/app-connections?provider=datalust
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Datalust Seq homepage: https://datalust.co/seq