IT Operations Analytics (ITOA) - Revision history

User at 20:36, 1 December 2022

2022-12-01T20:36:34Z

Show changes

User at 18:17, 11 November 2022

2022-11-11T18:17:32Z

User at 18:15, 11 November 2022

2022-11-11T18:15:06Z

User at 17:24, 11 November 2022

2022-11-11T17:24:14Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T16:21:13Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

Show changes

User at 17:00, 19 July 2019

2019-07-19T17:00:17Z

User at 16:13, 19 July 2019

2019-07-19T16:13:49Z

User at 15:24, 19 July 2019

2019-07-19T15:24:57Z

User: Created page with "'''Content Coming Soon'''"

2018-12-06T22:40:13Z

Created page with "'''Content Coming Soon'''"

New page

'''Content Coming Soon'''

@@ Line 77: / Line 77: @@
 == See Also ==
-[[IT Operations (Information Technology Operations)]]<br />
+*[[IT Operations (Information Technology Operations)]]
-[[IT Operations Management (ITOM)]]<br />
+*[[IT Operations Management (ITOM)]]
-[[Information_Technology_Asset_Management_(ITAM)|Information Technology Asset Management (ITAM)]]<br />
+*[[Information_Technology_Asset_Management_(ITAM)|Information Technology Asset Management (ITAM)]]
-[[IT_Transformation|IT Transformation]]<br />
+*[[IT_Transformation|IT Transformation]]
-[[Information_System_(IS)|Information System (IS)]]<br />
+*[[Information_System_(IS)|Information System (IS)]]
-[[Information_Technology_(IT)|Information Technology (IT)]]<br />
+*[[Information_Technology_(IT)|Information Technology (IT)]]
-[[IT Ecosystem]]<br />
+*[[IT Ecosystem]]
-[[Big Data]]<br />
+*[[Big Data]]
-[[Data Analysis]]<br />
+*[[Data Analysis]]
-[[Data Analytics]]<br />
+*[[Data Analytics]]
-[[Enterprise Data Integration (EDI)]]<br />
+*[[Enterprise Data Integration (EDI)]]
-[[Enterprise Data Replication (EDR)]]<br />
+*[[Enterprise Data Warehouse (EDW)]]
-[[Enterprise Data Warehouse (EDW)]]<br />
+*[[Data Integration]]
-[[Data Integration]]<br />
+*[[ITIL_(Information_Technology_Infrastructure_Library)|ITIL]]

@@ Line 16: / Line 16: @@
 *Reactive to Proactive: IT Operations Analytics empowers teams to make decisions quickly, and equips them with the tools needed to make intelligent decisions. Proactive detection of patterns improves the [[system]] efficiency and helps to avoid any outages in future
 *Transform [[Service]] Delivery: IT Operations Analytics benefits the end consumer with transparency and accurate service delivery, irrespective of whether the end-user is a developer or a [[business]] user whose profits are proportional to system uptime.
-*Enhance [[Capacity Planning]]: In the age of [[virtualization]] and Scalability, the capability to operate dynamically is mandatory and is the primary focus for infrastructure managers. ITOA computes the utilization over a period of time to arrive at the best formula or [[strategy]] to deploy resources.
+*Enhance [[Capacity Planning]]: In the age of virtualization and Scalability, the capability to operate dynamically is mandatory and is the primary focus for infrastructure managers. ITOA computes the utilization over a period of time to arrive at the best formula or [[strategy]] to deploy resources.
 *Enable BYOD Integration: The concept of Bring Your Own [[Device]] (BYOD) at work has increased the access points that need to be managed for security and sustainability. ITOA lets administrators collect and index data from applications, machines and sensors, websites, mobile devices, and more - and analyze it in real-time.

@@ Line 5: / Line 5: @@
-== Definition of IT Operations Analytics (ITOA)<ref>Definition - What is of IT Operations Analytics (ITOA)? [https://www.extrahop.com/company/blog/2016/it-operations-analytics-itoa-big-data/ Eric Giesa]</ref> ==
+== Definition of IT Operations Analytics (ITOA)<ref>Definition - What is IT Operations Analytics (ITOA)? [https://www.extrahop.com/company/blog/2016/it-operations-analytics-itoa-big-data/ Eric Giesa]</ref> ==
 IT Operations Analytics (ITOA) is an approach that allows you to eradicate traditional data siloes using Big Data principles. By analyzing all your data via multiple sources including log, agent, and wire data, you'll be able to support proactive and data-driven operations with clear, contextualized operational intelligence:
@@ Line 13: / Line 13: @@
 == The Need to Focus on IT Operations Analytics (ITOA)<ref>The Four Reasons for the Need to Focus on IT Operations Analytics (ITOA) [http://snuviktechnologies.com/2017/08/14/it-operations-analytics-infographics/ Snuvik]</ref> ==
-There are four reasons why companies need to focus on IT Operations Analytics in todays degital age.
+There are four reasons why companies need to focus on IT Operations Analytics in today's digital age.
-*Reactive to Proactive: IT Operations Analytics empowers teams to make decisions quickly, and equips them with tools needed to make intelligent decisions. Proactive detection of patterns improves the [[system]] efficiency and helps to avoid any outages in future
+*Reactive to Proactive: IT Operations Analytics empowers teams to make decisions quickly, and equips them with the tools needed to make intelligent decisions. Proactive detection of patterns improves the [[system]] efficiency and helps to avoid any outages in future
 *Transform [[Service]] Delivery: IT Operations Analytics benefits the end consumer with transparency and accurate service delivery, irrespective of whether the end-user is a developer or a [[business]] user whose profits are proportional to system uptime.
 *Enhance [[Capacity Planning]]: In the age of [[virtualization]] and Scalability, the capability to operate dynamically is mandatory and is the primary focus for infrastructure managers. ITOA computes the utilization over a period of time to arrive at the best formula or [[strategy]] to deploy resources.
-*Enable BYOD Integration: The concept of Bring Your Own [[Device]] (BYOD) at work has increased the access points that need to be managed for security and sustainabilty. ITOA lets administrators collect and index data from applications, machines and sensors, websites, mobile devices, and more - and analyze it in real time.
+*Enable BYOD Integration: The concept of Bring Your Own [[Device]] (BYOD) at work has increased the access points that need to be managed for security and sustainability. ITOA lets administrators collect and index data from applications, machines and sensors, websites, mobile devices, and more - and analyze it in real-time.
 === ITOA Uses Big Data Principles ===
 Nearly any Big Data initiative has the [[objective]] of transforming an [[organization]]'s access to data for better and more agile business insights and actions. However, this can only be achieved through the extraction, indexing, storage, and analysis of many different data sources coupled with the flexibility to add more data sources as they become available or as opportunities arise.
-To provide the greatest flexibility and avoid [[vendor]] lock-in, more organizations are adopting open source technologies like Elasticsearch, MongoDB, Spark, Cassandra, and [[Hadoop]] as their common data store. This same approach is at the heart of ITOA.
+To provide the greatest flexibility and avoid [[vendor]] lock-in, more organizations are adopting open-source technologies like Elasticsearch, MongoDB, Spark, Cassandra, and [[Hadoop]] as their common data store. This same approach is at the heart of ITOA.
 [[File:ITOA_Big_Data_Approach.png|400px|The Big Data Approach to ITOA]]<br />
@@ Line 30: / Line 30: @@
 === The Shift from Tools-Driven to Data-Driven IT ===
-The last couple decades has seen an accumulation of disjointed tools, resulting in islands of data that prevent you from getting a complete picture of your environment. This is the antithesis of Big Data. If the CIO wants their organization to be data-driven with the ability to provide better performance, availability, and security analysis while making more informed investment decisions, they must [[design]] a data-driven monitoring practice. This requires a shift in thinking from today's tool-centric approach to a data-driven [[model]] similar to a Big Data initiative.
+The last couple of decades have seen an accumulation of disjointed tools, resulting in islands of data that prevent you from getting a complete picture of your environment. This is the antithesis of Big Data. If the CIO wants their organization to be data-driven with the ability to provide better performance, availability, and security analysis while making more informed investment decisions, they must [[design]] a data-driven monitoring practice. This requires a shift in thinking from today's tool-centric approach to a data-driven [[model]] similar to a Big Data initiative.
@@ Line 38: / Line 38: @@
 *If the CISO wants better security insight, monitoring, and surveillance, they must think in terms of continuous pervasive monitoring and correlated data sources, not in terms of analyzing the data silos of log [[management]], anomaly detection, packet capture systems, or [[malware]] monitoring systems.
-*If the VP of [[Application]] Development wants better cross-team [[collaboration]], faster, more reliable and predictable application upgrades and rollouts for both on-premises and cloud-based workloads, they must have a continuous data-driven monitoring [[architecture]] and practice. The ITOA monitoring architecture must span the entire application delivery chain, not just the application stack. Because of all the workload interdependencies, without this data an organization will be flying blind resulting in project delays, capacity issues, cross-team dysfunction, and increased costs.
+*If the VP of [[Application]] Development wants better cross-team [[collaboration]], faster, more reliable, and predictable application upgrades and rollouts for both on-premises and cloud-based workloads, they must have continuous data-driven monitoring [[architecture]] and practice. The ITOA monitoring architecture must span the entire application delivery chain, not just the application stack. Because of all the workload interdependencies, without this data, an organization will be flying blind resulting in project delays, capacity issues, cross-team dysfunction, and increased costs.
-*If the VP of Operations wants to cut their mean time to resolution (MTTR) in half, dramatically reduce downtime, and improve end-user experience while instituting a continuous [[improvement]] effort, they must have the ability to unify and analyze across operational data sets.
+*If the VP of Operations wants to cut their mean time to resolution (MTTR) in half, dramatically reduce downtime, and improve the end-user experience while instituting a continuous [[improvement]] effort, they must have the ability to unify and analyze across operational data sets.
 *The CIO, security, application, [[network]], and operations teams can achieve these objectives by drawing from the exact same data sets that are the foundation of ITOA. This effort should not be difficult, costly or take years to implement. In fact, this new data-driven approach to IT is actually being accomplished today; we're just codifying the design principles and practices we've observed and learned from our own customers who are the inspiration behind it.
@@ Line 46: / Line 46: @@
 ITOA systems tend to be used by IT operations teams, and Gartner describes five applications of ITOA systems:
 *[[Root Cause]] Analysis: The models, structures and pattern descriptions of IT infrastructure or application stack being monitored can help users pinpoint fine-grained and previously unknown root causes of overall system behavior pathologies.
-*Proactive [[Control]] of Service Performance and Availability: Predicts future system states and the [[impact]] of those states on performance.
+*Proactive [[Control]] of Service Performance and Availability: Predicts future system states and the impact of those states on performance.
 *Problem Assignment: Determines how problems may be resolved or, at least, direct the results of inferences to the most appropriate individuals or communities in the enterprise for problem resolution.
-*Service [[Impact Analysis]]: When multiple root causes are known, the analytics system's [[output]] is used to determine and rank the relative impact, so that resources can be devoted to correcting the fault in the most timely and cost-effective way possible.
+*Service Impact Analysis: When multiple root causes are known, the analytics system's [[output]] is used to determine and rank the relative impact, so that resources can be devoted to correcting the fault in the most timely and cost-effective way possible.
-*Complement Best-of-breed Technology: The models, structures and pattern descriptions of IT infrastructure or application stack being monitored are used to correct or extend the outputs of other discovery-oriented tools to improve the fidelity of information used in operational tasks (e.g., service dependency maps, application runtime architecture topologies, network topologies).
+*Complement Best-of-breed Technology: The models, structures, and pattern descriptions of IT infrastructure or application stack being monitored are used to correct or extend the outputs of other discovery-oriented tools to improve the fidelity of information used in operational tasks (e.g., service dependency maps, application runtime architecture topologies, network topologies).
-*Real time application behavior learning: Learns & correlates the behavior of Application based on user pattern and underlying Infrastructure on various application patterns, create metrics of such correlated patterns and store it for further analysis.
+*Real-time application behavior learning: Learns & correlates the behavior of the Application based on user patterns and underlying Infrastructure on various application patterns, creates metrics of such correlated patterns, and stores it for further analysis.
-*Dynamically Baselines [[Threshold]]: Learns behavior of Infrastructure on various application user patterns and determines the Optimal behavior of the Infra and technological components, bench marks and baselines the low and high water mark for the specific environments and dynamically changes the bench mark baselines with the changing infra and user patterns without any manual [[intervention]]
+*Dynamically Baselines [[Threshold]]: Learns behavior of Infrastructure on various application usage patterns and determines the Optimal behavior of the Infra and technological components, benchmarks, and baselines the low and high water marks for the specific environments and dynamically changes the benchmark baselines with the changing infra and user patterns without any manual [[intervention]]
@@ Line 60: / Line 60: @@
 *Synthetic data (service checks and synthetic transactions) –This data enables IT teams to test common transactions from locations around the globe or to determine if there is a failure in their network infrastructure. Although synthetic transactions are no replacement for real-user data, they can help IT teams to discover errors or outages at 2 a.m. when users have not yet logged in. Tools that fit into this category include Nimsoft, Pingdom, Gomez, and Keynote.
 *Wire data (L2-L7 communications, including full bi-directional payloads) – The information available off the wire, which has traditionally included HTTP traffic analysis and packet capture, historically has been used for measuring, mapping, and forensics. However, products from vendors such as Riverbed and NetScout barely scratch the surface of what's possible with this data source. For one thing, they do not analyze the full bi-directional payload and so cannot programmatically extract, measure, or visualize anything in the transaction payload. NetFlow and other flow records—although technically machine data generated by network devices—could be considered wire data because they provide information about which systems are talking to other systems, similar to a telephone bill.
-Every IT organization needs visibility into these four sources of data. Each data source serves an important purpose, although the purposes are evolving as new technologies open up new vistas in terms of what's possible. In the realm of wire data, ExtraHop unlocks the tremendous potential of this data source by making it available in real-time and in a way that makes sense for all IT teams.
+Every IT organization needs visibility into these four sources of data. Each data source serves an important purpose, although the purposes are evolving as new technologies open up new vistas in terms of what's possible. In the realm of wire data, ExtraHop unlocks the tremendous potential of this data source by making it available in real time and in a way that makes sense for all IT teams.

@@ Line 9: / Line 9: @@
 [[File:ITOA.png|400px|IT Operations Analytics (ITOA)]]<br />
@@ Line 32: / Line 41: @@
 *If the VP of Operations wants to cut their mean time to resolution (MTTR) in half, dramatically reduce downtime, and improve end-user experience while instituting a continuous improvement effort, they must have the ability to unify and analyze across operational data sets.
 *The CIO, security, application, network, and operations teams can achieve these objectives by drawing from the exact same data sets that are the foundation of ITOA. This effort should not be difficult, costly or take years to implement. In fact, this new data-driven approach to IT is actually being accomplished today; we're just codifying the design principles and practices we've observed and learned from our own customers who are the inspiration behind it.
@@ Line 43: / Line 63: @@
-[[File:ITOA_Architecture.png|300px|The Four Primary Sources of Data for IT Operations Analytics (ITOA) ]]<br />
+[[File:ITOA_Architecture.png|400px|The Four Primary Sources of Data for IT Operations Analytics (ITOA) ]]<br />
 source: Extrahop<br />

@@ Line 2: / Line 2: @@
 *Proactively avoid outages.
 *Achieve faster mean time to repair (MTTR).
-*Realize cost savings through greater operational efficiency.<ref>Definition - What does IT Operations Analytics (ITOA) Mean? [https://www.ibm.com/cloud-computing/xx-en/products/hybrid-it-management/it-operations-analytics/]</ref>
+*Realize cost savings through greater operational efficiency.<ref>Defining IT Operations Analytics (ITOA)? [https://www.ibm.com/cloud-computing/xx-en/products/hybrid-it-management/it-operations-analytics/]</ref>

← Older revision		Revision as of 15:24, 19 July 2019
Line 1:		Line 1:
−	~~'''Content Coming Soon'''~~	+	IT operations analytics involves collecting IT data from different sources, examining that data in a broader context, and proactively identifying problems in advance of their occurrence. With the right ITOA solution, you can detect patterns early to predict issues before they arise. You can extract insight from key operational data types, such as log files, performance metrics, events and trouble tickets, so you can:
		+	*Proactively avoid outages.
		+	*Achieve faster mean time to repair (MTTR).
		+	*Realize cost savings through greater operational efficiency.<ref>Definition - What does IT Operations Analytics (ITOA) Mean? [https://www.ibm.com/cloud-computing/xx-en/products/hybrid-it-management/it-operations-analytics/]</ref>