3 ms·

I guess the follow up question is how do we assure companies like Slack aren't grossly under reporting their downtime?

• LinuxBender 8y ago
  Create a simple integration that runs from multiple locations, ISP networks, datacenters and log the results back to a monitoring system that records http status codes, integration results, best / average / worst latency 95th percentile. Provide an easy way for Slack to see the results and for others to reproduce the results.
  • rileyt 8y ago
    This might be an interesting service for companies that are paying for software with uptime in their SLA and want to hold them accountable. It would probably pay for itself pretty fast, considering how often companies like Slack are down...
    • LinuxBender 8y ago
      There are companies that do this, but they do not get involved in the 3rd party SLA legal issues. In my humble opinion, I think that each consumer of Slack and other web services should implement their own monitoring. It probably would not hurt to open source the monitoring so that Slack and the ilk can help keep your monitoring accurate and honest. This would empower others to replicate your methods for the service providers they consume as well without having to pay monitoring service providers. They will only show outages from their perspective and some of them run from Amazon, which may be sub-optimal in this case. Some existing open source tooling are Nagios and Sensu. Sensu being a little more dynamic and cloud friendly and a newer kid at the table. There are chef and ansible scripts for both of these.