Difference between revisions of "GGUS:Ticket monitoring"

From EGIWiki
Jump to: navigation, search
Line 2: Line 2:
  
 
== Ticket Monitoring Dashboard ==
 
== Ticket Monitoring Dashboard ==
For easier triage of critical tickets a [https://ggus.eu/pages/monitor.php dashboard] was implemented.  
+
For easier triage of critical tickets a [https://ggus.eu/?mode=ticket_monitor dashboard] was implemented.  
This dashboard is linked from the "GGUS tools/reports" section with label "Monitor" on [https://ggus.eu/pages/home.php GGUS Home].<br>
+
This dashboard is linked from the "GGUS tools/reports" section with label "Monitor" on [https://ggus.eu/?mode=index GGUS Home].<br>
 
The dashboard is only visible for the GGUS monitoring group.
 
The dashboard is only visible for the GGUS monitoring group.
  

Revision as of 14:31, 3 April 2014

GGUS-logo.jpg


GGUS wiki / GGUS Documentation


GGUS ticket monitoring



Ticket Monitoring Dashboard

For easier triage of critical tickets a dashboard was implemented. This dashboard is linked from the "GGUS tools/reports" section with label "Monitor" on GGUS Home.
The dashboard is only visible for the GGUS monitoring group.

Operations Tickets

Operations tickets are submitted via the operations portal. They are of ticket type OPS.
Monitoring of OPS tickets is done by the COD team.

Middleware Tickets

The monitoring of middleware tickets follows the processes described in this FAQ.

In general the monitoring process given in File:Ticket Monitoring.pdf is also valid for middleware tickets.

  • If there are doubts about tickets, please submit a ticket to Operations SU referencing the tickets in question. Operations SU will then escalate this to TCB

Other Tickets

The monitoring process for non-operations and non-middleware tickets is documented in File:Ticket Monitoring.pdf in detail. A short summary of required actions is as follows:

  • add comments
  • tag ticket for adding to monitoring dashboard
  • set follow-up date
  • set appropriate remind on date
  • assign ticket to site operations managers if applicable
  • involve NGI operations managers if necessary
  • submit a ticket against "Operations" SU referencing untouched tickets

References