elk stack - filebeat is sending log directly to elastic search not to logstash -

-

i facing problem since have deleted indices . executed following command 

curl -xdelete 'http://localhost:9200/*'

filebeat.yml

filebeat:   prospectors:     -      paths:       - /var/log/syslog     - input_type : log       document_type: syslog   registry_file: /var/lib/filebeat/registry output:   logstash:     hosts: ["127.0.0.1:5044"]     bulk_max_size: 1024  shipper: logging:   files:     rotateeverybytes: 10485760 # = 10mb

and logstash config files input config

   input {       beats {         port => 5044       }     }

and output config

  output {       elasticsearch {         hosts => ["localhost:9200"]         sniffing => true         manage_template => false         index => "%{[@metadata][beat]}-%{+yyyy.mm.dd}"         document_type => "%{[@metadata][type]}"       }     }

problem logs not coming through logstash , these coming directly because can not see new field added in kibana , in case of apche-access log there log value of type.

you may have syntactical error in filebeat config, try changing

 - input_type : log

to

input_type : log

that - messing config declaring second prospector. if logstash processing done type, improperly typed logs make elasticsearch through logstash no parsing done.


Comments

Post a Comment

Popular posts from this blog

iis - ASP.Net Core CreatedAtAction in HttpPost action returns 201 but entire request ends with 500 -

-
i'm following[1] setting first .net core webapi (moving "old" webapi). when httppost action, in tutorial: [httppost] public iactionresult create([frombody] todoitem item) { if (item == null) { return badrequest(); } todoitems.add(item); return createdataction("gettodo", new { id = item.key }, item); } i httperror 500 after exiting controller. createdataction returns proper object status code 201 expect, , after method exits server somehow turns 500. don't seem able step rest of pipeline. trace gives me following error: 81. -general_request_entity 82. -notify_module_completion 83. -module_set_response_error_status [warning] 171ms modulename aspnetcoremodule notification execute_request_handler httpstatus 500 httpreason internal server error httpsubstatus 0 errorcode operation completed successfully. (0x0) configexcepti...
Read more

Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project.Error occurred in starting fork -

-
i searched on internet provided answers did not in building project. the error starting fork. tried following methods: mvn clean install -u when searched, people said because of java 7 , should work java 6. using java 6 only. some said set surefire plugin this: <groupid>org.apache.maven.plugins</groupid> <artifactid>maven-surefire-plugin</artifactid> <version>2.5</version> <configuration> <skiptests>false</skiptests> <testfailureignore>true</testfailureignore> <forkmode>once</forkmode> </configuration> the actual error is: [error] failed execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project junitcategorizer.instrument: error occurred in starting fork, check output in log -> [help 1] org.apache.maven.lifecycle.lifecycleexecutionexception: failed execute goal org.apache.maven.plugins:maven-surefire-plugin:2...
Read more