{"id":2866,"date":"2021-05-28T09:59:15","date_gmt":"2021-05-28T16:59:15","guid":{"rendered":"https:\/\/44.203.207.232\/?p=2866"},"modified":"2021-05-28T09:59:16","modified_gmt":"2021-05-28T16:59:16","slug":"salesforce-outage-linked-to-dns-configuration-change","status":"publish","type":"post","link":"https:\/\/webdev.siff.io\/salesforce-outage-linked-to-dns-configuration-change\/","title":{"rendered":"Salesforce Outage Linked to DNS Configuration Change"},"content":{"rendered":"\n
Yes, another example of an incident. In this case a very visible global outage, due to infrastructure misconfiguration.\u00a0If you are not familiar with the Salesforce outage, read more<\/a>. <\/p>\n\n\n\n Before you sound the trumpet for more DevOps automation, of which I am a strong supporter, what I would like to highlight is the need for visibility to the configuration changes (or lack thereof), for completed change requests.\u00a0<\/p>\n\n\n\n Visibility to all configuration changes across your entire infrastructure: networks, servers, apps, containers, and cloud is essential for effective incident response, to quickly narrow down and isolate the root cause. Change monitoring; however, can also be used as a proactive tool to prevent incidents by correlating configuration changes with planned change requests, in order to make it easier to see what configuration was changed from the completed work.\u00a0<\/p>\n\n\n\n During the post implementation review stage of the change process, reviewers can examine whether the resulting configuration changes have errors and\/or are missing. This may give the slight chance needed, to prevent an incident or outage from occurring.<\/p>\n\n\n\n Regarding the Salesforce DNS misconfiguration outage, the change was indeed automated, but there was a bug in the automation that caused the problem. Making it easy to review the configuration changes will enable reviewers to check for errors, especially for manual changes.<\/p>\n\n\n\n If you\u2019re responsible for your company\u2019s infrastructure operations, come visit us at SIFF.IO<\/a> to find out \u201cWhat the #%&$ changed?!\u201d<\/p>\n\n\n\n