NetBrain currently has no way to automatically build a source-to-destination path when source and destination IP addresses are supplied through a trigger source, such as a ticketing system, email, or bot, for a given application. Users must manually input path endpoints before running any diagnostic checks, which delays troubleshooting for ticket-driven automation. This enhancement would allow the source and destination IP addresses parsed from a trigger source to automatically populate a path calculation on the fly, and then execute a predefined, application-specific set of diagnostic intents, such as device health, interface health, and application health checks, against that path to produce a diagnosis output. Automating path creation and diagnosis directly from trigger data would reduce manual setup time and speed up root-cause identification for customers running high volumes of ticket-triggered network and application health investigations.
On the Roadmap
Automatic Path Creation and Diagnosis from Trigger-Sourced Source/Destination IPs
Login to the community
No account yet? Create an account
Sign in with SSO
Login via NetBrain Universityor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
