QOS has written solutions that allow us to monitor the reachability of and latency challenges to that database from each VeloCloud edge device. We can detect if a route from the application is down all the way up to the customer’s data center. Or, we can validate that the route is up and that application issues are arising elsewhere in the system.
The VeloCloud edge contains an internal stateful firewall that blocks all incoming requests by default, unless they are explicitly allowed via the VeloCloud orchestrator. To facilitate these security logging requirements, QOS developed a solution that looks for incoming requests from these specific IP addresses, logs these requests in a specific format and streams them to the customer’s syslog environment. The request is blocked by the VeloCloud edge and the customer is alerted via their existing environment. The VCO also doesn’t have a native way to log incoming requests; just outbound or sources that are specifically NAT’d to an internal destination. There is also not a native way to manage a blacklist of IP addresses. They block everything incoming by default and let you whitelist specifics. Customers who need a more flexible way to log incoming requests can benefit from the custom integrations QOS has written.