Approve a fix on the Varqeni host
Approving needs administrator access to the host that runs Varqeni. In early access this is usually Fortis, working with you.
AvailabilityFor the person who runs Varqeni for your team. In early access that is usually Fortis, working with you.
Steps
- Read the investigation's report and confirm what it asks, for example that nobody paused the connector on purpose.
- On the host, run the command the report prints, with your name:
sudo opsagent-approve <incident> resume_connector --by "Emma Clarke"for a pipeline fix,sudo opsagent-approve-infrafor an infrastructure fix, orsudo opsagent-approve-servicefor a service fix. - Exit code 0 means the fix was sent and verified within 90 seconds. Exit code 2 means it was refused, nothing sent, or it did not recover. The printed result says which.
What you should see: The outcome appears under Actions in the console, sealed with your name.
What it can and cannot do
Can
- Run one fix once, with your name sealed into the outcome.
Cannot
- Approve an incident older than 60 minutes, or retry a fix that did not recover.
If it does not work
- Approvals older than 60 minutes are refused: let Varqeni investigate again and approve the new incident.
Related articles
- Approve a recommended fixWhen a report recommends a fix, a person on the on-call rota approves it for that one incident, in the console. Varqeni runs it once and checks it.
- Stop every action at onceThe kill switch stops all fixes, by a person or the autopilot, immediately.
Still stuck? Contact support or email info@fortisdatagroup.com.