I am new in ElasticSearch, please help me on this.
When my log is updating(SOA Admin log), even single line added, that time My complete Kibana dashboard (discover tab) time option is updating with the current timestamp as shown in below screenshot.
Might be as I understood filebeat is reading the log every time from the scratch.
so due to that, I am not able to draw the graph because timestamp contain only one day value.
Below is my machine description:
OS : Linux 7
ELK: 6.4
tools : elasticsearch, kibana, logstash, filebeat.
####<Jul 15, 2018 5:30:56 PM CDT> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <04a8865b-6081-470c-ba5a-e5d69fa34bc8-00000286> <1531693856023> <Received exception while creating connection for pool "LocalSvcTblDataSource": Listener refused the connection with the following error:
java.sql.SQLException: Listener refused the connection with the following error:
Caused By: oracle.net.ns.NetException: Listener refused the connection with the following error:
####<Jul 15, 2018 5:30:56 PM CDT> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <04a8865b-6081-470c-ba5a-e5d69fa34bc8-00000287> <1531693856946> <Received exception while creating connection for pool "SOALogDataSource": Listener refused the connection with the following error:
java.sql.SQLException: Listener refused the connection with the following error:
Caused By: oracle.net.ns.NetException: Listener refused the connection with the following error:
####<Jul 15, 2018 5:30:57 PM CDT> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <04a8865b-6081-470c-ba5a-e5d69fa34bc8-00000288> <1531693857399> <Received exception while creating connection for pool "mds-owsm": Listener refused the connection with the following error:
java.sql.SQLException: Listener refused the connection with the following error:
Caused By: oracle.net.ns.NetException: Listener refused the connection with the following error:
####<Jul 15, 2018 5:30:57 PM CDT> <[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <04a8865b-6081-470c-ba5a-e5d69fa34bc8-00000289> <1531693857834> <Received exception while creating connection for pool "mds-soa": Listener refused the connection with the following error:
java.sql.SQLException: Listener refused the connection with the following error:
Caused By: oracle.net.ns.NetException: Listener refused the connection with the following error:
####<Jul 15, 2018 5:30:58 PM CDT> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <04a8865b-6081-470c-ba5a-e5d69fa34bc8-0000028a> <1531693858298> <Received exception while creating connection for pool "opss-audit-DBDS": Listener refused the connection with the following error:
java.sql.SQLException: Listener refused the connection with the following error:
Caused By: oracle.net.ns.NetException: Listener refused the connection with the following error:
####<Jul 15, 2018 5:30:58 PM CDT> <[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <04a8865b-6081-470c-ba5a-e5d69fa34bc8-0000028b> <1531693858766> <Received exception while creating connection for pool "opss-audit-viewDS": Listener refused the connection with the following error:
java.sql.SQLException: Listener refused the connection with the following error:
Caused By: oracle.net.ns.NetException: Listener refused the connection with the following error:
####<Jul 15, 2018 5:30:59 PM CDT> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <04a8865b-6081-470c-ba5a-e5d69fa34bc8-0000028c> <1531693859309> <Received exception while creating connection for pool "opss-data-source": Listener refused the connection with the following error:
java.sql.SQLException: Listener refused the connection with the following error:
Caused By: oracle.net.ns.NetException: Listener refused the connection with the following error:
####<Jul 15, 2018 5:31:01 PM CDT> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <04a8865b-6081-470c-ba5a-e5d69fa34bc8-0000028e> <1531693861024> <Received exception while creating connection for pool "LocalSvcTblDataSource": Listener refused the connection with the following error:
java.sql.SQLException: Listener refused the connection with the following error:
Caused By: oracle.net.ns.NetException: Listener refused the connection with the
No, I think filebeat is re-reading the entire file each time. Below is the Filebeat config file :
#=========================== Filebeat inputs =============================
filebeat.inputs:
# Below are the input specific configurations.
- type: log
# Change to true to enable this input configuration.
enabled: true
# Paths that should be crawled and fetched. Glob based paths.
#include_lines: ['^####']
#exclude_lines: ['<Info>']
tags: ["soa-server-logs"]
paths:
#- /var/log/secure
#- /var/log/messages
- /home/app/soft/soa_logs/wls_soatx1.out
- /home/app/soft/soa_logs/soatx_domain.log
- /home/app/soft/soa_logs/AdminServer.log
input_type: log
# Exclude files. A list of regular expressions to match. Filebeat drops the files that
# are matching any regular expression from the list. By default, no files are dropped.
#exclude_files: ['.gz$']
# Optional additional fields. These fields can be freely picked
# to add additional information to the crawled log files for filtering
#fields:
# level: debug
# review: 1
### Multiline options
# Multiline can be used for log messages spanning multiple lines. This is common
# for Java Stack Traces or C-Line Continuation
# The regexp Pattern that has to be matched. The example pattern matches all lines starting with [
#multiline.pattern: ^\[
# Defines if the pattern set under pattern should be negated or not. Default is false.
#multiline.negate: false
# Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
# that was (not) matched before or after or as long as a pattern is not matched based on negate.
# Note: After is the equivalent to previous and before is the equivalent to to next in Logstash
#multiline.match: after
#============================= Filebeat modules ===============================
filebeat.config.modules:
# Glob pattern for configuration loading
path: ${path.config}/modules.d/*.yml
# Set to true to enable config reloading
reload.enabled: false
# Period on which files under path should be checked for changes
#reload.period: 10s
#==================== Elasticsearch template setting ==========================
setup.template.settings:
index.number_of_shards: 3
#index.codec: best_compression
#_source.enabled: false
#================================ 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:
# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]
# Optional fields that you can specify to add additional information to the
# output.
#fields:
# env: staging
#============================== Dashboards =====================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here, or by using the `-setup` CLI flag or the `setup` command.
#setup.dashboards.enabled: false
# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:
#============================== 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
# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
#host: "localhost:5601"
#============================= Elastic Cloud ==================================
# These settings simplify using filebeat with the Elastic Cloud (https://cloud.elastic.co/).
# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:
# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:
#================================ 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: ["XX.XXX.XX.XX:5044"]
# Optional SSL. By default is off.
# List of root certificates for HTTPS server verifications
ssl.certificate_authorities: ["/etc/pki/tls/certs/logstash-forwarder.crt"]
# Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
# Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
#================================ Logging =====================================
# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
logging.level: debug
logging.path: "/var/log/filebeat"
logging.name: filebeat.log
# 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: ["*"]
Are you sure your application is not rotating log files causing them to be read again? I.e it move adminserver.log to adminserver.log.1 then adminserver.log.2 etc etc?
first, I would like to tell you it is my Lab server. on daily basis, i copy the log from my real environment server to lab server for POC.
yes, my application becomes log as adminserver.log.1, adminserver.log.2., etc, etc.
but what I did, i copied all the log data from all the files to one single file.
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.
