2. Network automation
Network automation will continue to grow. New products are making it easier, and network teams are starting to develop the skills to take advantage of it. But there’s still a long way to go. The sooner your organization starts, the sooner you’ll see the benefits. The challenge will be around standardization. Each vendor has its own API library. This is somewhat alleviated by model-based functionality that standardizes network data and configuration.
Automation will not only be about automating configuration changes. It will increasingly be used to verify that the network is working properly and to aid in the troubleshooting process. Instead of using a command line interface to gather troubleshooting information, the network team will be able to run a series of automation systems to gather information and georgia mobile database what has changed. This will significantly reduce troubleshooting time and lay the foundation for the wider use of network automation.
We will see continued adoption of ChatOps practices, which combine automated network data collection and analysis tools with team collaboration tools like Teams, Slack, and Webex. There will be some effort to make this integration happen, so productivity will be slow in the short term during this phase of the rebuild.
I expect event streaming and message bus technology to become important for network automation and monitoring. They make sense for projects that allow customers to create the holy grail of network management: a single pane of glass. It will collect and display important events and data from multiple network management systems that are necessary for monitoring a modern network.
We will also see model-based telemetry take over some of the performance data collection, but it will be some time before monitoring tools make that transition. This does not mean that SNMP will disappear. There are too many networking products and performance monitoring systems that rely on SNMP to collect and process performance data.