<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Moogsoft AIOps on Medium]]></title>
        <description><![CDATA[Stories by Moogsoft AIOps on Medium]]></description>
        <link>https://medium.com/@moogsoft?source=rss-fe410e3471d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XpHh87boKgYdSg1FijxcwQ.png</url>
            <title>Stories by Moogsoft AIOps on Medium</title>
            <link>https://medium.com/@moogsoft?source=rss-fe410e3471d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:22:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@moogsoft/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Impact of Artificial Intelligence on IT Operations in 2019]]></title>
            <link>https://medium.com/moogsoft/the-impact-of-artificial-intelligence-on-it-operations-in-2019-7c809e02e2a3?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c809e02e2a3</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[it-operations]]></category>
            <category><![CDATA[aiops]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Fri, 12 Apr 2019 15:46:07 GMT</pubDate>
            <atom:updated>2019-04-12T15:46:07.566Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: Phil Tee, CEO of Moogsoft</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8OCMBAe1EkdN4Bk2cCm88g.jpeg" /></figure><p>Artificial intelligence is changing business operations, and companies can expect to see significant shifts in the role of AI for IT operations, or <a href="https://www.moogsoft.com/">AIOps</a>, in 2019. The power of AI doesn’t stop at robotics, driverless cars or voice-controlled speakers. AIOps is truly <a href="https://www.moogsoft.com/customers/">moving the needle </a>for IT operations, putting to use the big data enterprises produce each day for a more productive IT team. With the proper tools in place, enterprises can automatically reduce the number of daily system alerts, empowering IT to ensure peak performance, service integrity, and business agility.</p><p>Here are five predictions for the growing AIOps market in the coming year:</p><p><strong>1. Automation will shift the focus of IT operations</strong></p><p>Efficient IT operations depend on an enormous amount of data to understand how devices and applications perform in an organization’s global infrastructure. The mechanical process for digesting this data, conducting analysis, rejecting false results, and isolating potential root cause is more efficient and more accurate when done with AIOps.</p><p>In 2019, IT will value the ability to apply business analytics to results generated by AIOps, as opposed to simply detecting incidents and dispatching triage. Humans are still critical to the process of setting appropriate service levels and instructing AIOps platforms on how to affect better business outcomes. IT professionals will shift their focus to reducing the impact of incidents on both internal and external customers in alignment with customer success teams.</p><p><strong>2. AIOps will be a necessity for new industries</strong></p><p>AIOps enables agile team workflows to ensure the maximum performance and integrity of IT operations. Because of this, industries with exponential growth in system data — such as telecommunication service providers — will be the most likely to adopt AIOps this year. This is akin to the financial services sector, which successfully adopted AI in high-volume trading systems, followed closely by large manufacturers and pharmaceutical companies.</p><p>AIOps will be the only way for telecommunication service providers to ensure the integrity of 5G operations in 2019. Cell towers have a transmission range of about 10–19 miles, but 5G networks use much smaller cells limited to a range of 32 feet to one mile. The volume of 5G cells will exponentially grow the number of systems that need monitoring. The telemetry volume of 5G systems will swamp outdated legacy technology developed during the 1990s. For many telecom providers, AIOps will be the only viable solution.</p><p><strong>3. The number of AIOps use cases will expand</strong></p><p>The transformation of AIOps began with the automation of IT event response, as a result of growing compute capacity and big data enabled by the cloud. Now AIOps can leverage time series data and machine learning in additional ways. This year will see new use cases for AIOps such as cybersecurity and capacity planning. As this happens, AIOps will eventually touch all areas of digital operations. This will be especially true for organizations using a mix of private, hybrid and public cloud applications and infrastructure.</p><p><strong>4. Service providers will use AIOps to differentiate on durability</strong></p><p>Many service providers are currently facing the challenge of effectively differentiating themselves and their offerings from competitors. In 2019, AIOps will be used by some to demonstrate their durability. AIOps allows service providers to ensure peak performance and operational continuity, and then to deliver valuable data as substantial proof of durability. This year, organizations will capitalize on the effectiveness of AIOps for keeping systems stable, avoiding typical incidents, ensuring availability and protecting customers from outages and downtime.</p><p><strong>5. The AIOps market will become (more) crowded and noisy</strong></p><p>As the power and potential of AIOps become more widely understood by enterprise buyers, expect the large legacy IT vendors to “follow the money.” As more providers join the conversation, IT professionals will be challenged to separate reality from hype. We should expect buyers to become more savvy and discerning. AIOps is impacting all businesses that run on IT, and no one will be exempt.</p><p>Virtually every profession faces the changes brought by AI-enabled automation. Every IT organization can benefit from AIOps and its ability to deliver operational continuity and business agility. 2019 is definitely a year to watch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c809e02e2a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/the-impact-of-artificial-intelligence-on-it-operations-in-2019-7c809e02e2a3">The Impact of Artificial Intelligence on IT Operations in 2019</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AIOps Liberates IT beyond the Antiquity of Rules]]></title>
            <link>https://medium.com/moogsoft/aiops-liberates-it-beyond-the-antiquity-of-rules-1b26b9d40e11?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b26b9d40e11</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[rules]]></category>
            <category><![CDATA[aiops]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Fri, 22 Mar 2019 16:11:04 GMT</pubDate>
            <atom:updated>2019-03-22T16:11:04.478Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: <a href="https://www.moogsoft.com/author/philtee/">Phil Tee</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uDf1uGDoirnGT5rbG3D52Q.jpeg" /></figure><p><em>This blog is the fifth and final in the series, “How AIOps Liberates IT from a Rules-based Approach”.</em></p><h3>Summary</h3><p><em>1. AIOps liberates IT professionals from rules-driven workflows that are repetitive mental drudgery, providing the opportunity to advance new skills, knowledge, and productivity.</em></p><p><em>2. Because AIOps is a mathematical machine learning approach, a single algorithm can replace the logic of hundreds of thousands of rules.</em></p><p><em>3. IT Operations must move beyond the antiquity of rules-based solutions and put the modern machine-learning of AIOps to work, sooner not later.</em></p><p>I grew up in England close to <a href="https://en.wikipedia.org/wiki/Textile_manufacture_during_the_British_Industrial_Revolution">the birthplace of the Industrial Revolution</a>. The wrenching, cataclysmic social changes in the transition to the new steam powered and automated manufacturing processes between 1780–1830 were prelude to a new world. An agrarian and subsistence economy was revolutionized by machines used to automate production of textiles and other goods at a mind boggling scale. You could say the drive to <em>mechanize</em>became the philosophical core of twentieth century life. Orderly systems. Cogs in a wheel. Predictable behaviors. Pre-determined results. All governed by rules. All beautifully captured by <a href="https://www.youtube.com/watch?v=HPSK4zZtzLI">Charlie Chaplin in <em>Modern Times</em></a>.</p><h3>Moving Beyond Rules</h3><p>The days of the <a href="https://www.thoughtco.com/who-invented-the-spinning-jenny-4057900">“Spinning Jenny”</a> are long gone. But rules are still everywhere. As we grapple again with the turmoil of change in the twenty-first century, it’s a good time to ask why. This question is particularly germane as many people wonder if AI and machine learning (ML) is about to trample life as we know it — just like <a href="https://www.history.com/news/who-were-the-luddites">the Luddites did</a> during the Industrial Revolution.</p><p>The rules I speak of are not the guardrails of everyday life like obeying traffic laws, complying with health regulations, and paying your taxes (or else).</p><p>Moogsoft is about improving IT Operations at enterprises which — despite being run globally at scale on esoteric virtual cloud systems — typically bet their performance and uptime on rules.</p><p>In this <a href="https://www.moogsoft.com/blog/aiops/how-brittle-rules-frustrate-it-operations/">educational blog series</a>, we’ve dissected serious limitations with rules-based solutions and why they are insufficient to effectively manage IT Operations. We’ve learned that:</p><ul><li>Rules have the illusion of simplicity, but instead add exponential complexity because they are brittle and easy to break</li><li><a href="https://www.moogsoft.com/blog/aiops/understanding-the-true-cost-of-rules/">Rules are expensive</a> to maintain and carry hidden costs</li><li><a href="https://www.moogsoft.com/blog/aiops/the-teeny-tiny-scope-of-rules">Rules are unpredictable</a> in complex environments due to their tiny scope.</li><li><a href="https://www.moogsoft.com/blog/aiops/the-undecidable-challenge-of-rules">Rules are undecidable</a> in real-world failure scenarios, which renders them deficient for continuous service assurance.</li></ul><h3>AI and Machine Learning are New Enablers</h3><p>We’ve also described how AI and ML liberate IT from each and every limitation of rules. The fundamental difference is how AI/ML uses monitoring data. A rules-based system separates the infrastructure you’re trying to understand from the data it produces. To predict trouble, it applies pre-built logic to the alerts generated by system events. As I’ve outlined in this blog series, this doesn’t always work as advertised.</p><p>AI/ML takes the opposite approach. It does <em>not</em> treat data as separate from the system. You cannot go from state to event, but you can go from event to state. This approach assumes there is signal in the noise produced by alerts, which is interpreted mathematically by statistical machine learning to infer the existence of issues worth investigating. And if you think that notion is an oddity, this relationship of the system to the observer has been common currency for centuries in everything from <a href="http://www.marketfaith.org/non-christian-worldviews/a-basic-understanding-of-eastern-mysticism/">eastern mysticism</a> to <a href="https://www.quora.com/In-laymans-term-what-is-a-quantum-state">quantum mechanics</a>.</p><p>In the practice of IT operations, we are just now realizing you cannot separate the two.</p><p>AIOps allows you to discover incidents previously not detected by a rules-based solution. Statistical ML can use the same algorithm to infer one type of instance from other types. Algorithms themselves are error-resistant and don’t need to have all of the data to make reliable conclusions. Algorithms are deterministic — meaning that they always produce the same output, regardless of input. Algorithms work no matter the order in which the data is processed. Because AIOps is a mathematical ML approach, a single algorithm can replace the logic of hundreds of thousands of rules. In fractions of a second.</p><p>All of this sounds so straightforward, it’s almost magical. So why isn’t everyone using AIOps?</p><h3>Breakthroughs and Impediments for Change</h3><p>For one thing, the application of statistical ML in IT operations entails fairly new techniques. The concepts have been around since <a href="https://blogs.scientificamerican.com/guest-blog/how-alan-turing-invented-the-computer-age/">Alan Turing’s breakthrough</a> 90 years ago. The foundations for modern AI algorithms were laid during the 1960s, ’70s, and ’80s. The earliest commercial applications were stock trading systems, then followed others such as fraud detection and handwriting recognition.</p><p>Three recent breakthroughs have finally facilitated the wide adoption of AI/ML for IT Operations.</p><p>First, statistical ML requires very powerful computers, which have become common only in the last decade. Second, statistical ML requires <em>lots and lots</em> of data. The ease of storing, accessing, and using Big Data is finally practical thanks to the global cloud, and of course thanks to the ironclad continuity of <a href="http://www.mooreslaw.org/">Moore’s Law</a> on storage and compute. Third, knowledge that was once the exclusive preserve of academic computer science is now spreading to the wider IT Ops community.</p><p>What may be the only remaining barrier to pervasive use of AIOps? Resistance by IT professionals!</p><p>We’re only human. People tend to be suspicious of new ML approaches because they don’t understand them. The topic <em>is</em> certainly complex. It’s easier for people to wrap their heads around <a href="https://www.techopedia.com/definition/579/boolean-logic">Boolean logic</a>, which is an old and familiar way of thinking. Their comfort zone is stretched when you talk about neural networks, similarity as a range not a Boolean, back propagation, high-level calculus, category theory, homology and probability — all advanced, mathematical terms unfamiliar to many IT professionals.</p><h3>AIOps Brings a Future of Change and Hope</h3><p>Despite these issues, there’s great hope for AIOps because it is a small part of what I call <em>Industrial Revolution 2.0</em> — which encapsulates all of the innovations springing from AI/ML. The first Industrial Revolution lifted people from a life of misery, hunger and poverty. In Revolution 2.0, people will see positive albeit unpredictable improvements in their work and life.</p><p>The Revolution of the 19th Century produced then unpredictable social innovations that permanently changed society. Technology inventions included textile manufacture, iron production, steam power, machine tools, chemicals, cement, gas lighting, glass making, paper machine, agriculture, mining and transportation. Social effects included the factory system, improved standards of living, clothing and consumer goods, urbanization, better life for women and families, and safer labor conditions.</p><p>Powered by AI/ML, Revolution 2.0 will also change our lives. I am optimistic these changes will be positive. For example, if you are an IT Operations professional, consider your current work life. Frankly, the rules-based world mostly provides workflow that is mental drudgery: menial, repetitive, and low-pay. AI/ML will automate that miserable life and provide the opportunity for IT professionals to up-level the application of their knowledge in a more productive and enjoyable fashion.</p><p>We cannot ignore the <a href="https://www.forbes.com/sites/nicolemartin1/2019/02/27/what-ai-means-for-your-job-in-the-next-recession/#298916b667c9">massive changes</a> that AI will bring to job roles and career opportunities. The <a href="http://www3.weforum.org/docs/WEF_Future_of_Jobs_2018.pdf">World Economic Forum</a> predicts the use of AI will cause 75 million jobs to be displaced by 2022. However, 133 million new ones will be created — a net increase of 58 million. With this change is the requirement that today’s workers “reskill” for these new opportunities. The 2018 study projects that “no less than 54 percent of all employees will require significant re-skilling and upskilling.” If you work in IT, it is very important to begin planning for this change NOW.</p><p>Moogsoft has <a href="https://www.moogsoft.com/customers/">many large enterprise customers</a> that are already reaping huge benefits from AIOps. Our new approach is enabling them to accelerate mean-time-to-resolution of operational incidents, improve service assurance for customers, simplify the management of cloud infrastructure, and more effectively manage digital transformation initiatives.</p><p>It’s time for IT Operations to move beyond the antiquity of rules-based legacy solutions and put the modern machine-learning of AIOps to work. It is a better approach for delivering continuous service assurance to the enterprise.</p><p><strong>Read the previous blog in this series: </strong><a href="https://www.moogsoft.com/blog/aiops/the-undecidable-challenge-of-rules"><strong>The Undecidable Challenge of Rules</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b26b9d40e11" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/aiops-liberates-it-beyond-the-antiquity-of-rules-1b26b9d40e11">AIOps Liberates IT beyond the Antiquity of Rules</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AIOps for AWS CloudWatch]]></title>
            <link>https://medium.com/moogsoft/aiops-for-aws-cloudwatch-7a1fd68a5802?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a1fd68a5802</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aiops]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Fri, 15 Mar 2019 17:44:05 GMT</pubDate>
            <atom:updated>2019-03-15T17:44:05.493Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: <a href="https://www.moogsoft.com/author/itai-david-njanji/">Itai Njanji</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6k9W5kO9D99jPtchbDqsbQ.jpeg" /></figure><p>Customers migrating workloads to Amazon Web Services (AWS) can choose from an almost infinite variety of tools to monitor their infrastructure. All of these monitoring tools generate valuable insights from events and alarms from services such as Amazon CloudWatch and AWS Config. Customers can further drive more insights by applying machine learning techniques to this data. By using advanced machine learning techniques, customers can reduce operational incidents and increase their service quality.</p><h3>When Traditional Ops Fail</h3><p>Modern applications that are being re-platformed or re-architected on AWS require modern techniques to operate them. Traditionally, hiring support teams was directly proportional to the number of tickets generated (more or less). This outdated approach does not scale well with the distributed nature of the cloud and the rate of innovation which cloud computing enables. Simply put, the number of incidents occurring in AWS CloudWatch, as well as in all of the other tools that are already in use, can be very hard to predict, making the number of expected incidents a much less dependable metric for hiring and planning in IT Operations.</p><p>One traditional approach to managing the number of tickets is extensive manual curation of alarms. For instance, one common practice is to kill some alarms that users do not expect to need to receive on a regular ongoing basis. In this case, the risk is that important and rare alerts or insights might be missed because the condition in which they occur is unexpected. The machine learning techniques which are being gathered under the umbrella of Artificial Intelligence for IT Operations, or AIOps, can provide a new way to think about reducing the number of tickets and providing remediation advice to busy operators.</p><p>Automating anomaly detection in this way helps operations management teams separate signal from noise, surfacing significant events together with all of the context required to accelerate root cause analysis and incident resolution. Combining CloudWatch logs and metric data from existing monitoring tools and custom metrics developed in-house gives operation teams full visibility into the true extent of technical issues and their business impact. By analysing very large volumes of data, early warnings of incidents will be detected and routed to the right specialists, avoiding incidents and minimizing impact to end users.</p><h3>What Happens to ITIL?</h3><p>A question that often comes up at this point is, what happens to ITIL when AIOps is incorporated into wider IT Operations processes? There is no simple answer to this question, as customers implement ITIL differently. Generally speaking, AWS CloudWatch customers have found that utilizing AIOps will improve the quality of their tickets, making them more actionable, which in turns improves their ITIL processes — and users’ satisfaction with those processes. For example, a reduction in the volume of tickets means service desk members have more time to diagnose issues with AIOps insights, helping them achieve lower MTTR (Mean Time to Resolution). The time freed up can then be dedicated to more strategic work such as ITSM hygiene — perhaps making sure that the CMDB is up to date, or performing analysis of recurring issues and best practices.</p><h3>What About DevOps?</h3><p>IT is no longer just about Operations. New technical architectures and development methodologies are coming together to blur the distinction between the previously separate roles of Development and Ops, commonly called DevOps. AIOps helps teams working according to DevOps methodologies to deliver continuous service assurance as they accelerate their digital transformation drives.</p><p>The key ways in which AIOps can enhance DevOps and increase the return on companies’ investments are as follows:</p><ul><li><strong>Increasing CI/CD frequency</strong>: continuous assurance without the need for time-consuming, manual changes to infrastructure or extensive and intrusive instrumentation of applications</li><li><strong>Improving service quality</strong>: automated early detection and diagnosis of issues ensures uptime and mitigates impact to the business</li><li><strong>Reducing ticket volume:</strong> issues that require manual handling can be reduced by 40 percent on average, engaging the right teams automatically, and so reducing escalations</li></ul><h3>How Do I Start?</h3><p>Operations leaders have to balance building their Operations Data Science capabilities and keeping the lights on for their end users. Moogsoft AIOps offers AWS CloudWatch customers an easy path to full operational AIOps capability, thanks to its <a href="https://www.businesswire.com/news/home/20180913005121/en/Moogsoft-Achieves-Amazon-Web-Services-Cloud-Management">Cloud Management Tools Competency certification</a>. Integration between <a href="https://www.moogsoft.com/blog/aiops/moogsoft-aiops-aws-cloud-formation">Moogsoft AIOps and other AWS tools such as CloudFormation</a> helps to deliver a complete ML-enabled IT Ops toolchain to AWS customers, ensuring continuous assurance of applications and services. <a href="https://aws.amazon.com/marketplace/seller-profile?id=cc4e14db-a1c9-4406-be89-112f76042f04">Moogsoft AIOps is available directly from the AWS marketplace</a> for customers to evaluate and purchase.</p><p>Read More:</p><ul><li><a href="https://www.moogsoft.com/blog/aiops/moogsoft-aiops-aws-cloud-formation">How Moogsoft AIOps and AWS CloudFormation together enable cloud migration</a> (blog)</li><li><a href="https://www.moogsoft.com/resources/aiops/case-study/godaddy-migrates-aws/">GoDaddy migrates to AWS with Moogsoft</a> (case study)</li><li><a href="https://www.moogsoft.com/resources/aiops/webinar/symposium-aws">Warp Speed Cloud Migration Powered by AI</a> by AWS Global Operational Intelligence (video)</li></ul><p><em>Disclaimer: This post is my own opinion, and not the opinion of Amazon Web Services or any organization I am associated to professionally. The goal of the article is to trigger intellectual and thought leadership ideas.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a1fd68a5802" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/aiops-for-aws-cloudwatch-7a1fd68a5802">AIOps for AWS CloudWatch</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Actually Reduce IT Costs]]></title>
            <link>https://medium.com/moogsoft/how-to-actually-reduce-it-costs-80816f324dd8?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/80816f324dd8</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[incident-management]]></category>
            <category><![CDATA[aiops]]></category>
            <category><![CDATA[it-cost]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Thu, 07 Mar 2019 18:29:31 GMT</pubDate>
            <atom:updated>2019-03-07T18:29:31.112Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: <a href="https://www.moogsoft.com/author/dominicwellington/">Dominic Wellington</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YV_NGM4gCSwwFUdulhwsBw.jpeg" /></figure><p>It is a truism to say that most decisions in business are driven by financial concerns. The value of the business is determined by that margin between the cost of doing business and the value that customers will pay. In turn, businesses invest to improve that margin: to serve more customers better, to offer them new services, and to do so sustainably.</p><p>IT is no different. Despite being a fairly high-profile function, investments in IT still need to satisfy the same cost / benefit calculations as in every other aspect of the business.</p><p>In the early stages of discussing a potential AIOps project, I always try to understand what the person sitting across the table is actually trying to achieve. When I ask why they are planning to deploy AIOps, their first answer in invariably to reduce cost — specifically, the cost of operating IT services.</p><p>Cost reduction is a valid goal. If we make IT cheaper, we can do more of it and do it better. We can give end users and the business more of what they need. However, there are alternative ways to articulate our primary objective, however, and these each have radically different outcomes.</p><p>A few examples of AIOps drivers include:</p><ol><li>Avoiding critical IT incidents</li><li>Keeping IT operations humming</li><li>Supporting business growth</li></ol><p>Let’s examine each of these.</p><h3>1. Avoiding Critical IT Incidents</h3><p>Businesses are utterly reliant on IT, and any disruption to IT services will also have huge impact on the business. Try visiting any office when the power is out or the internet is down. Even in organizations that still produce a lot of paperwork, all of those printers are still reliant on distant servers and the networks that connect them.</p><p>Consequently, the cost of a major IT incident can be massive. Moogsoft co-founder Mike Silvey tells a story about <a href="https://siliconangle.com/2019/01/07/aiops-is-bigger-boat-to-hunt-jaws-lurking-in-modern-it-reinvent-startupoftheweek/">how Moogsoft AIOps averted an outage at a major airline</a>:</p><p>Last year, an American airline suffered a six-hour outage. Its ground-handling software failed, and it could not schedule a single flight for that period. This year they have Moogsoft. Our software detected an incident that they could act on earlier, and then resolved before it impacted their ground-handling system. Detecting that previously unknown situation prevented an outage of flights across the U.S. that would have lasted a minimum of 4.5 hours.</p><p>It’s worth remembering that any projected impact is probably still a conservative estimate, as it does not attempt to quantify the long-term brand impact. People often prove unwilling to become or remain customers of a brand or business that they perceive as unreliable.</p><p>Avoiding even ONE major incident like the kind the airline suffered can therefore pay dividends. Enough to pay for quite a lot of AIOps software (shameless plug alert!)</p><h3>2. Keeping IT Operations Humming</h3><p>Even absent major incidents, it’s still not cheap to run IT Operations at a major enterprise. Ever since there have been computers, there has been a drive to automate and standardize IT work in order to reduce running costs. Do some of these past automation drives sound familiar?</p><p>“It takes a long time to install a physical server from scratch, so let’s figure out a way to boot from the network instead, pulling standardised images from a central location.”</p><p>“Say, what if we virtualized the entire server and spun it up only when the application needs it?”</p><p>“Even better, let’s architect applications to be as independent from the underlying compute infrastructure as possible.”</p><p>Despite all of this progress, there’s still the need for a room of people staring at screens, watching for something to turn red or a system to do something anomalous. All of those people and computers and networks and virtual servers cost money. Being able to reduce all of these associated costs — without causing any IT incidents, of course — would be a big win.</p><h3>3. Supporting Business Growth</h3><p>IT is always ready to fight the last war. We are forever prepared to prevent a recurrence of the last incident. What IT is not always so well prepared for is <em>change</em>. The marketing department launches a new advertising campaign and enjoys a 50 percent increase in website traffic — but ooops, we forgot to tell IT! That sort of event can be a minor annoyance or a complete catastrophe, depending on how prepared the IT team and its systems are for unforeseen curveballs coming their way.</p><h3>IT Cost as a Metric, Not a Goal</h3><p>Here’s the key point to bear in mind. Cost reduction is the main driver in precisely <em>none</em> of the three key AIOps scenarios outlined. The actual objectives are stability, efficiency, and agility. Cost is relegated to a critically important metric, that is, a way to measure the achievement of these objectives but not the goal in and of itself.</p><p>That being said, it is vitally important to <em>have</em> a metric, i.e. a way to measure what is to be achieved by any AIOps project, and whether that goal has been reached. But it is also key not to confuse the goal with the metric.</p><p>Why? Because some of these goals are going to be difficult to quantify. Others may lead to short-term decisions that do not adequately consider the long-term results and impacts.</p><h3>Why Tracking IT Cost Reduction Is Not So Easy</h3><p>Incident avoidance is one obvious AIOps use case. But how do we quantify incidents that never occur? What if the incident we thought avoided was never going to happen anyway? It’s very rare to see a clear-cut situation where an incident was absolutely going to occur. The best that we can normally say is that, based on prior experience, the probability that an incident would have occurred is high. Correctly apportioning the blame and praise for its occurrence (or its lack thereof) is liable to be a fraught exercise.</p><p>Tracking the daily cost of IT Operations would seem to offer a better chance of accurate “before and after” comparisons. The difficulty here is more a human one, however. The main way to reduce routine running costs is to take people out of the system. Don’t know about you, but I wouldn’t sleep particularly well at night knowing I got a bunch of people fired. Luckily, that rarely happens. In many countries, labor laws prevent companies from eliminating people’s jobs in a hurry. As a European, I’m generally in favor of this idea! However, it does make it difficult to point to a substantial savings in salaries as justification for an AIOps investment. Moving people to other departments (and their associated cost centers) is harder to recognize as “savings”.</p><p>So it’s better to focus on goals like stability, efficiency, and agility. The idea is to make the IT operations as predictable and invisible as possible, so that business functions that rely on IT support can easily factor it into their own planning.</p><p>One unglamorous parallel here is the Facilities department. It is able to provide whatever physical building services are required for all employees, given some fairly minimal high-level requirements. The Facilities team is not expected to go with lowest cost bidders every time. No one expects them to mix their own cement or lay their own carpet. Depending on the physical plant requirements, a variety of different approaches may be appropriate, as long as they satisfy their ultimate goals. IT Operations should operate in the same way.</p><p>For almost every enterprise out there, IT is no longer a daring cutting-edge innovation, but routine table stakes. Everyone has IT, so the competition has moved up to the next level. Namely, whoever can operate their IT systems better, wins. This mean ensuring that they are stable, efficient, and able to react with agility to whatever may be required.</p><h3>Putting the Emphasis on “Ops” in AIOps</h3><p>As a field, AIOps is pretty cutting edge. The “<a href="https://www.moogsoft.com/blog/aiops/what-is-ai">AI</a>” part is the giveaway there. It’s true that there’s a lot of overheated hype around these two little letters, causing some justified scepticism. However, there is <a href="https://www.moogsoft.com/resources/aiops/white-paper/moogsoft-observe-incident-detection">some very interesting work</a> being done on Moogsoft algorithms. Specifically, the Moogsoft AIOps Platform’s ability to sift faint signals from enormous amounts of IT operational noise, identify correlations between seemingly disconnected events, and assemble cross-disciplinary teams to respond to identified IT incidents.</p><p>However, all of this is in service of the fairly prosaic goals of continuous assurance of IT operations, which have not changed much since the dawn of computing. Namely, to keep everything running, to avoid outages, and to not spend too much doing it!</p><p>AIOps projects are only worth getting into if they satisfy one or more of the basic business needs of stability, efficiency, and agility. Cost is a good way to measure the size and success of an AIOps project, but it’s only one metric. Don’t let that obscure the actual, higher goals that you are supposed to be working toward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80816f324dd8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/how-to-actually-reduce-it-costs-80816f324dd8">How To Actually Reduce IT Costs</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Undecidable Challenge of Rules]]></title>
            <link>https://medium.com/moogsoft/the-undecidable-challenge-of-rules-b80fe9c8f386?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b80fe9c8f386</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[it-operations]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aiops]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Tue, 26 Feb 2019 18:25:10 GMT</pubDate>
            <atom:updated>2019-02-26T18:25:10.544Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: <a href="https://www.moogsoft.com/author/philtee/">Phil Tee</a></p><p><em>This blog is the fourth in the series, “How AIOps Liberates IT from a Rules-based Approach”.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O0wKzEYGnzPGZ9oMfyeONA.jpeg" /></figure><h3>Summary</h3><p><em>1. Rules-based solutions cannot guarantee to fully determine or decide the root cause of a system failure.</em></p><p><em>2. The random circumstances of real-world failures often confuse undecidable rules and delay remediation.</em></p><p><em>3. Unlike a rules-based system, AIOps teaches itself without having to account in advance for every input and output.</em></p><p>We all nod to the maxim’s wisdom, “If your only tool is a hammer, then every problem looks like a nail.” Yet for many IT operations centers, the primary (if not only) tool for ensuring stability and performance is a rules-based service assurance system. Perhaps, in a simpler world, this was enough to do the job. But with the explosion of microservices-based virtual IT in a potpourri of cloud environments, it’s worth asking if that approach is wise. Especially when the problems trying to be solved by rules are <em>undecidable</em>.</p><h3>Why Rules Are Undecidable</h3><p>The approach of rules assumes that with enough time and effort, you can eventually find a solution. The goal is to identify the fix you need that will bring a service back on line. Presuming the right set of rules and inputs, you can always predict the correct outcome by identifying the correct underlying cause. However, for complex problems, such as predicting performance of enterprise IT systems, rules fall short. These problems are difficult or impossible to solve with rules.</p><p>From a logical perspective, we say these rules are <a href="https://en.wikipedia.org/wiki/Undecidable_problem">undecidable</a>. In computational theory, an undecidable problem is a decision problem for which it is impossible to construct an algorithm that always leads to a correct yes-or-no answer.</p><p>To illustrate, a common and important use case for enterprise IT infrastructure monitoring is known as downstream suppression; it involves a dependency relationship. Consider a simple network with 100 servers. A rules-based monitoring system pings each one to determine if they are alive. A rule states: if a ping is negative, then that server is down.</p><p>Ambiguity for rules arises for servers connected by a switch that fails. Monitoring for those servers triggers phantom pings, so that particular rule provides inaccurate information for remediation. You need another rule to ping switches in the network to distinguish what is really down. This scenario shows why simple rules quickly grow into complex rule sets in order to account for all potential variations of related infrastructure.</p><p>But what happens if the switch and servers are all in a data center that loses power? A rules-based solution has no way to distinguish between phantom and real failure. The scenario is ambiguous — it’s <em>undecidable</em> because rules cannot work out the most likely cause. IT operators must get information from another source to determine the real problem. This is a very simple illustration, but it captures the fundamental problem: rules cannot guarantee to fully determine or <em>decide</em> the root cause.</p><h3>Rules Make Real-World Failures Especially Undecidable</h3><p>The simple scenario gets worse in a big enterprise with thousands of servers, tens of thousands of apps, and millions of virtual circuits — all of which have dependencies on the others. Any of those elements can generate an error. In a rules-based system, there are loads of those un-decidable scenarios.</p><p>We saw one occur this month when Wells Fargo Bank’s mobile app and web site became <a href="https://www.americanbanker.com/news/wells-fargo-glitch-causes-widespread-outage-leaves-customers-fuming">unusable by customers</a>. On February 7, a data center outage in Minnesota killed mobile app and web site usage for the bank’s U.S. customers with fallout continuing into the next day. Customers also reported being unable to use Wells Fargo credit and debit cards as well as company ATMs.</p><p>This outage is germane because it illustrates the <a href="https://www.datacenterknowledge.com/uptime/update-2-data-center-outage-disrupts-wells-fargo-atms-mobile-app-website">cascading consequences</a> of a rules-based solution (presumably IBM Netcool Network Management) being confused at determining root cause of an event. The bank’s undecidable disaster started with detecting smoke in the data center, apparently started by routine maintenance. It’s unclear if smoke was actually present. Then power was automatically shut down. Failover was supposed to occur, but took unusually long for undisclosed reasons. The result was national outrage by affected customers.</p><p>Dependencies in Wells Fargo Bank’s scenario did not all occur at a fix-in-time event. What was true when the smoke occurred (or a smoke detector malfunctioned) was not true when power shut down. Logic was required to change, as a vast multitude of dependent systems became affected. Just for users to log into the online banking system, required elements that were affected included applications, databases and systems for authentication, authorization, DNS, lots of hardware, and a huge amount of interconnectivity and interdependency. These varying dependencies triggered delays in remediation, and the bank <a href="https://newsroom.wf.com/press-release/corporate-and-financial/wells-fargo-provides-update-restoring-services-customers-0">acknowledged</a> intermittent recurrences of fallout.</p><h3>AIOps Provides More Insight for Correct Decisions</h3><p>The lesson from Wells Fargo Bank’s outage is a rules-based system is not enough to keep IT systems running. IT operations staff need additional visibility, external information, an understanding of probability and likelihood of underpinning failures, and the most common path to what caused a given type of alert.</p><p>Ironically, IT people know about this. Those with rules-based systems are awash in symptomatic alerts that don’t mean anything. For IT Ops, it’s the Grand Operational Challenge. Too many organizations ignore this problem and hope it will go away; meanwhile they endure poor quality of service. Others continue to commit the definition of insanity by doing the same thing over and over, expecting a different result. They triage different rules-based solutions in a hopeless effort.</p><p>The visionaries are pushing beyond legacy solutions with <a href="https://www.moogsoft.com/">AIOps</a>. Instead of grappling with undecidable problems, AIOps steps around the quicksand of baked-in cause ambiguity.</p><p>AIOps is independent of the rigid, brittle logic of rules. Instead of forcing IT Ops professionals to manually piece together data that falls outside the limited scope of rules, an AIOps system can ingest <em>all</em> the operational data in your enterprise and automatically apply algorithms to determine which events matter and which do not. Unlike a rules-based system, AIOps teaches itself without having to account in advance for every input and output.</p><p>If your organization relies on rules to solve undecidable problems that underpin performance of the company’s heartbeat — namely its IT systems and applications — now is the time to evaluate the wisdom of that path. As the victims have learned in our recent example, having the wrong tool for the real problem is a fool’s errand with nasty results.</p><p><strong>Read the previous blog in this series:</strong><a href="https://www.moogsoft.com/blog/aiops/the-teeny-tiny-scope-of-rules"><strong> The Teeny-Tiny Scope of Rules</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b80fe9c8f386" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/the-undecidable-challenge-of-rules-b80fe9c8f386">The Undecidable Challenge of Rules</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Teeny-Tiny Scope of Rules]]></title>
            <link>https://medium.com/moogsoft/the-teeny-tiny-scope-of-rules-39cf39465959?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/39cf39465959</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[rules]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aiops]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Tue, 19 Feb 2019 17:20:01 GMT</pubDate>
            <atom:updated>2019-02-19T17:20:01.207Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: <a href="https://www.moogsoft.com/author/philtee/">Phil Tee</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*843iRhGN-RaPASLwPnck8A.jpeg" /></figure><p><em>This blog is the third in the series, “How AIOps Liberates IT from a Rules-based Approach”.</em></p><h3>Summary</h3><p><em>1. Rules have predictable results in simple environments</em></p><p><em>2. Rules results are unpredictable in complex environments</em></p><p><em>3. </em>The scope of rules guarantees they will not work in large IT environments</p><p><em>4. AIOps avoids the limits of rule scope for accurate predictions of emergent behavior</em></p><p>Accurate prediction of future events and behavior is the object of <a href="https://www.moogsoft.com/blog/aiops/how-brittle-rules-frustrate-it-operations/">using rules to manage IT operations</a>. Teams lean heavily on the assumption of accuracy. It’s why organizations with a rules-based approach make big commitments to a continuous process of adding new rules, refining old ones, and evaluating outcomes. But there’s a fundamental gating factor for accuracy that remains forever impervious to constant tweaking: the teeny-tiny <em>scope</em> of rules.</p><p>In this context, scope is the potential range of IT scenarios that may affect system performance. The scope issue is like a pervasive dark cloud that shades accuracy of rules-based predictions. To understand why, consider an analogy that irritates virtually everyone who commutes to work daily.</p><h3>What Commuting Teaches Us About Scope</h3><p>The mission of a metro commute is simple: get to work safely and on time. With minor variations, the process consists of a few simple actions. Get in the car. Start the engine. Check Google Maps for accidents and congestion. Drive the car and avoid hitting hard things. Grab a coffee if there’s time. And finally slip into your desk chair before the boss notices you’re slightly late.</p><p>Decision logic for commuting is straightforward because there is one driver, a simple two-dimensional road system, a finite number of routes between points A and B, and set rules for driving. Despite this simplicity, everyone complains that traffic keeps getting worse. Frustration abounds because unpredictable traffic clogs your efficient transit even when Google shows the route as “green.”</p><p>None of this frustration would exist if the only driver were you. But a metropolitan area is a large, complex system where the random actions of hundreds of thousands or millions of independent decision-making units (i.e. commuters) produce unpredictable results. If you’re lucky, the result will simply make you late. All bets are off if your car hits something hard.</p><p>The intrinsic unpredictability of the commute decision problem is a classic example of what is described mathematically as <a href="https://en.wikipedia.org/wiki/NP_(complexity)">NP-complete</a>. Math experts define this as computational complexity so bad that no matter how large the computer you can quickly scale a problem past the ability to work out an answer. For example, if you can solve the commuter problem for 10 cars using your laptop, 100 cars would take all of the available compute power on planet earth. You can certainly see that the <em>scope</em> of this commute scenario is too big for a rules-based approach.</p><h3>Limitations of Rule Scope for IT Operations</h3><p>For IT Ops, a direct analog to the commute decision problem is the rules used to identify issues that may affect system performance. An individual rule is like the driver in a car. It’s simple and easy to say, “If I get alert X or Y, then the outcome will be Z.” Conclusive, highly predictable results are always available when the scope of operational variables is small (akin to your commute occurring on empty roads).</p><p>Enterprise networks are anything but empty. Depending on size and type of business activity, an enterprise network can easily generate millions or billions of event triggers every day. The complexity and potential combination of events generated by this scale of activity dwarfs the decision problem illustrated by metro commuting.</p><p>Using rules to manage IT Ops is problematic because you need a separate rule to address each scenario, all of the rules must work together, and the outcome of one rule often depends upon the outcome of many others. With a rules-based approach, you must verify all of that for every scenario to ensure accurate predictions. Otherwise, the only guarantee is results that are unpredictable.</p><p>In the simpler example of metro commuting, calculating all the potential results decided by <a href="http://www.laalmanac.com/employment/em22.php">4.4 million commuters in Los Angeles</a> would be impossible with today’s technology and knowledge of mathematics. It may take a few decades before those catch up.</p><p>Doing the same for rules-based IT Ops has the same problem. Both are NP-complete problems. With rules, scope is limited so there is no way to ever know if all their specific results are accurate. Hence the peril of using rules to guarantee IT service delivery.</p><h3>AIOps Avoids Limits of Rule Scope</h3><p>Using artificial intelligence for IT Ops instead of a rules-based approach avoids the constraining limits of scope. <a href="https://www.moogsoft.com/product/">AIOps</a> allows enterprise teams to eliminate the responsibility of creating rules for every possible combination of events. Using AI and machine learning allows your monitoring system to ingest <em>all </em>the operational data in your enterprise and automatically apply algorithms to determine which events matter and which ones do not. Unlike a rules-based approach, AIOps teaches itself without having to account in advance for every input and output.</p><p>The result of using AIOps is greater accuracy in detecting and predicting events that can hamper system performance — and allow teams to keep IT Operations working at peak efficiency. The unique capability of AIOps to treat data as a whole also enables detection of emergent behavior. This is a big problem that cannot be solved with a legacy rules-based tool shackled by a teeny-tiny capability of scope. And as with the mission of metro commuting, AIOps provides a safer path to prevent IT systems from hitting something hard.</p><p><strong>Read the previous blog in this series: </strong><a href="https://www.moogsoft.com/blog/aiops/understanding-the-true-cost-of-rules"><strong>Understanding the True Cost of Rules</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39cf39465959" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/the-teeny-tiny-scope-of-rules-39cf39465959">The Teeny-Tiny Scope of Rules</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making AIOps Intuitive at Cisco Live EMEA]]></title>
            <link>https://medium.com/moogsoft/making-aiops-intuitive-at-cisco-live-emea-7cfee87324f5?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cfee87324f5</guid>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[aiops]]></category>
            <category><![CDATA[application]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Thu, 14 Feb 2019 20:43:46 GMT</pubDate>
            <atom:updated>2019-02-14T20:43:46.630Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: <a href="https://www.moogsoft.com/author/dominicwellington/">Dominic Wellington</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dc7tgOz4I6BJVSSyYPwZrQ.jpeg" /></figure><p><a href="https://newsroom.cisco.com/feature-content?type=webcontent&amp;articleId=1965043">Cisco Live EMEA in Barcelona</a> was held on the last week of January. It’s always a great show to take the pulse of the industry. While the show used to be very much about networking concerns, these days there is a much broader base of attendees and topics under discussion. Of course in recent years many of the same trends have affected the previously separate domains of computer and network, most notably virtualization and the move to software-defined architectures, so there are many more common topics for the two groups to discuss.</p><p>To underline the overall move away from a purely network-centric event, much of the keynote address was actually focused on enterprise data center concerns. Ultimately, three main trends emerged which were also featured topics of the show.</p><h3>Enterprise Expansion to the Cloud</h3><p>This is perhaps the most obvious of the three trends, but one aspect worth pointing out is that we are talking about <em>expansion </em>to the cloud, not the wholesale <em>move </em>to the cloud that some of the more excitable projections from a few years ago predicted. New startups can operate their business on a wholly cloud-native infrastructure — including Moogsoft, full disclosure. The only actual physical hardware that <a href="https://www.moogsoft.com/">Moogsoft </a>owns is a bunch of MacBooks covered in cow stickers (mooooo!) However most larger enterprises either already owned a data center or found themselves in a position where it made sense to start one. These enterprises are still taking advantage of the cloud, but as an expansion or extension of their existing efforts.</p><p>The reasoning behind operating both environments side by side in this way is stability. If something ain’t broke, don’t fix it. Meanwhile, build <em>new</em> things with state-of-the-art tools. Yet the unintended result is unavoidable complexity. New tools and processes are required that understand both worlds. Attempts to treat the ephemeral, fast-changing world of the cloud the same way as the rigid, predictable world of the in-house data center is a recipe for disaster, at worst. At best, it’s guaranteed to miss out on most of the benefits of these new technologies.</p><h3>Applications Anywhere</h3><p>One session track was subtitled “any information, any device, any time”, which is a great way to describe end users’ expectations. To take one obvious example, I booked my travel to Barcelona on my laptop, trusting implicitly that the relevant information would show up wherever I needed it, whenever I needed it. The boarding passes showed up on my phone. The time blocks showed up on my shared calendar so everyone knows when I’m flying. The airline’s backend systems that do all this scheduling so I’m confident they’re expecting me. All this travel data is seamlessly distributed, not only to my own devices but also via web services to any number of people: work colleagues who need to know when I’m available, family who need to know when I’ll be home, and so on.</p><p>This is a substantially different set of expectations than even one generation ago. The traveler would have to go to specific physical locations to sign on to particular services or access specific data. Think the travel agent, the ticket counter, the office workstation. Problems arise when outdated assumptions don’t match the new reality — notably, that these systems can no longer be operated in isolation. When a fault arises in the modern, interconnected, amorphous service cloud, it isn’t always quick and easy to determine whether an alert is the cause — or the symptom of a larger problem in some entirely different system. The second trend is that IT operations teams need to map their response procedures to this “anywhere, any time” world.</p><h3>Complexity &amp; Change</h3><p>These first two trends culminate in new challenges for IT in the enterprise: mainly the complexity of these new technical architectures and the accelerating rate of change. Increasing complexity and accelerating change are both driven by technological evolution and higher user expectations. A holistic response is required to address all of these challenges — right from the initial architectural design straight through to long-term production operations.</p><p>Cisco Live speakers made some very interesting points about IT architectures being reinvented to be <em>intent-based</em>. Previously a small number of tasks were defined, and an architecture was constructed to enable those discrete tasks — and to implicitly exclude others. Requests from users to enable new actions required significant effort. Today’s systems are architected to enable fluid changes, directly at the intersection of users, devices, data, and apps. Systems and their relationships are no longer static but rather constantly changing, and mostly through automated actions in response to detected situations. No more manual changes by human engineers.</p><h3>New Operational Models</h3><p>New fluid architectures require new operational models. As they are intrinsically dynamic and changeable in the extreme, it is increasingly evident that static models of systems and the engineers responsible for them are no longer fit for purpose.</p><p>This search for new operational models drove intense interest in Moogsoft AIOps all week. Besides our own exhibit, traffic jammed at our demo pod in the Cisco area, where Moogsoft technology integrated with Cisco Network Services Orchestrator (NSO) and Netrounds was being showcased by Cisco engineers. The algorithmic and collaborative approach behind AIOps — and its Cisco-branded manifestation, <a href="https://blogs.cisco.com/sp/cisco-crosswork-part-3-situation-manager">Crosswork Situation Manager</a> — is the only way to understand what requires attention and who needs to work on quick resolution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/919/0*4thBmQc-VvCRbViI.png" /></figure><h3>“Imagine Intuitive”</h3><p>What was particularly gratifying throughout the week was the stream of people exposed to this new way of working by one of Moogsoft’s partners. Managed service providers using Moogsoft AIOps have begun inviting engineers from end user customers into our collaborative <a href="https://www.moogsoft.com/product/collaboration-workflow/">Situation Room</a>. That’s where all parties involved in a particular issue meet to accelerate resolution times (while minimizing unproductive finger-pointing). After a few choice situations where they directly experienced the power of our approach, those suppliers are now interested in adopting Moogsoft for themselves.</p><p>This really validated Cisco Live’s show theme, <em>Imagine Intuitive</em>. Instead of forcing users to conform to how IT systems are designed, let’s instead design solutions that support and enable users to get the job done.</p><p>If you are interested in finding out more about AIOps and what it means for IT Operations, a great starting point would be <a href="https://www.moogsoft.com/resources/aiops/webinar/aiops-the-next-five-years">this recorded webinar</a> about the potential of this new approach.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cfee87324f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/making-aiops-intuitive-at-cisco-live-emea-7cfee87324f5">Making AIOps Intuitive at Cisco Live EMEA</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Brittle Rules Frustrate IT Operations]]></title>
            <link>https://medium.com/moogsoft/how-brittle-rules-frustrate-it-operations-c6b52dcd14b0?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6b52dcd14b0</guid>
            <category><![CDATA[aiops]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[it-operations]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 21:26:43 GMT</pubDate>
            <atom:updated>2019-02-07T21:26:43.337Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: <a href="https://www.moogsoft.com/author/philtee/">Phil Tee</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lzYlduz_Y9Xh0HcfNBT9MQ.jpeg" /></figure><p><em>This blog is the first in the series, “How AIOps Liberates IT from a Rules-based Approach“.</em></p><h3>Summary</h3><p><em>1. Rules have illusion of simplicity</em></p><p><em>2. Rules bring exponential complexity</em></p><p><em>3. Rules do not address unpredictable events</em></p><p><em>4. AIOps solves these issues</em></p><p>Rules have governed IT operations monitoring and remediation for decades. Those of you who are seasoned IT Ops professionals probably see a rules-based approach as an old familiar friend. As alerts flow into a traditional monitoring tool, the simple logic of “<em>If</em> this condition exists, <em>then</em> do that” addresses each issue with reliable execution and results.</p><p>Or does it? Do rules always behave the way we assume they do?</p><p>The question posed is serious for it challenges the fundamental assumption of rules-based predictability. Let’s peek under the hood of a rules-based approach to IT Ops and consider how rules are becoming brittle, weak and ineffective against the enormous rising tide of operational data in a modern IT infrastructure.</p><h3>Illusion of Simplicity</h3><p>A rule looks like it what it says. It consists of a fixed input and a fixed output. A set of associated rules attempts to address a black-and-white situation without leaving ambiguous, “I’m not sure what to do next” advice. Yet what appears to be straightforward is not always the case. The cause for hesitation is an unpredictable universe of exceptions that <em>always occurs</em> in IT Ops.</p><p>The tiniest exception to a rule is a deviation from what that rule was designed for. Exceptions mean the rule’s logic ceases to work. Any result will be 100 percent wrong — until a new rule is created to address the exception.</p><p>An analogy affecting all of us is the tax code. On the surface, a law is something for which you either comply or ignore at risk of penalty. But it’s not quite that simple. As with IT Ops, tax laws have many exceptions (“loopholes”). For example, the <a href="https://en.wikipedia.org/wiki/Tax_Cuts_and_Jobs_Act_of_2017">U.S. Tax Cuts and Jobs Act of 2017</a>contains <a href="https://docs.house.gov/billsthisweek/20171218/CRPT-115HRPT-%20466.pdf">503 pages</a> of new policy. The changes are so big and complex that CPAs are wondering exactly how they may apply in the real world. The U.S. Treasury Dept. is writing rules (regulations) that will answer some of those questions over several years. By then, there will be thousands, possibly tens of thousands of new pages of rules attempting to cover all exceptions to one law.</p><p>For IT Ops, a large modern enterprise is getting tens or hundreds of thousands — even <em>millions</em>– of alerts <em>every day</em>. Trying to comprehensively and effectively address all those alerts with a rules-based approach is quite similar to tax compliance. Gray areas will never disappear with rules.</p><h3>Exponential Complexity</h3><p>Rules are easy to create. And as noted, you will need to create many of them to address exceptions. This is where IT Ops gets tricky for if you double the rule portfolio from one to two, then you have to know if the two rules are 100 percent consistent with each other. Complexity then rises exponentially as you create more rules for the same set.</p><p>Calculating the potential combinations for a rule set is a factorial function, which is the product of all positive integers less than or equal to n (denoted by n!). For example, with five rules, there are 120 possible combinations. With six rules there are 740. Ten rules will generate 3,628,800 potential combinations. And 100 rules may result in nine to the 157thpower — that’s nine followed by 157 zeros.</p><p>Those examples are tiny compared to combination totals for a typical enterprise portfolio of thousands of rules.</p><p>Testing an enterprise portfolio of rules to ensure consistent accuracy is a major issue. Each combination of rules must be verified to ensure avoiding false positive alerts or missing critical incidents. Data scientists call this the “NP Complete” problem because no computer exists that is capable of scaling to this requirement.</p><p>Clearly, to say that using a rules-based system for enterprise IT Ops is “simple” would be a misnomer! It’s virtually impossible to understand the effects of alert exceptions in a collection of rules.</p><h3>Challenged by Unknown Unknowns</h3><p>The classic problem of logical induction arises when you attempt to base IT Ops decisions on results generated by a rules-based tool. To frame this problem, consider the <a href="https://en.wikipedia.org/wiki/Black_swan_theory">Black Swan Theory</a> presented by Nassim Nicholas Taleb in 2007. In applying statistics to trading systems, he addressed the ancient myth that presumed black swans do not exist, which was reinterpreted after black swans were discovered to exist in Australia.</p><p>Taleb’s theory offers two relevant points: (1) hard-to-predict, rare events have a disproportionate role in complex operations; and (2) rules do a poor job at predicting the probability of these events.</p><p>You can see where I’m going with this. A “black swan event” has become a phrase used in data science for things you can’t predict. Such as discovery of potentially crippling, unusual events in IT Ops. And this is precisely why a rules-based scheme for IT Ops will always leave you on very shaky ground — the very place where your SOC team needs as much certainty as possible to take decisive action.</p><h3>Beyond Rules, More Certainty</h3><p>Issues like these are why more large enterprises are turning to data science for clearer insights and more control over IT Ops. With artificial intelligence and machine learning, a SOC team is able to process <em>all</em> IT Ops data in a manner that is tolerant to exceptions without the limitations of rules.</p><p>Analyzing all the data is possible with a simple but very powerful characteristic of AI, as applied by Moogsoft AIOps. We use algorithms to know when something is unusual — think unusual <em>feature</em> of the event, not in a statistically-compared-with-everything-we-have-seen kind of way.</p><p>Moogsoft’s unsupervised algorithms are similar to how our brains work when confronted with a new situation. Imagine I show you two pictures of a field, one with and without an <em>animal</em>. It’s easy to spot the animal, even if you have never seen that <em>particular</em> animal. Your brain simply processes the visual imagery and can recognise that something that moves, and is a correlated portion of the image <em>unlike</em> the background, is likely to be an animal.</p><p>Making a rule replicate this behavior of your brain would require a rule set of detailed descriptions of every type of animal. The rule would also address the exceptions, such as mistaking a car for a black swan. There will also be rules for every possible color for the same type of animal, such as a white swan versus the black ones. Rules are brittle because there is no possible way to satisfy all of these requirements.</p><p>The human brain’s methodology for processing data provides a scalable model for AIOps, which uses very similar algorithms so no training is required. The AIOps algorithms are a sophisticated way of spotting collections of your enterprise’s events that are behaving as a related incident, not just noisy unimportant background.</p><p>AIOps replaces the uncertainty of brittle rules by quickly and effectively finding event patterns that are a priority for SOC teams — even if results are unanticipated surprises that might otherwise disrupt IT operations.</p><p>If your enterprise IT ops relies on brittle monitoring rules, considering a modern data science-based approach will help instill deep, reliable visibility into what your operational data really mean. AIOps is quickly becoming a mandatory shift in approach to help ensure peak performance and integrity of IT operations.</p><p><strong>Read the next blog in this series: </strong><a href="https://www.moogsoft.com/blog/aiops/understanding-the-true-cost-of-rules"><strong>Understanding the True Cost of Rules</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6b52dcd14b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/how-brittle-rules-frustrate-it-operations-c6b52dcd14b0">How Brittle Rules Frustrate IT Operations</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the True Cost of Rules]]></title>
            <link>https://medium.com/moogsoft/understanding-the-true-cost-of-rules-3ab9ecefd0e4?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ab9ecefd0e4</guid>
            <category><![CDATA[rules]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[aiops]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 21:23:24 GMT</pubDate>
            <atom:updated>2019-02-07T21:23:24.477Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: <a href="https://www.moogsoft.com/author/philtee/">Phil Tee</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LheISBI9boGF_wmaMZv-Pw.jpeg" /></figure><p><em>This blog is the second in the series, “How AIOps Liberates IT from a Rules-based Approach”.</em></p><h3>Summary</h3><p><em>1. Rule maintenance is expensive</em></p><p><em>2. Rules have hidden complexity and cost</em></p><p><em>3. Rules can hinder detection and remediation</em></p><p><em>4. AIOps solves these issues</em></p><p>Business is rightfully obsessed with costs. Cost of goods sold. Cost to market and sell goods. Product development costs. Compliance costs. Cost of using employees versus contractors. And so forth. For IT operations, the pressure 24×7 is to ensure the entity avoids costs of sluggish systems or downtime, which impede conducting business and booking revenue.</p><p>But what about the cost of rules? Many organizations rely on legacy monitoring systems that use large sets of rules intended to spot potential issues that would prevent optimal performance. You could say those enterprises live or die based on the rules. It’s worth exploring the cost of rules because an enterprise should know if the cost is too high.</p><h3>Not a Bargain</h3><p>A rule is a simple concept. It states a fixed predictive input and a fixed predictive output. Takes but a moment to jot one down, which sounds inexpensive. Seems like a bargain compared to other processes.</p><p>We know the bargain ends after writing the first rule because it covers just one situation. The endless variation in issues for enterprise IT system performance requires a different rule for each option. Each rule must be checked for consistency against all the other rules in a set. As I described in <a href="https://www.moogsoft.com/blog/aiops/how-brittle-rules-frustrate-it-operations">the first blog in this series</a>, the number of combinations grows exponentially to levels where no computer exists that is capable of scaling to this requirement.</p><p>Understanding the true cost of rules entails the never-ending process of creating, checking, and revising all the rules. This is a habitual maintenance problem of gargantuan size. It’s like painting the Golden Gate Bridge — by the time you finish one pass, you’re late starting a new coat over dangerous ever-recurring rust.</p><p>Rule maintenance requires keen insight on the interactions and nuances of a rule set. The technical knowledge and operational experience needed for effective maintenance is not a skill set possessed by junior SOC staffers. Be prepared to focus your senior (i.e. expensive) SOC experts on this one.</p><p>The severe shortage of experts puts organizations in a double bind because there is no practical or cost effective way to reliably maintain all the rules. The number of rules has exploded with proliferation of modular, distributed application and device virtual instances that pop on and off on demand. When rules don’t work as intended, or when there are conflicts between rules, their accuracy suffers and the SOC becomes inundated by irrelevant alerts. To address alert fatigue, SOC analysts often pull back from using rules for root-cause correlation of events. Well-meaning analysts may even turn rules off, although this action makes them more reactive than proactive to system issues. The result is incurring higher costs of poor availability and downtime.</p><h3>Restricting Rules Provokes Risks</h3><p>The temptation to turn off some rules exists because in a typical operational environment, often less than 10 or 20 percent turn out to be critical. Needless alerts occur especially when SOC analysts over-attribute severity to particular alerts. Often this attribute is hard coded into rules. Trying to deliberately avoid irrelevant alerts may seem efficient on the surface, but the cost will often become onerous.</p><p>Suppose the SOC decides to filter “irrelevant” rules at the source in order to process only critical alerts. The Achilles heel of this strategy is that most severe outages do not start with a critical alert. Instead, the issue usually starts with a low-severity incident. The monitoring tool reveals just the hint of a new problem, and if that hint’s indicator is turned off, the issue will be undetected. By the time an incident turns critical, analysts will never have seen the issue coming. It will be too late.</p><p>Consider a common example that can seriously hamper performance of a microservices-based system. Suppose a Kubernetes DNS error triggers a service failure. This severity is hard-coded into the rule. Perhaps that rule makes sense for the particular microservice. But its failure is not automatically the cause of performance hits to other microservices, which usually are consequential. Automatically elevating severity for a particular event may misdirect SOC responses at an early stage. It’s how binary rules can easily lead you down the wrong path to remediation.</p><p>Rules reward you with hidden complexity and cost. Going in, rules are attractive. They look simple, and naively, proponents will claim rules are far simpler than AI. They look predictable; what is more straightforward than true or false? Indeed, areas of science such as chemistry, genetics and life are based upon very simple physical laws. But while scientific laws are a direct analog of true or false, their scale creates enormous complexity. For a modern enterprise, rules offer a false economy that encourages stepping backward.</p><h3>AIOps Reduces the Cost of Rules</h3><p>The inherent messiness of maintaining rules carries potentially incalculable costs when SOC analysts are unable to detect and remediate issues that hamper performance. The scientific answer to issues posed by a rules-based approach is AIOps — using artificial intelligence and machine learning to solve the problems that rules are supposed to handle (but cannot).</p><p>AIOps eliminates the need to create rules for every possible combination of events. Instead, an AIOps system can ingest <em>all</em> the operational data in your enterprise and automatically apply algorithms to determine which events matter and which do not. Unlike a rules-based system, AIOps teaches itself without having to account in advance for every input and output. Using AIOps is essential for ensuring peak performance of modern systems.</p><p>For more technical background, I invite you to read an academic analysis of how AIOps with machine learning is superior to a rules-based approach in our study, “<a href="https://www.semanticscholar.org/paper/Cookbook%2C-a-recipe-for-fault-localization-Harper-Tee/d7a0516451da3e08ce1dc4908a26b3189add4da4">Cookbook, a Recipe for Fault Localization</a>“ (paywall). It was published in the <em>NOMS 2018 IEEE/IFIP Network Operations and Management Symposium</em>, so IEEE members can <a href="https://ieeexplore.ieee.org/document/8406284">pick it up here</a>.</p><p>Using AIOps eliminates the typical costs associated with rules and does a much better job at ensuring system performance. Some people would call that a “twofer” — and that’s a real bargain!</p><p><strong>Read the first blog in this series: </strong><a href="https://www.moogsoft.com/blog/aiops/how-brittle-rules-frustrate-it-operations"><strong>How Brittle Rules Frustrate IT Operations</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ab9ecefd0e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/understanding-the-true-cost-of-rules-3ab9ecefd0e4">Understanding the True Cost of Rules</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing What’s New In Moogsoft AIOps 7.1]]></title>
            <link>https://medium.com/moogsoft/announcing-whats-new-in-moogsoft-aiops-7-1-916dc08fdae5?source=rss-fe410e3471d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/916dc08fdae5</guid>
            <category><![CDATA[aiops]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Moogsoft AIOps]]></dc:creator>
            <pubDate>Wed, 30 Jan 2019 18:33:17 GMT</pubDate>
            <atom:updated>2019-01-30T18:33:17.480Z</atom:updated>
            <content:encoded><![CDATA[<p>Author: <a href="https://www.moogsoft.com/author/ciaranbyrne/">Ciaran Byrne</a></p><p>Here at Moogsoft, as with modern IT operations at any enterprise, things move pretty quickly. Our mission is all about enabling business agility for our customers in the face of the ever-accelerating rate of change. Our platform assures they can keep up with the demands placed on IT Ops by increasingly dynamic networking environments.</p><p>Our quarterly <a href="https://docs.moogsoft.com/display/AIOR/Moogsoft+AIOps+Releases">Enterprise Stability Release</a> schedule allows us to roll out new features, respond to enhancement requests from users, and provide a stable and predictable environment in production.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jq7r5C-2ECYQ1NwvizNtWg.jpeg" /></figure><p>As part of that process, we are proud to announce the Enterprise Stability Release of Moogsoft AIOps 7.1. Here are the release highlights and resources to help you learn more about our latest features.</p><h3>Visualize</h3><p>Visualize provides transparency about the inner workings of the algorithms, both to aid with understanding and to help guide an administrator through any optimization steps that may be needed.</p><p>For every situation that is generated, if an algorithm was used in the generation of a situation, then additional information is available to provide context. This approach ensures that this information is transparent and can be leveraged for algorithm optimization.</p><p>Because Visualize is an early-access version, it can be enabled via “Labs” in the System Settings UI and requires a specific permission to view.</p><h3>Powerful New Enhancements</h3><p><strong>Algorithm Improvements </strong>— Cookbook is one of our most popular algorithms. There is a configuration option “cook for” which specifies the duration a situation typically takes to unfold, i.e. for all alerts to be captured. With the 7.1 release we have added an auto extension capability as the algorithms are aware that new alerts are still happening within a certain time period. This provides a more flexible configuration and minimizes the chance that duplicate situations will occur.</p><p><strong>Similar Situations API</strong> — Similar Situations is a feature that surfaces patterns of repeating situations. This is very important for problem management as well as diagnosis and remediation of current situations. Knowing the details about prior occurrences may help solve the current issue.</p><p>With the 7.1 release the Graze API can now be used to find out if a situation has similar situations and if so, the associated details of those situations. This now enables automation and workflow actions to be performed based on this data.</p><p><strong>More Granular Permissions</strong> — Ensuring appropriate access is very important for our customers. In this release administrators now have more control over permissions.</p><p>New permissions include:</p><ul><li>Situation Resolve has its own permission</li><li>Visualize can be used to manage who can view situation generation data</li><li>Collaboration has multiple permissions to manage roles with read/write or read-only access</li><li>Situation Summary page now has a permission to access</li></ul><p><strong>Integrations UI Configuration Options</strong> — As part of our ongoing focus to simplify and ensure configuration is transparent, there are now additional configuration options available via the UI. Some options such as specifying multiple targets were only available via configuration file but all are now surfaced in the UI.</p><p>The list of updated integrations is</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/0*_LGfo_HTO2Y6SS5B.png" /></figure><p><strong>Integrations</strong> — These enable administrators and implementers to quickly integrate AIOps with well-known products to increase the speed of deployment. New integrations for data ingestion include:</p><ul><li>Moogsoft Observe</li><li>Moogsoft Observe Polling</li><li>Zabbix Webhook</li></ul><p><strong>System Management</strong> — One focus of this release is enabling our customers to more easily manage their deployment.</p><p>Improvements include:</p><ul><li>A utility manages the startup of Moogsoft related services on reboot</li><li>The logging component is now Apache Log4j which allows for more flexibility with logging options and dynamic updating of log levels</li><li>Separation of what was a central configuration file into configuration files based on functionality for ease of management</li><li>Automatic enablement of High Availability capability at the component level (requires system-wide enablement)</li></ul><p><strong>Documentation</strong> — We supply extensive online documentation for our software. You can browse all the documentation for AIOps 7.1 as well as previous versions of AIOps at <a href="https://docs.moogsoft.com/display/060500/Moog-Docs">docs.moogsoft.com</a>.</p><ul><li>The AIOps 7.1 <a href="https://docs.moogsoft.com/display/070100/Release+Notes">release notes</a> cover the new features, improvements, and bug fixes.</li><li>If you’re upgrading from a previous version of AIOps, follow these instructions:</li><li><a href="https://docs.moogsoft.com/display/070100/Upgrade+RPM+v7.0.x+to+RPM+v7.1.x">Upgrade: v7.0.x — v7.1.x</a></li><li>Here’s documentation for the new integrations:</li><li><a href="https://docs.moogsoft.com/display/070100/Observe">Moogsoft Observe</a></li><li><a href="https://docs.moogsoft.com/display/070100/Observe+Polling">Moogsoft Observe Polling</a></li><li><a href="https://docs.moogsoft.com/display/070100/Zabbix">Zabbix Webhook</a></li></ul><p>We hope you enjoy using Moogsoft AIOps 7.1 as much as we have enjoyed building the new features! If you have any comments or feedback, please send them our way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=916dc08fdae5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moogsoft/announcing-whats-new-in-moogsoft-aiops-7-1-916dc08fdae5">Announcing What’s New In Moogsoft AIOps 7.1</a> was originally published in <a href="https://medium.com/moogsoft">AIOps Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>