Hi,
Somedays back I was getting the logs in kibana. Then since two days the logs are getting into filebeat logs but I could not see them on Kibana although I have not made any changes in any file.
Please help me as soon as possible.
Hi,
Somedays back I was getting the logs in kibana. Then since two days the logs are getting into filebeat logs but I could not see them on Kibana although I have not made any changes in any file.
Please help me as soon as possible.
Hi!
Could you provide more information about your setup/configuration etc? Anything interesting in what filebeat logging? Are events successfully sent to Elasticsearch?
C.
#=========================== 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
** # Change to true to enable this input configuration.**
** enabled: true**
** json.keys_under_root: true**
** json.add_error_key: true**
** json.message_key: log**
** # Paths that should be crawled and fetched. Glob based paths.**
** paths:**
** - /var/atlassian/application-data/jira/log/*.log**
** #- c:\programdata\elasticsearch\logs***
** # Configure the file encoding for reading files with international characters**
** # following the W3C recommendation for HTML5 (http://www.w3.org/TR/encoding).**
** # Some sample encodings:**
** # plain, utf-8, utf-16be-bom, utf-16be, utf-16le, big5, gb18030, gbk,**
** # hz-gb-2312, euc-kr, euc-jp, iso-2022-jp, shift-jis, ...**
** # encoding: utf-8**
** # Exclude lines. A list of regular expressions to match. It drops the lines that are**
** # matching any regular expression from the list.**
** #exclude_lines: ['^DBG']**
** # Include lines. A list of regular expressions to match. It exports the lines that are**
** # matching any regular expression from the list.**
** #include_lines: ['^ERR', '^WARN']**
In filebeat log file I can lot many errors as:
ERROR readjson/json.go:52 Error decoding JSON: invalid character 't' after object key:value pair
Error decoding JSON: invalid character 'a' looking for beginning of value
But I an getting some good data as well so I am expecting the correct data to be displayed on kibana which I cannot see.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.