# Elasticsearch and VeloCloud / VMWare SDWAN **URL:** \ **Category:** Elasticsearch\ **Created:** [June 12, 2023, 9:32pm UTC](https://discuss.elastic.co/t/elasticsearch-and-velocloud-vmware-sdwan/335810 "2023-06-12T21:32:57Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![hogie365](https://avatars.discourse-cdn.com/v4/letter/h/8e8cbc/32.png) [@hogie365](https://discuss.elastic.co/u/hogie365)\ **Post date:** [June 12, 2023, 9:32pm UTC](https://discuss.elastic.co/t/elasticsearch-and-velocloud-vmware-sdwan/335810/1 "2023-06-12T21:32:58Z")
Afternoon - I'm new to Elasticsearch and want to see if it's possible to connect to a VeloCloud API to pull and analyze logs from the VeloCloud orchestrator. We've been struggling getting back any real content over SNMP. Any help is appreciated. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [June 13, 2023, 8:48am UTC](https://discuss.elastic.co/t/elasticsearch-and-velocloud-vmware-sdwan/335810/2 "2023-06-13T08:48:54Z")
Elasticsearch itself doesn't pull logs from anywhere, you need something else to push logs into ES. Try the [Logstash forum](https://discuss.elastic.co/c/elastic-stack/logstash/14) for help with that. However, if the problem is that the data is not available to be pulled then you'll need to find someone with VeloCloud expertise to work out what to do about that. ---
**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\ **Post date:** [June 13, 2023, 10:49am UTC](https://discuss.elastic.co/t/elasticsearch-and-velocloud-vmware-sdwan/335810/3 "2023-06-13T10:49:33Z")
This question probably belongs more in the Beats/Elastic Agent/Logstash category. Regarding the API, (I'm not familiar with it), but there is this article about it: [Extracting VMware Velocloud SD-WAN events with Elastic Stack | SkinnyNetTech](https://www.skinnynettech.com/post/velo-elastic-fun/), it's a bit old, but the Filebeat [part](https://www.skinnynettech.com/post/velo-elastic-fun/#beatsfilebeatyml), still seems roughly accurate. You could also possibly try translating it into the Elastic Agent [Custom API Integration](https://docs.elastic.co/integrations/httpjson) for a more _modern_ approach. Regarding SNMP, in my opinion, this is probably the weakest part of the Elastic Stack when it comes to observability. The best way I've found to do SNMP with Elastic, is to actually use the [Prometheus snmp\_exporter](https://github.com/prometheus/snmp_exporter) to handle the SNMP part, and then use the Elastic [Prometheus Exporter Collector integration](https://docs.elastic.co/integrations/prometheus#prometheus-exporters-collectors) to scrape the snmp\_exporter and ingest data into Elasticsearch. ---
**Author:** ![hogie365](https://avatars.discourse-cdn.com/v4/letter/h/8e8cbc/32.png) [@hogie365](https://discuss.elastic.co/u/hogie365)\ **Post date:** [June 13, 2023, 3:17pm UTC](https://discuss.elastic.co/t/elasticsearch-and-velocloud-vmware-sdwan/335810/4 "2023-06-13T15:17:44Z")
Thank you for the assist, I will look at Log stach and see what I can find out. Appreciate the help ---
**Author:** ![techie.antonio](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/techie.antonio/32/77423_2.png) [@techie.antonio](https://discuss.elastic.co/u/techie.antonio)\ **Post date:** [July 2, 2023, 8:50am UTC](https://discuss.elastic.co/t/elasticsearch-and-velocloud-vmware-sdwan/335810/5 "2023-07-02T08:50:39Z")
The best way to poll SNMP and send it to Elasticsearch is to use the [**ElastiFlow SNMP Collector**](https://www.elastiflow.com/unified-snmp-collector). Follow the link to the documentation. ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/8/d821da58a6cc19553d0fe7469cc6578e8f721e0f.jpeg) If you are collecting IPFIX flow data from Velocloud, you should also look at ElastiFlow's Flow Collector. It is the only one I know of that properly handles the bi-direction flow records sent by Velocloud. From the changelog: > Bi-Directional Flows - Bi-directional records, as sent by Velocloud SD-WAN and certain Cisco and other devices, are now split into two uni-directional records, enabling the full ElastiFlow feature set to be applied to both directions represented in the original record. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 30, 2023, 8:51am UTC](https://discuss.elastic.co/t/elasticsearch-and-velocloud-vmware-sdwan/335810/6 "2023-07-30T08:51:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.