Download Open-AudIT

Go to open-audit.org to download the latest version. Select the Linux or Windows option, and download the binary.

Open-AudIT is installed on-premises. You can also use the FirstWave Virtual Machine if you prefer, and get all the FirstWave monitoring applications installed and ready to use.

How to install for Windows

Prerequisites

• For Windows, the following distributions are supported (64-bit only):
  • Windows Server 2016 and up.
• If you don’t already have NMAP, go to nmap.org to download the latest NMAP binary. Right-click the downloaded .exe file, select Run as Administrator, and run the installation wizard with default installation settings applied.
• If you don’t already have it, install the latest Visual C runtime.
• Windows 10 and 11 are not supported for Open-AudIT Server (they are fine as discovered machines).

Installing for SUSE? Get installation details here.

Claim your free licences

• Open your web browser, navigate to http://YOUR_SERVER/open-audit/, and log in.
• Fill out the form at http://YOUR_SERVER/open-audit/index.php/configuration/license_string to activate your free 20-device professional licence.

Add your credentials

Open-AudIT can handle a variety of credential types, including the standard SNMP, Windows, and SSH types.

• In the Open-AudIT dashboard, navigate to Discover > Credentials > Create Credentials.
• Add your credential details and click Submit.
• Repeat this process as many times as needed to add your desired device credentials to Open-AudIT.

If you don’t have the credentials for a device on your network you will still see the device in Open-AudIT, but data retrieval will be limited.

Now, you can add a discovery!

Start discovering

• From the Open-AudIT dashboard, navigate to Discover > Discoveries > Create Discoveries.
• Add a name and the subnet for your discovery. Typically most users use a /24 network ,e.g. 192.168.1.0/24.
• Click the Execute button on the discovery details page.
• Click the Refresh button at any time to update the logs as the discovery progresses.
• Repeat this process as many times as needed to add all desired discoveries.
• On the Discoveries dashboard, you’ll now see all your listed devices. To view detailed information on a discovered device, navigate to Manage > Devices > List Devices.
• Click the eye icon under the Details column for any device to explore the extensive data Open-AudIT has collected for it.

After adding your credentials and running your discoveries, you’ll notice your home dashboard now displays a variety of charts that give you deeper insights into your network.

Done!

Want a visual run-through? You can watch the entire process in more detail below.

Happy discovering!

Learn more about Open-AudIT

Open-AudIT YouTube playlist

Open-AudIT Community Wiki

Chat to our Support team

In managing computer networks, keeping services running and minimizing disruptions is crucial. One important way to measure how well network managers and operators handle problems is through Mean Time to Resolution (MTTR).

So, What is Mean Time to Resolution (MTTR)?

MTTR is a key performance indicator used in network management to quantify the average time it takes to resolve a network issue or outage from the moment it is detected.

 

This metric encompasses the entire process, from initial problem identification (when a device such as a router, switch, or server goes down or starts experiencing issues) through to the restoration of normal service. MTTR is calculated by taking the total time spent on resolving all incidents within a specific period and dividing it by the number of incidents.

 

 

In simpler terms, MTTR provides a clear picture of how long your network is out of action during a typical incident and how quickly your team can bring everything back to normal. It’s a reflection of the efficiency and effectiveness of your incident response processes.

Why MTTR Matters for Network Managers and Operators

MTTR is more than a mere number; it serves as a direct indicator of the health of your network management practices. Here’s why it’s so crucial:

1. Minimizing Downtime: Networks are the backbone of any organization, and every minute of network downtime can result in lost productivity, customer dissatisfaction, and revenue loss. MTTR helps network managers understand how quickly they can respond to and resolve issues, thus minimizing downtime and its associated impacts.
2. Operational Efficiency: A lower MTTR indicates a streamlined, efficient response process. It reflects well on the team’s capability to detect, diagnose, and fix issues quickly. This significantly enhances the network’s reliability, instilling a heightened level of confidence and bolstering the team’s reputation within the organization.
3. Customer Satisfaction (this is the most imporant one): In today’s fast-paced digital environment, customers expect near-instantaneous service. A quick resolution time keeps customers happy by ensuring that disruptions are brief and service is restored promptly.
4. Resource Management: MTTR can also help in assessing how effectively resources are being used during incident response. A consistently high MTTR might indicate bottlenecks or inefficiencies that need to be addressed, such as outdated tools or a lack of adequate training for the team.

What is a Good MTTR?

The definition of a “good” MTTR can vary depending on the industry, the complexity of the network, and the nature of the incidents. However, there are some general benchmarks that network managers can consider:

• Industry Standards: In many industries, a good MTTR is typically under 4 hours. However, for high-stakes environments, such as financial services or healthcare, MTTR might need to be even lower, often measured in minutes.
• Historical Performance: Your historical data is a great baseline. If your average MTTR has been 6 hours, bringing it down to 4 hours could be a significant improvement. The key is consistent improvement over time.
• SLAs and Customer Expectations: Service Level Agreements (SLAs) often dictate the acceptable MTTR for your organization. These agreements are usually based on customer expectations, which can vary greatly. Meeting or exceeding these SLAs should be the target.
• Comparative Analysis: Look at similar organizations within your industry. Benchmarking against peers can provide insight into where your MTTR stands and what might be achievable.

Conclusion

MTTR stands as a critical measure that network managers and operators need to monitor and improve. It acts as a clear signal of how rapidly your team can recover from network issues, affecting everything from operational efficiency to customer satisfaction. By aiming for a reduced MTTR, network teams are not only able to improve their service reliability but also bolster their overall network management approach. Ultimately, a successful MTTR is one that meets or surpasses your organization’s and its customers’ expectations, while continually striving for quicker and more effective resolutions.