Skip to content
Tiatra, LLCTiatra, LLC
Tiatra, LLC
Information Technology Solutions for Washington, DC Government Agencies
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact
 
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact

Back to basics: Keys to taking a pragmatic approach to observability

In the world of IT operations, “observability” is a concept that’s been around for some time. Having been in IT operations for more than 30 years, I can say that, even before anyone called it “observability,” we were in effect examining ways to achieve the same ends.

While definitions can vary, in essence, observability is about gaining an understanding of a given system by tracking and analyzing its external outputs. When done right, observability should tell you two things:

  1. What’s going on now
  2. How to make improvements that yield better future results

Getting back to basics: 4 steps to gain true observability

In spite of all the purported potential of observability, many IT leaders I speak with still don’t feel like they’re really getting what was promised. Over time the concept of observability has grown highly complex; unnecessarily so in my opinion. I think a lot of teams could realize the power of observability by taking a simpler approach. Here are a few key steps to get started.

#1. Don’t collect more data, collect the right data

Today, large enterprises are awash in massive volumes of data points being collected by various monitoring systems. In time, enormous databases have emerged. Invariably, when issues arise, operators don’t know where to start; no one has time to look at all the data captured. Further, the reality is that many of these data points have no bearing on what really matters: the user experience.

Start by doing a cohesive inventory of all the data being collected, particularly with respect to application performance. Look at what needs to be captured, and, just as importantly, what doesn’t need to be.

#2. Do an honest assessment of approaches and tools

Next, do an objective assessment of current tools and approaches. See how you can rationalize the disparate tools being used. By reducing the number of tools that need to be procured, implemented, and supported, teams can realize a number of benefits, including reducing costs, administrative overhead, and monitoring “noise.”

#3. Ensure you have the right team

In going through this process, it is important to take a look at the people who look at the data.

In recent years, as environments have continued to evolve, I’ve often seen a disconnect in organizations. For example, a team of network engineers will be tasked with assessing increasing volumes of application-centric data.

In establishing a site reliability engineering (SRE) function in another organization, we were able to build a team with top talent from across key technology domains. We had network engineers, java programmers, database administrators, mainframe specialists, and more, and all were some of the company’s top experts in these areas.

Having the right expertise in the right place was invaluable. With this team, we could make significant strides in terms of establishing observability and gaining actionable insights for improvement. Most critically, we had the expertise needed to execute those insights.

#4. Break down silos

True observability isn’t achieved with monitoring silos. Ultimately, this isn’t simply about networks or apps—it’s about holistic observability that reveals what the user experience is really like. All different aspects need to be looked at together to make decisions that are best for the user experience and the business.

Conclusion

Within many enterprise IT shops today, the promise of observability isn’t being fully realized. By stripping out the data and tools that aren’t creating value, and taking a holistic, user-centric approach, teams can establish effective, powerful observability.

To learn more, be sure to visit us here. Also, you can view an IDC report that reveals the critical capabilities that NetOps teams need to gain complete network visibility and control.

Networking
Read More from This Article: Back to basics: Keys to taking a pragmatic approach to observability
Source: News

Category: NewsJune 29, 2023
Tags: art

Post navigation

PreviousPrevious post:3 things that make a CIO-CFO dream teamNextNext post:8 problematic IT team members — and how to deal with them

Related posts

Start small, think big: Scaling AI with confidence
May 9, 2025
CDO and CAIO roles might have a built-in expiration date
May 9, 2025
What CIOs can do to convert AI hype into tangible business outcomes
May 9, 2025
IT Procurement Trends Every CIO Should Watch in 2025
May 9, 2025
‘서둘러 짠 코드가 빚으로 돌아올 때’··· 기술 부채 해결 팁 6가지
May 9, 2025
2025 CIO 현황 보고서 발표··· “CIO, 전략적 AI 조율가로 부상”
May 9, 2025
Recent Posts
  • Start small, think big: Scaling AI with confidence
  • CDO and CAIO roles might have a built-in expiration date
  • What CIOs can do to convert AI hype into tangible business outcomes
  • IT Procurement Trends Every CIO Should Watch in 2025
  • ‘서둘러 짠 코드가 빚으로 돌아올 때’··· 기술 부채 해결 팁 6가지
Recent Comments
    Archives
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • October 2023
    • September 2023
    • August 2023
    • July 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • December 2022
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • July 2022
    • June 2022
    • May 2022
    • April 2022
    • March 2022
    • February 2022
    • January 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • August 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    Categories
    • News
    Meta
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Tiatra LLC.

    Tiatra, LLC, based in the Washington, DC metropolitan area, proudly serves federal government agencies, organizations that work with the government and other commercial businesses and organizations. Tiatra specializes in a broad range of information technology (IT) development and management services incorporating solid engineering, attention to client needs, and meeting or exceeding any security parameters required. Our small yet innovative company is structured with a full complement of the necessary technical experts, working with hands-on management, to provide a high level of service and competitive pricing for your systems and engineering requirements.

    Find us on:

    FacebookTwitterLinkedin

    Submitclear

    Tiatra, LLC
    Copyright 2016. All rights reserved.