Service desk
The service desk sits beside Varqeni's own incidents. People raise tickets here or through the API; Varqeni already sees the systems, so a ticket about something it is watching can be tied to the incident it opened.
Steps
- Raise a ticket: choose New ticket, say whether it is a request or a problem report, give it a title, and set its impact (how many it affects) and urgency (how soon it hurts). The priority follows from both, P1 critical to P4 low, and is shown before you send.
- The queue: open tickets come first by priority, then the oldest. Filter by state, priority, group or owner, choose Mine for your own, and search titles and references. On a keyboard, j and k move and Enter opens.
- The clocks: each priority has a time to first response and a time to resolve. The ring on each ticket fills as the time is used, turns amber at three quarters and red when it is past. Waiting on the requester or a third party pauses it.
- Owners: a P1 or P2 that nobody owns goes to whoever is on call for its group. A P1 pages them; a P2 tells them.
- Incidents: when Varqeni has an incident open on the ticket's system, the ticket offers it. Link it, or say it is not this problem. When a linked incident resolves, its tickets resolve with it, with the incident's summary. Requesters are emailed once a mail server is set up.
- Replies and notes: a reply goes to the requester; an internal note stays with the people working tickets.
- History: every change is kept in order, with who made it, and sealed like the rest of Varqeni's record.
- The past: while the time bar shows a moment in the past, tickets are read only. Go back to live to change one.
What you should see: Who may do what follows the roles in your on-call file: responders, approvers and admins work tickets; anyone signed in can read the queue and follow their own tickets. In the Fortis lab a P2 ticket was given to the person on call, offered the incident Varqeni opened for a real fault, and resolved by itself when that incident recovered; a P1 raised its warning at three quarters of its 15 minute response time; and the sealed history checked out against its locked copy.
What it can and cannot do
Can
- Keep requests and problem reports in one queue with an ITIL priority from impact and urgency, response and resolution clocks that pause while waiting, an owner from the on-call rota, and a link to any incident Varqeni has open on the same system.
Cannot
- Email requesters until a mail server is set up, or take tickets by phone or email yet.
Related articles
- The On-call viewWho is on call now, the rules for paging and escalation, and every page with what happened to it.
- Paging and escalationVarqeni pages the person on call only when it cannot settle an incident itself, and escalates when nobody answers.
- The live mapOne picture of everything Varqeni watches: each pipeline's data path, your services, the database, the platform they run on and the hosts underneath, live.
Still stuck? Contact support or email info@fortisdatagroup.com.