www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Schaefer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7651) Document what we think are core services
Date Thu, 01 May 2014 15:55:14 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986691#comment-13986691
] 

Joe Schaefer commented on INFRA-7651:
-------------------------------------

I agree with Jan.  In order to keep the lists well-maintained, we need to incorporate them
into our circonus configuration and generate the service breakdown as appropriate.  While
I am loathe to pretend we will be operating under SLA's because our contracts aren't structured
like that, a general breakdown of our response priorities would be useful.


> Document what we think are core services 
> -----------------------------------------
>
>                 Key: INFRA-7651
>                 URL: https://issues.apache.org/jira/browse/INFRA-7651
>             Project: Infrastructure
>          Issue Type: Task
>            Reporter: David Nalley
>            Assignee: Joe Schaefer
>
> Per the conversation we had during the post-mortem today, we need to document the services
that we consider core to properly set expectations and expected service levels around them.
This may mean we define several strata and pigeonhole services into the various strata. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message