ASK RUNDECK WHY THE JOB FAILED — THEN FIX IT.
Connect Rundeck to Menza and ask about jobs, executions, logs and node inventory in plain English — what failed overnight, which jobs run longest, which nodes keep erroring. Menza reads it live through the official Rundeck API, and when a job needs re-running it triggers it only once you approve.
- Reads developer data
- Can take action on Rundeck, once you approve
- Connects via the official API
What can Menza do with Rundeck?
Re-run failures without opening the console
Menza spots the overnight executions that failed, reads the logs for the cause, and proposes the re-run — scoped to the affected nodes — which it triggers the moment you approve.
Let the logs explain themselves
Ask why a job failed and Menza digs through the execution log for the actual error, so you get the cause in plain English instead of scrolling raw output.
Know your node inventory cold
Ask which nodes keep failing, which are missing from a project, or what changed since last week — Menza reads inventory and execution history together and answers straight.
See these answers on your own Rundeck data.
Menza working with Rundeck.
Menza doesn't just answer questions about Rundeck — it proposes the fix and, once you approve, does the work. You stay in control; nothing changes until you say go.
Menzajust nowThe nightly backup job failed on three of 42 nodes — its first failures in 26 days. I'll re-run the backup against just those three nodes — the logs show a full disk caused each failure.
Menza6m agoAverage execution time on your deploy job crept from four minutes to eleven over two weeks. I'll kill the execution that's been hung since this morning and trigger a clean run.
Connect Rundeck in a couple of clicks.
Is my Rundeck data secure?
Your credentials are encrypted at rest and never exposed to the AI. Menza reads your data through the provider's official API using the access you grant, and you stay in control of what it can do — read-only by default, with any actions gated behind your approval.
Read our privacy policy- Encrypted in transit and at rest
- Scoped access — you choose what Menza can see
- Read-only by default; any action needs your approval
- Credentials are encrypted and never shown to the AI
- Revoke access at any time
Rundeck questions, answered.
How does Menza connect to Rundeck?
You connect with a Rundeck API token — about a minute of setup. The token is encrypted at rest and never shown to the AI. Menza then talks to the official Rundeck API on your behalf, so there's nothing to install on your nodes and nothing to export.
What can Menza answer about my Rundeck data?
Anything Rundeck exposes: projects, jobs, executions and their logs, node inventory and system info. Ask which jobs failed overnight, how long the deploy job has been trending, which nodes error most, or what a specific execution's log actually says went wrong.
Is my Rundeck data safe with Menza?
Yes. Your API token is encrypted, never exposed to the AI, and Menza only reaches the projects the token allows. It reads jobs, executions and logs to answer questions, and any action — running or re-running a job — always waits for your explicit approval first.
Which projects and jobs can Menza touch?
Exactly what your API token permits, and nothing more. Scope the token to the projects you want covered and Menza reads within that boundary. Even inside it, Menza never triggers, re-runs or kills anything without you approving that specific action.