How do you measure and report on network performance and reliability using documentation data?

1 Documentation data sources

Documentation data can come from various sources, depending on the level of detail required. Network diagrams are graphical representations of the network structure, components, connections, and functions, which can help visualize the network layout, identify potential bottlenecks, and troubleshoot issues. Network inventories are lists of all the network devices, their specifications, locations, and statuses, allowing you to track resources and plan for upgrades. Network policies define the network behavior, access, and performance to enforce standards and comply with regulations. Lastly, network logs are records of events, activities, and errors that help measure performance, identify root causes of problems, and audit operations.

2 Documentation data collection

In order to collect documentation data effectively, you need to have a clear and consistent methodology that covers data scope, sources, and format. Data scope involves defining what data needs to be collected, how often, and for what purpose. Data sources involve identifying where and how to obtain the data, whether manually or automatically. Data format involves standardizing the data format, naming conventions, and structure for accuracy and ease of processing. Examples of common file formats include PDF, CSV, XML, and JSON; industry best practices include ITIL or ISO/IEC 27001.

3 Documentation data analysis

In order to analyze documentation data, you need to have a set of metrics and indicators that measure the network performance and reliability. These include availability, which is the percentage of time that the network is operational and accessible; throughput, which is the amount of data that can be transmitted or received in a given time; latency, which is the delay between the sending and receiving of data packets; and packet loss, which is the percentage of data packets that are lost or discarded during transmission. A high availability, throughput, and low latency and packet loss all indicate a reliable, fast, responsive network that meets service level agreements (SLAs), supports bandwidth requirements, minimizes transmission time, and preserves data integrity.

4 Documentation data reporting

To report on documentation data effectively, it is important to have a clear and concise way of presenting the data analysis results and recommendations. Visual aids such as charts, graphs, tables, or dashboards can be used to display the data in a graphical and interactive way, while summaries, headlines, or bullet points can be used to convey the main messages, findings, or actions. Additionally, feedback, comments, or questions can be used to engage the audience and solicit their opinions or address their concerns. Doing so will help improve communication, collaboration, and alignment among stakeholders.

5 Documentation data tools

In order to effectively use documentation data, you need the right tools. SolarWinds Network Performance Monitor is a comprehensive tool that can monitor, troubleshoot, and optimize the network performance and reliability. It can collect data from various sources and display it in real-time dashboards, charts, or reports. Lucidchart is a cloud-based tool that can create, edit, and share network diagrams. It can help document the network topology and policies, as well as integrate with other tools. Splunk is a powerful tool that can collect, index, and analyze network logs. It can measure the network performance, detect anomalies, and investigate incidents. It can also provide insights, alerts, or recommendations based on the data patterns.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?