![DX NetOps vs. InfluxData [EOL] report](https://www.peerspot.com/assets/media/images/icons/pdf-c33db68f.svg){kind=icon}
![InfluxData [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_64/QuafG8uWZsJc8SV1xtnXaify.jpg?_a=BACAGSDL)
![InfluxData [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_30/QuafG8uWZsJc8SV1xtnXaify.jpg?_a=BACAGSDL){kind=small}
![InfluxData [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_40/QuafG8uWZsJc8SV1xtnXaify.jpg?_a=BACAGSDL){kind=small}
DX NetOps can be improved by expanding its integrations with different tools, as it can currently integrate with Spectrum and other Broadcom products. It would be beneficial to gain integration capabilities with tools such as New Relic or SolarWinds. Integration with DX NetOps occurs through API, which fetches metrics from those tools, and this is currently happening in our area, with DX NetOps receiving data not only from Spectrum but also from New Relic and SolarWinds. DX NetOps could be improved by providing more communication methods beyond SNMP traps to accommodate different private clouds, especially as customers increasingly adopt vendor-specific clouds. For example, Sainsbury's uses SAP cloud, SAS, and Oracle cloud, where monitoring is not currently possible through DX NetOps and Spectrum, which are limited to certain mechanisms. Within the organization, SNMP is usable, but to display metrics from outside the organization, different communication methods such as agent-based connections, TCP/IP, or secured connections are necessary—features not currently available in DX NetOps and Spectrum.
