IT has access to an amazing amount of data. Often we collect hundreds of data points on one server such as individual processor load, thread state, disk throughput both in and out etc. We then store this in a bin and use this to create a metric called something similar to server performance. When it comes time to provide reports (weekly, monthly and so on) IT then assigns some poor person the job of collating this information. This is usually done by running a report and importing it into a spread sheet and then combining various servers and metrics into some grouping and calling it an application. Then some numbers are calculated and saved in the spreadsheet to create a performance over time graph. The same is done with database numbers, application performance, network statistics etc. This process is then repeated by levels of management combining more numbers into a single number to represent service performance to allow reporting to more senior levels of management.
Given that IT is all about automating processes, this has struck me as somewhat backwards.
Data Management and IT – Operational Intelligence
IT by and large is staffed by realists – the type that don’t respond well to marketing, want solutions and have little time for repetition.
A second reality is that IT is a fledgling science. While it has a century under its’ belt, it has not developed some niceties like the common taxonomy of biology; every company creates its own rankings and groupings of IT functions. Quite often a great deal of resources are used in creating the custom taxonomy.
To add to the frustration of IT managers everywhere, different off the shelf applications also present data in the taxonomy that is coded specific to that application. It becomes more and more difficult to extract and combine data in a meaningful way.
An IT user friendly application should allow its user base to create rules for the grouping of data for reports. By allowing atomic bits of data, such as unused server capacity for a select group of servers, it now can report on the unused server capacity for an application. Using this application data as a new data point, the well-designed application will allow another ad hoc grouping to provide information on an over-all service.
This process of using groups to create other groups goes on as needed until the application is configured to match the taxonomy the company has designed. Instead of complex calculations each month, a one-time setup is created and automation is achieved.
By allowing different data elements to be members of more than one group, we can avoid a second common pitfall such as the question of factoring the time of DNS queries or a multi-application database server.
IT needs to save time, and its internal applications need to accept the reality of reporting against an ever changing data set that is custom to each company that uses it.
Robin Lyon is Director of Analytics at AppEnsure.
The Latest
The 2024 State of the Data Center Report from CoreSite shows that although C-suite confidence in the economy remains high, a VUCA (volatile, uncertain, complex, ambiguous) environment has many business leaders proceeding with caution when it comes to their IT and data ecosystems, with an emphasis on cost control and predictability, flexibility and risk management ...
In June, New Relic published the State of Observability for Energy and Utilities Report to share insights, analysis, and data on the impact of full-stack observability software in energy and utilities organizations' service capabilities. Here are eight key takeaways from the report ...
The rapid rise of generative AI (GenAI) has caught everyone's attention, leaving many to wonder if the technology's impact will live up to the immense hype. A recent survey by Alteryx provides valuable insights into the current state of GenAI adoption, revealing a shift from inflated expectations to tangible value realization across enterprises ... Here are five key takeaways that underscore GenAI's progression from hype to real-world impact ...
As software development grows more intricate, the challenge for observability engineers tasked with ensuring optimal system performance becomes more daunting. Current methodologies are struggling to keep pace, with the annual Observability Pulse surveys indicating a rise in Mean Time to Remediation (MTTR). According to this survey, only a small fraction of organizations, around 10%, achieve full observability today. Generative AI, however, promises to significantly move the needle ...
While nearly all data leaders surveyed are building generative AI applications, most don't believe their data estate is actually prepared to support them, according to the State of Reliable AI report from Monte Carlo Data ...
Enterprises are putting a lot of effort into improving the digital employee experience (DEX), which has become essential to both improving organizational performance and attracting and retaining talented workers. But to date, most efforts to deliver outstanding DEX have focused on people working with laptops, PCs, or thin clients. Employees on the frontlines, using mobile devices to handle logistics ... have been largely overlooked ...
The average customer-facing incident takes nearly three hours to resolve (175 minutes) while the estimated cost of downtime is $4,537 per minute, meaning each incident can cost nearly $794,000, according to new research from PagerDuty ...
In MEAN TIME TO INSIGHT Episode 8, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses AutoCon with the conference founders Scott Robohn and Chris Grundemann ...
Numerous vendors and service providers have recently embraced the NaaS concept, yet there is still no industry consensus on its definition or the types of networks it involves. Furthermore, providers have varied in how they define the NaaS service delivery model. I conducted research for a new report, Network as a Service: Understanding the Cloud Consumption Model in Networking, to refine the concept of NaaS and reduce buyer confusion over what it is and how it can offer value ...
