# Filebeat is sending data from a Different Location **URL:** \ **Category:** Beats\ **Created:** [July 25, 2019, 12:04pm UTC](https://discuss.elastic.co/t/filebeat-is-sending-data-from-a-different-location/192236 "2019-07-25T12:04:31Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mostafa\_kamal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mostafa_kamal/32/50914_2.png) [@mostafa\_kamal](https://discuss.elastic.co/u/mostafa_kamal)\ **Post date:** [July 25, 2019, 12:04pm UTC](https://discuss.elastic.co/t/filebeat-is-sending-data-from-a-different-location/192236/1 "2019-07-25T12:04:31Z")
Hi, I am trying to send log from one server to logstash server. But, I found that, log is being sent from other location. What did I miss? filebeat.yml ######################Filebeat Configuration Example ######################### #This file is an example configuration file highlighting only the most common #options. The filebeat.reference.yml file from the same directory contains all the #supported options with more comments. You can use it as a reference. # #You can find the full configuration reference here: #[https://www.elastic.co/guide/en/beats/filebeat/index.html](https://www.elastic.co/guide/en/beats/filebeat/index.html) #For more available modules and options, please see the filebeat.reference.yml sample #configuration file. #=========================== Filebeat inputs ============================= filebeat.inputs: #Each - is an input. Most options can be set at the input level, so #you can use different inputs for various configurations. #Below are the input specific configurations. - type: log #================================ General ===================================== #The name of the shipper that publishes the network data. It can be used to group #all the transactions sent by a single shipper in the web interface. #name: #name: #The tags of the shipper are included in their own field with each #transaction published. #tags: ["service-X", "web-tier"] tags: ["mxtrace-log"] #Optional fields that you can specify to add additional information to the #output. #fields: #env: staging #============================== Kibana ===================================== #Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API. #This requires a Kibana endpoint configuration. setup.kibana: #Kibana Host #Scheme and port can be left out and will be set to the default (http and 5601) #In case you specify and additional path, the scheme is required: [http://localhost:5601/path](http://localhost:5601/path) #IPv6 addresses should always be defined as: https://[2001:db8::1]:5601 host: "[elk.devops-bjit.com:5601](http://elk.devops-bjit.com:5601)" #Kibana Space ID #ID of the Kibana Space into which the dashboards should be loaded. By default, #the Default Space will be used. #space.id: #================================ Outputs ===================================== #Configure what output to use when sending the data collected by the beat. #-------------------------- Elasticsearch output ------------------------------ #output.elasticsearch: #Array of hosts to connect to. #hosts: ["localhost:9200"] #Optional protocol and basic auth credentials. #protocol: "https" #username: "elastic" #password: "changeme" #----------------------------- Logstash output -------------------------------- output.logstash: #The Logstash hosts hosts: ["[elk.devops-bjit.com:5044](http://elk.devops-bjit.com:5044)"] #Optional SSL. By default is off. #List of root certificates for HTTPS server verifications #ssl.certificate\_authorities: ["/etc/pki/root/ca.pem"] #Certificate for SSL client authentication #ssl.certificate: "/etc/pki/client/cert.pem" #Client Certificate Key #ssl.key: "/etc/pki/client/cert.key" #================================ Processors ===================================== #Configure processors to enhance or manipulate events generated by the beat. processors: - add\_host\_metadata: ~ - add\_cloud\_metadata: ~ #================================ Logging ===================================== #Sets log level. The default log level is info. #Available log levels are: error, warning, info, debug #logging.level: debug #At debug level, you can selectively enable logging only for some components. #To enable all selectors use ["_"]. Examples of other selectors are "beat", #"publish", "service". #logging.selectors: ["_"] #============================== Xpack Monitoring =============================== #filebeat can export internal metrics to a central Elasticsearch monitoring #cluster. This requires xpack monitoring to be enabled in Elasticsearch. The #reporting is disabled by default. #Set to true to enable the monitoring reporter. #xpack.monitoring.enabled: false #Uncomment to send the metrics to Elasticsearch. Most settings from the #Elasticsearch output are accepted here as well. Any setting that is not set is #automatically inherited from the Elasticsearch output configuration, so if you #have the Elasticsearch output configured, you can simply uncomment the #following line. #xpack.monitoring.elasticsearch: #================================= Migration ================================== #This allows to enable 6.7 migration aliases #migration.6\_to\_7.enabled: true But from Kibana, I am finding this path. ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/f/ff7ae73a9d518770ae0ba5ad9c9bc8c9a565146b.png) Can you please, help? ---
**Author:** ![mostafa\_kamal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mostafa_kamal/32/50914_2.png) [@mostafa\_kamal](https://discuss.elastic.co/u/mostafa_kamal)\ **Post date:** [July 26, 2019, 5:09am UTC](https://discuss.elastic.co/t/filebeat-is-sending-data-from-a-different-location/192236/2 "2019-07-26T05:09:47Z")
Is there anyone for help? ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [July 26, 2019, 5:43am UTC](https://discuss.elastic.co/t/filebeat-is-sending-data-from-a-different-location/192236/3 "2019-07-26T05:43:28Z")
Hi there, apologies but it is very difficult to read / understand your config .. filebeat.yml because you did not paste it as formatted code (the symbol `` above) plus you did not include your version of filebeat and elasticsearch. Have you enabled any modules? That looks like a default path from the system module. [https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-modules.html](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-modules.html) [https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html) Plus if at some point filebeat already loaded the data it will only load it once because it keeps track of the logs it's already loaded, that data is kept in the `data` directory under filebeat if you want to reload a file you have to clear that data directory ... _do not do that in production._ ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 23, 2019, 7:43am UTC](https://discuss.elastic.co/t/filebeat-is-sending-data-from-a-different-location/192236/4 "2019-08-23T07:43:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.