Welcome!

@DevOpsSummit Authors: Yeshim Deniz, Zakia Bouachraoui, Liz McMillan, Pat Romanski, Elizabeth White

Related Topics: @DevOpsSummit, Java IoT, Containers Expo Blog

@DevOpsSummit: Blog Feed Post

NOC, NOC… Who’s There? By @VictorOps | @DevOpsSummit [#DevOps]

A NOC, for those who don’t know, stands for Network Operations Center

By Bryce Ambraziunas

In part one of this series, our COO tackles the history and purpose of the NOC.

A NOC, for those who don’t know, stands for Network Operations Center and, quite simply, is how large organizations with complex systems monitor them. Early versions of the NOC came about in the early 1960’s when there was a need for humans to actively take part in noticing, and fixing, complex errors. An early NOC was opened by AT&T in New York to display switch and route information, in real-time. It’s easy to see why a NOC used to be considered essential for larger companies that deal with a myriad of issues that call for escalation and rational judgement.

6281302040_f44da69e93_z

Back when the NOC was based in the telecommunications industry, the job was a much different one. The Network Operations Center was designed so that all of the important information necessary to the system was easily consumed by a few people sitting in the same “war room” if you will. There were several rows of desks, all facing a wall of big screens which typically show critical info in real time, making the sharing of this data amongst the group very simple.

Today NOC engineers monitor infrastructure health, security and capacity while making decisions that optimize network performance. Depending on what incidents arise, the NOC might be researching anomalous activities, making adjustments and corralling the resources needed for an emergency situation. The depth of their coverage ranges from troubleshooting app installations to backup management to firewall monitoring.

Some companies opt for an in-house NOC while others can’t justify the cost and therefore turn to outsourced options. Both choices have pros and cons to them (enough for a completely different post) but one thing that can be said of the NOC – it is not designed to be a help desk. The NOC provides back end maintenance, problem resolution and support so that the company can be freed up to deal with client-facing issues. Fielding front-line questions from customers is the responsibility of a help desk or support team – not the NOC.

Historically, the NOC was standard operating procedure and just assumed to be the only way to deal with complex systems. There has always been a need for human intervention and the NOC provided that. They were created out of this necessity but today, many of the traditional NOC functions have been automated and replaced by monitoring software.

We view the NOC as the human version of what our product does. To that end, in part 2 of this series, I’ll show how VictorOps can be used to empower the traditional NOC.

The post NOC, NOC…who’s there? appeared first on VictorOps.

Read the original blog entry...

More Stories By VictorOps Blog

VictorOps is making on-call suck less with the only collaborative alert management platform on the market.

With easy on-call scheduling management, a real-time incident timeline that gives you contextual relevance around your alerts and powerful reporting features that make post-mortems more effective, VictorOps helps your IT/DevOps team solve problems faster.

@DevOpsSummit Stories
The best way to leverage your Cloud Expo presence as a sponsor and exhibitor is to plan your news announcements around our events. The press covering Cloud Expo and @ThingsExpo will have access to these releases and will amplify your news announcements. More than two dozen Cloud companies either set deals at our shows or have announced their mergers and acquisitions at Cloud Expo. Product announcements during our show provide your company with the most reach through our targeted audiences.
Enterprises are universally struggling to understand where the new tools and methodologies of DevOps fit into their organizations, and are universally making the same mistakes. These mistakes are not unavoidable, and in fact, avoiding them gifts an organization with sustained competitive advantage, just like it did for Japanese Manufacturing Post WWII.
When building large, cloud-based applications that operate at a high scale, it's important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. "Fly two mistakes high" is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee Atchison, Principal Cloud Architect and Advocate at New Relic, discussed how this same philosophy can be applied to highly scaled applications, and can dramatically increase your resilience to failure.
DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term.
With more than 30 Kubernetes solutions in the marketplace, it's tempting to think Kubernetes and the vendor ecosystem has solved the problem of operationalizing containers at scale or of automatically managing the elasticity of the underlying infrastructure that these solutions need to be truly scalable. Far from it. There are at least six major pain points that companies experience when they try to deploy and run Kubernetes in their complex environments. In this presentation, the speaker will detail these pain points and explain how cloud can address them.