Thank you for contacting Support at FirstWave.

For us to assist you in creating a case, you will need to:

1. Create a FirstWave Support Jira Account
2. Log a FirstWave Support Ticket

For any assistance or inquiries, reach out to us at
support@firstwave.com.

Discover how this central communication system enables you to scale and decouple your communication in a distributed network architecture.

As businesses increasingly rely on distributed systems and microservices to serve their growing networks, effective communication between their different components becomes more challenging.

Enter message bus, or enterprise service bus: a communication system enabling seamless data exchange between network components to help you manage your distributed network.

In this blog, we’ll break down the concept of a message bus architecture, explaining how it works, its core features, available alternatives, and the benefits that a message bus solution like FirstWave opHA-MB brings to distributed systems.

Table of Contents

• What is message bus?
• Key components of a message bus architecture
• The benefits of message bus
• Common use cases for message bus technology
• Alternatives to message bus
• When to use which architecture
• The ultimate message bus solution: opHA Message Bus

What is message bus?

Imagine a bustling city with numerous neighborhoods, each representing a different application or service. To keep the city running smoothly, these neighborhoods need to exchange information efficiently.

A message bus acts like the city’s central transit system, ensuring messages are delivered to the right destinations without requiring any direct connections between them. In technical terms, the message bus enables different applications, services, or systems to communicate by transmitting messages through a shared infrastructure.

This setup ensures that each component remains independent for flexibility and scalability.

Key components of a message bus architecture

1. Producers (pollers)

Also known as peers, pollers collect data from various network devices and systems, generating messages that contain critical information about network performance, events, and statuses. These pollers can be scaled horizontally or vertically for efficient data collection across expansive networks.

2. Broker (message bus)

Serving as the central communication hub, the message bus ensures real-time synchronization among multiple pollers. It manages the routing of messages from producers to consumers, maintaining data integrity through message replication across three nodes, which allows the system to tolerate single-node failures.

3. Consumers (primary server and applications)

The primary server and associated applications function as consumers. They receive and process messages relayed by the message bus, providing users with a consolidated, real-time view of network health and performance. This setup enhances capabilities like event logging, monitoring, and the generation of intuitive dashboards and reports.

A message bus decouples communication, instead allowing senders and receivers to operate independently so network communication can happen asynchronously. This means users can manage distributed network systems via a central point that standardizes disparate communication styles. The result: a simple, integrated system.

The benefits of message bus

A message bus architecture is useful for businesses managing large-scale, distributed, multi-customer, and/or mission-critical networks, as data is freely available to travel between endpoints as needed.

• Multi-tenancy support: Especially for Managed Service Providers (MSPs), managing multiple clients efficiently is critical. A message bus architecture is designed for multi-tenancy, allowing MSPs to handle multiple customer environments within a single infrastructure.
• Fault tolerance: To ensure uninterrupted operations, many message buses (including opHA Message Bus) are built with fault tolerance and redundancy mechanisms that keep services running even if individual components fail.
• Flexibility: Scale your architecture with minimal configuration as decoupled components can operate and change independently. Easily handle high-traffic scenarios with the ability to distribute single messages across multiple consumers.
• Managed distribution: Message bus solves the problem of temporal decoupling, as peers and the primary do not need to be online simultaneously for the system to work. Messages can also be delivered in either single, group, or broadcast models.
• Reduced delays: Receive events to the primary system in real time, and process new events with minimal to no downtime.
• No API calls: Unlike traditional communication, where both services must be available simultaneously, a message bus can communicate at any time as well as rapidly push inventory updates.
• Reliability: Messages can be stored temporarily to prevent data loss, and retry mechanisms are supported if a consumer fails.
• Security: Authentication can be configured to control who sends and receives messages, and encryption can (and should) be incorporated to maintain secure communication.
• Monitoring: Track message flows for debugging, auditing, and performance monitoring.

Common use cases for message bus technology

1. Microservices architecture

In modern network management and cybersecurity environments, different services handle distinct functions—such as network monitoring, security alerts, performance analytics, and automation workflows—while seamlessly communicating with each other. A good message bus acts as the backbone for this communication, ensuring that services remain loosely coupled, scalable, and resilient in distributed architectures.

Network management benefits for microservices include:

• Seamless data flow: Ensures real-time data exchange between network monitoring tools, security systems, and reporting dashboards.
• Scalability: Allows IT teams and MSPs to add or modify monitoring components without affecting the entire system.
• Reduced latency and bottlenecks: Distributes network event data efficiently, preventing system slowdowns.
• Asynchronous processing: Enables automated alerts, log analysis, and device polling without delays.

2. Event-driven systems

Modern applications rely on real-time event processing to improve responsiveness and automation. A message bus is a core component of event-driven architectures, where events (e.g., user actions, system changes, external triggers) are published and consumed dynamically.

Where it’s useful:

• IoT networks: Devices publish sensor data, and analytics engines process it instantly.
• Cybersecurity monitoring: Suspicious activity is flagged and sent to security systems in real time.
• Finance and banking: Fraud detection systems react instantly to unusual transactions.

Alternatives to message bus

Alternatives to a message bus are usually point-to-point based, where services communicate directly rather than via a central interconnected point.

Point-to-point communication has its benefits, but it does limit your capabilities in that it silos data between sender and receiver, preventing cross-communication which can limit efficiency in more complex architectures.

But the good news is that you’re not just limited to one option; your distributed system can use a combination of communication styles for different functions to optimize its efficiency for your business.

APIs

APIs are a tightly coupled solution where each of your services need to know about each of your endpoints. With APIs, each service manages its own connections. This approach is ideal for simpler architectures or where latency isn’t a major consideration.

Pros:

• Suits synchronous interactions: APIs work when a service needs an immediate response and can’t be held or queued.
• Easy to implement: APIs are ideal in small-scale applications where adding a message bus would be overkill.
• Easy to integrate: APIs allow messages to be externally exposed to public or partner systems through simple calls.

Cons:

• Failure recovery challenges: Failure recovery mechanisms are harder to implement as services handle errors individually.
• Request bottlenecks: Too many requests can overload an API-driven system, leading to delays or failures.
• Limited scalability: API-driven systems are difficult to scale as each service directly communicates with others, increasing management complexity.
• Workflow issues: Performance and reliability suffer in asynchronous workflows like order processing or event-driven systems.
• High-throughput limitations: High-throughput systems that need decoupling and scalability can’t be supported, as each service manages its own connections.

Message queuing

A message queue is similar to a message bus, but they differ in how messages are routed and processed. Unlike a message bus, a message queue uses point-to-point communication and messages are prioritized by first in, first out. Once consumed, the message is simply removed from the queue.

Pros:

• Simple security: One-to-one messaging circumvents the need to implement encryption or similar security measures.
• Easy to implement: Ideal for task-based workflows, background jobs, or small applications with a clear producer-consumer relationship.
• Message durability: Messages can be persisted in the queue, ensuring they’re not lost even if the consumer is unavailable.

Cons:

• Limited communication: No built-in publish-subscribe model is available, limiting communication to one-to-one scenarios.
• No prioritization: There is no ability to prioritize or triage messages.
• Complex management: Managing message queues becomes more difficult at scale, and eventually totally inefficient.
• Potential for bottlenecks: With no ability to prioritize or triage messages, important messages can pile up in a queue if a consumer is overwhelmed or unavailable.

When to use which architecture

• APIs provide a tightly coupled solution, where each of your services need to know about each of your endpoints. If you use them on your own, you’re limited by point-to-point communication only, but APIs can form a useful part of a larger combination of communication architectures.
• Message queuing can be easy to implement for simple networks that manage only task-based workflows and point-to-point communication. But they’re not always easy to manage, as queue-based solutions typically require monitoring to ensure the queue doesn’t come too large, creating a bottleneck. They also require some form of orchestration to handle message processing.
• A message bus architecture is best suited for event-driven architectures, real-time updates, and systems where messages need to be broadcast to multiple consumers, e.g. notification systems, microservices communication. Message bus is also ideal for its ability to scale with your network as it grows over time, and integrates more complex or mission-critical communication systems.

If you have the time to implement and manage them all efficiently, you can use a message bus alongside other communication methods to expand your feature scope and optimize your setup for different use cases.

Some single providers will provide all of these functionalities in-house to make your journey even easier; for example, in addition to FirstWave’s opHA Message Bus solution, we also provide APIs to allow for message transfers, as well as integrate with queue-based message brokers such as RabbitMQ – all combined with hands-on expert support to make implementation easy.

Which is right for me?

To help you choose the best design (or combination of designs) for your business, ask yourself the following questions:

• Do we require or would we benefit from event-driven architecture?
• What level of decoupling do we need? Which services (if any) need the ability to communicate asynchronously?
• How critical is real-time communication? Do we need instant responses, near real-time event-driven updates, or delayed processing?
• What is our expected message volume and load on our services?
• How will we build resilience into our network? Do we need fault-tolerant messaging or constant availability?
• How important is scalability now, and what are our long-term growth plans?
• How do we plan to adopt AI or ML into our network, and how do we expect this to impact our network communication patterns?

The ultimate message bus solution: opHA Message Bus

opHA Message Bus (opHA-MB) is FirstWave’s own message bus solution, enabling you to simplify management of your distributed network systems with real-time data transfer across diverse and multi-tenanted environments.

This advanced network management solution acts as the central nervous system to your network to help you maintain optimal network performance, ensure resilience, and swiftly resolve the issues that come with complex network infrastructure.

How messages flow through opHA-MB

• Generating messages: Pollers collect data from network devices and generate messages containing key information.
• Publishing to the bus: These messages are sent to opHA-MB, which acts as the central broker.
• Smart routing: opHA-MB identifies which applications or services (consumers) need the data and directs messages accordingly.
• Processing and action: Consumers, such as the primary server, opCharts, and opEvents, receive the messages, process the data, and trigger the necessary actions, such as alerts or dashboard updates.

By keeping producers and consumers decoupled, this architecture allows each component to function independently. This improves flexibility, scalability, and resilience—ensuring efficient network management even as demands grow.

Features of opHA-MB

• Multi-tenancy: Managed Service Providers (MSPs) can easily manage multiple tenants with a single, configurable interface.
• Real-time communication and event management: Reduce data transfer times with real-time sync between multiple pollers, and enhance Mean Time to Resolve (MTTR) with immediate event notifications from pollers to the primary server.
• Fault tolerance: Ensure data integrity with message replication across three nodes, tolerating single-node failures.
• Multi-server architecture: Distribute the server load to multiple pollers for efficient data collection and processing.
• Provisioning management: Simplify platform provisioning with push changes and new poller deployment at the click of a button.
• Scaling for high availability: Scale pollers horizontally or vertically with mirroring to improve availability, redundancy, and flexibility across your architecture.
• Integration with FirstWave products: opHA-MB is designed to work seamlessly with other FirstWave products, including opEvents and opCharts, to  enhance your network management capabilities.

Key benefits of opHA-MB

• Unparalleled network visibility: Gain instant insights into your network with immediate event updates, empowering proactive issue resolution.
• Enhanced network resilience: Minimize downtime and ensure uninterrupted service delivery with automated failover mechanisms and resilient event transfer.
• Event prioritization: When you use opHA-MB as part of your FirstWave suite of solutions, your data is prioritized by our software to enable intuitive event prioritization with real-time notifications, so you can address the events that matter most to your business.
• Streamlined network management: Reduce manual intervention and optimize network management tasks with automated event processing and centralized data management.
• Scalable and flexible architecture: Grow your architecture with your business and make changes as needed, with the ability to scale pollers horizontally or vertically.
• Reduced delays: Receive events to your primary system in real time to process new events with minimal to no downtime, as well as zero event loss in high-traffic environments.
• No API calls: Push inventory updates to multiple systems instantly and automatically.

Learn more about opHA-MB

By activating the Virtual Operator feature in the NMIS opConfig module, IT managers can empower their team to proactively address common network issues, ensuring optimal performance, security, and compliance.

The virtual operator can:

• Troubleshoot common issues automatically. No more sifting through logs or waiting for expert assistance. They can diagnose and resolve common network problems instantly.
• Always follow best practice procedures for network security. Because they follow a script that you create, compliance with industry standards and regulations is pre-defined by you, removing human error and leaving you confident in your network’s safety.
• Help your team move from reactive to proactive network management. Reduce errors, increase performance, and free up valuable time for strategic initiatives.

The Evolution of Network Operations – from Manual to Virtual

The landscape of network operations has been undergoing a radical transformation.

Traditionally, managing networks involved a predominantly manual approach, relying heavily on human expertise and intervention to address issues, configure devices, and ensure optimal performance. Human error, time-consuming processes, and the inability to scale effectively in the face of growing network complexity posed significant challenges to traditional network management practices.

In the past decade, network monitoring and management platforms have become more intelligent, with advances in big data providing greater insights into a network environment, how and when it is accessed, what devices are used and when, which services are performing optimally, and which services are degrading.

According to the Gartner Market Guide to Network Automation, while more than 65% of enterprise networking activities are performed manually across SME’s, a growing percentage of large enterprises automate more than half of their network activities.

Firstwave Cloud Technology has been at the forefront of this new era of machine intelligence, gathering and analysing network data to provide advanced anomaly detection and predictive analytics that allows operators to proactively manage infrastructure and devices to ensure a healthy and predictable network environment.

With the introduction of the Virtual Operator, this machine intelligence goes a level deeper, allowing the NMIS platform to take action on insights and allowing operators to script a series of activities that the operator can perform at the touch of a button.

This article delves more deeply into the concept of the Virtual Operator, exploring its benefits and potential impact on an organisation’s network automation strategy.  We will examine how automation, through the implementation of a Virtual Operator, is reimagining network administration, driving efficiency, enhancing security, and unlocking new levels of performance and insights.

What is the Virtual Operator?

The Virtual Operator, is a software agent designed to automate repetitive tasks, optimise network performance, and provide intelligent insights. It functions as a rule-based engine that learns from historical data, network configurations, and best practices, allowing it to make informed decisions and take proactive actions to maintain network stability and efficiency.

Think of a Virtual Operator as a highly specialised AI assistant tailored for network administration. It acts like an extension of the network team, taking on the mundane and repetitive tasks, freeing up human engineers to focus on more strategic and complex challenges.

Benefits of implementing a Virtual Operator

The implementation of a Virtual Operator offers several key benefits to network administration teams:

1. Human Resource Optimisation

By automating routine tasks, the Virtual Operator can free up engineers to focus on more strategic and complex challenges. This shift allows teams to maximise human talent, enabling them to tackle innovation, problem-solving, and the implementation of new technologies.

2. Improved Network Efficiency and Performance

The Virtual Operator in conjunction with the broader opConfig and opEvents module can continuously monitor network performance, identify potential issues, and proactively take corrective actions. This pre-emptive approach ensures optimal network performance, minimising downtime, and maximising resource utilisation.

3. Enhanced Security and Compliance

The Virtual Operator can implement and enforce security policies, detect anomalies, and respond to security threats in real-time. This automated approach strengthens network security, improves compliance with industry regulations, and reduces the risk of security breaches.

4. Data-Driven Decision Making

Virtual Operators leverage vast amounts of network data to gain valuable insights and optimise network configurations. These insights empower network teams to make informed decisions based on real-time data, leading to more effective resource allocation and network optimisation.

Use Case:  Managed Service Providers

Managed Service Providers (MSPs) often manage multiple client networks simultaneously. This can be a resource-intensive task, particularly when dealing with routine maintenance and troubleshooting. The Virtual Operator offers a solution to this challenge by automating many of the routine tasks that MSPs typically perform.

For example, a MSP can use the Virtual Operator to automate the process of applying security patches across multiple client networks. The Virtual Operator can execute the necessary commands to apply the patches, run tests to ensure that the patches have been applied correctly, and report any issues that arise. This not only reduces the workload for the MSP’s engineers but also ensures that the patches are applied consistently and without errors.

Use Case: Hybrid Networks

The Virtual Operator simplifies the management of hybrid networks by automating the tasks required to maintain connectivity and performance.

For example, the Virtual Operator can automatically adjust network configurations to optimise performance as workloads shift between on-premise and cloud environments. It can also monitor network traffic for potential issues and make adjustments in real-time to prevent disruptions. This level of automation ensures that hybrid networks operate smoothly and efficiently, even as conditions change .

How Businesses can expand their Network Automation beyond the Virtual Operator

The adoption of the Virtual Operator for network administration presents a key stepping stone towards the future of network automation for IT teams.  How can a business expand the effectiveness of Virtual Operator and what new developments can we expect to see as network automation technology further evolves?

1. Increased Automation and Self-Healing Networks

Use of the Virtual Operator alongside other modules such as opEvents, opTrend and Open-Audit will drive further automation in network management, eventually enabling self-healing networks that can identify and resolve issues without human intervention. This will lead to more resilient, reliable, and efficient network infrastructure.

2. Enhanced Network Intelligence and Analytics

The use of the Virtual Operator to routinely check network health will play a critical role in advancing network intelligence, enabling teams to gain deeper insights into network performance, security threats, and user behaviour. This will empower teams to make more informed decisions and proactively optimise their networks.

3. Evolution of Network Administration Roles

Eventually, the use of network automation tools such as the Virtual Operator will transform the role of network administrators and engineers, shifting their focus from routine tasks to more strategic and creative activities. They will become more involved in AI model development and instructional writing, data analysis, and the design of intelligent network solutions.

Conclusion

The Virtual Operator represents a significant step forward in network automation, leveraging the power of AI to enhance network performance, optimise operations, and free up human resources for more strategic tasks. As AI and automation continue to advance, features like the Virtual Operator will play an increasingly crucial role in enabling more intelligent, efficient, and resilient network infrastructure.

Reference:

Gartner 2023 Market Guide to Network Automation

https://www.gartner.com/en/documents/4913231

Download Open-AudIT

Visit our website 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 licenses

• 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 100-device Professional license.

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.

Quick Guide: How to Get Secure Traffic Management With NMIS

Streamline your traffic management and boost your network efficiency with our easy step-by-step guide to using Secure Traffic Manager with NMIS.

In September 2023, FirstWave acquired a company called Saisei, including its flagship platform, Secure Traffic Manager (STM), for network traffic shaping and deep packet inspection.

This tool is a powerful way for telcos and large enterprises to monitor and manage network traffic, allowing certain applications or services to have greater Quality of Service (QoS) than others.

There are several benefits to using STM:

• Prevent bandwidth hogs with fair use host equalization
• Save on bandwidth costs without impacting customer experience
• Optimise streaming, even during peak times
• Prevent OS updates and other low-priority traffic from negatively impacting your network
• Always-on solution providing key metrics for proactive management and reduction in Mean Time to Innocence
• Security augmentation

Using STM with FirstWave’s open-source network management solution, NMIS, gives you full visibility and control over this traffic so you can set rules to automate traffic management, orchestrate alerts, and more.

This quick guide’ll show you how to monitor your Saisei STM appliance with NMIS.

Install NMIS

First, ensure that NMIS is installed and configured properly in your environment. Follow the installation instructions provided by FirstWave here. FirstWave offers a 20-node free license to get you started.

Configure SNMP on your STM appliance

Enable SNMP (Simple Network Management Protocol) on your STM appliance. Configure SNMP settings such as community strings and SNMP versions according to your security policies and requirements.

Add STM appliance to NMIS

In NMIS, add the STM appliance as a device to be monitored. You’ll need to provide the IP address or hostname of the STM appliance, SNMP community strings, and any other necessary authentication details.

Configure monitoring parameters

Specify which parameters and metrics you want to monitor on the STM appliance. This could include things like bandwidth usage, network traffic, or CPU and memory utilization.

Set up thresholds and alerts

Define threshold levels for monitored parameters to trigger alerts when certain conditions are met. This allows you to proactively manage and respond to potential issues on the STM appliance.

Test monitoring

Once configured, test your monitoring setup to ensure NMIS is successfully collecting data from the STM appliance and that alerts are working as expected.

Schedule regular maintenance

Periodically review and update your monitoring configuration as needed. This ensures that your monitoring remains effective as your network and infrastructure evolve over time.

That’s it! Now you can get all the benefits of STM combined with all the benefits of NMIS. Throughout this process, you can refer to FirstWave documentation for specific guidance on integrating STM appliances with NMIS.

Need further assistance? Reach out to the FirstWave support team.