Skip to main content
SRE who want a Julius workbook from Vertex scores, not a BigQuery slot

The Vertex telemetry stack

n8n takes the log burst, Vertex scores multimodal anomalies, Julius is the workbook. BigQuery stays a write inside n8n.

Who owns what

  1. n8n

    The hop — logs in, Julius out. BigQuery is infra, not a slot.

    Try n8n (opens in a new tab)
  2. Vertex AI

    The score — image+text log anomalies. Not the sheet.

    Try Vertex AI (opens in a new tab)
  3. Julius AI

    The workbook — charts the on-call defends. Not Vertex training.

    Try Julius AI (opens in a new tab)

How to use this stack

  1. Alert payload hits n8n. Warehouse inserts stay in the node, not a fourth tool.
  2. Vertex scores the burst (screenshot plus log text). Do not also run Groq on the same dump.
  3. n8n appends the scored rows into Julius. One orchestrator.
  4. This is not spreadsheet-to-brief (that one starts from a CSV, not telemetry). Not OpenRouter RCA.