# Using ElasticSearch to capture Syslogs (windows) **URL:** \ **Category:** Elasticsearch\ **Created:** [August 22, 2017, 7:11pm UTC](https://discuss.elastic.co/t/using-elasticsearch-to-capture-syslogs-windows/97963 "2017-08-22T19:11:35Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![blackmail242](https://avatars.discourse-cdn.com/v4/letter/b/9dc877/32.png) [@blackmail242](https://discuss.elastic.co/u/blackmail242)\ **Post date:** [August 22, 2017, 7:11pm UTC](https://discuss.elastic.co/t/using-elasticsearch-to-capture-syslogs-windows/97963/1 "2017-08-22T19:11:35Z")
Hello, I am relatively new to using ElasticSearch and the other products available here on Elastic. As mentioned above I am running a windows server and have installed Kibana, ElasticSearch, Beats, and (unsuccessfully) logstash. I have another server that is sending the syslogs being generated to the server where ElasticSearch is held however I am unable to view them in a log file. The syslogs are being generated from a CISCO box and the only options given for export are destination and port both of which are verified to be working through wireshark. The issue I am having is that I cannot find a stored location for these logs and am not experienced enough to configure ElasticSearch or any of it's partner app's to capture and store these logs. Once stored I believe I can fumble through Kibana and any other program to set up what I need. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 19, 2017, 7:11pm UTC](https://discuss.elastic.co/t/using-elasticsearch-to-capture-syslogs-windows/97963/2 "2017-09-19T19:11:38Z")
Closed on September 19, 2017, 7:11pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.