Filebeat sends no Logs to ELK

[Elasticisti]

Hello,

ELK Version: 9.1.0
Elastic Agent 9.1.0
Filebeat Version 9.1.0

I have installed filebeat and runs:

I have configured it on this way to send the atlassian Logs to ELK:

Only output.elasticsearch is activated:

No modules are activated ...

After restarting the service I do not find any filebeat logs in KIBANA:

Have I missed some requested steps?

I see filebeat logs, these are however from the Agent, it is not OK to use a Stand Alone Agent and a seperated filebeat Service on the same host?

If a Stand Alone Agent is also able to ingest Atlassian Logs from a separated directory, it could also be a solution for me.

According to the Atlassian Support Filebeat-Input has to be configured as follows:

 filebeat.inputs:
- type: log
  enabled: true
  paths:
    - /path/to/jira/logs/*.log

In my config I have used filestream because I have read "log" is already deprecated and should not be used.

Thank you for a short confirmation.

Best Regards

EI

[Elasticisti]

After some testing I have added *.log to my atlassian path and restarted filebeat.
This has not helped either. No Atlassian-Audit data arrive.

Shall we configure the fields for Filebeat manually or would Elasticsearch recognise them automatically as this format is suitable for proper "machine-reading"?

[RainTown (Kevin Maguire)]

Please don’t post images of text. Post the text itself. Cut and paste are your friend, as are backticks.

[Elasticisti]

@RainTown Oh sorry, I see, I will do it, where possible ...

You find enclosed the filebeat-config.

# ============================== 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.

# filestream is an input for collecting log messages from files.
- type: filestream

  # Unique ID among all inputs, an ID is required.
  id: XXXXXXXXXX-jira-test

  # Change to true to enable this input configuration.
  enabled: true

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /var/atlassian/application-data/jira/log/audit/*.log
    #- c:\programdata\elasticsearch\logs\*

  # Exclude lines. A list of regular expressions to match. It drops the lines that are
  # matching any regular expression from the list.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #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.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #include_lines: ['^ERR', '^WARN']

  # 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.
  #prospector.scanner.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

# journald is an input for collecting logs from Journald
#- type: journald

  # Unique ID among all inputs, if the ID changes, all entries
  # will be re-ingested
  #id: my-journald-id

  # The position to start reading from the journal, valid options are:
  #  - head: Starts reading at the beginning of the journal.
  #  - tail: Starts reading at the end of the journal.
  #    This means that no events will be sent until a new message is written.
  #  - since: Use also the `since` option to determine when to start reading from.
  #seek: head

  # A time offset from the current time to start reading from.
  # To use since, seek option must be set to since.
  #since: -24h

  # Collect events from the service and messages about the service,
  # including coredumps.
  #units:
    #- docker.service

# ============================== 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: 1
  #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 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` command.
#setup.dashboards.enabled: false

# The URL from where to download the dashboard archive. By default, this URL
# has a value that 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"

  # 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:

# =============================== 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: ["172.30.68.64:9200"]

  # Performance preset - one of "balanced", "throughput", "scale",
  # "latency", or "custom".
  preset: balanced

  # Protocol - either `http` (default) or `https`.
  #protocol: "https"

  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  username: "un"
  password: "pw"

# ------------------------------ Logstash Output -------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost: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 =================================
processors:
  - add_host_metadata:
      when.not.contains.tags: forwarded
  - add_cloud_metadata: ~
  - add_docker_metadata: ~
  - add_kubernetes_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",
# "publisher", "service".
#logging.selectors: ["*"]

# ============================= X-Pack 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.
#monitoring.enabled: false

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch outputs are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:

# ============================== Instrumentation ===============================

# Instrumentation support for the filebeat.
#instrumentation:
    # Set to true to enable instrumentation of filebeat.
    #enabled: false

    # Environment in which filebeat is running on (eg: staging, production, etc.)
    #environment: ""

    # APM Server hosts to report instrumentation results to.
    #hosts:
    #  - http://localhost:8200

    # API Key for the APM Server(s).
    # If api_key is set then secret_token will be ignored.
    #api_key:

    # Secret token for the APM Server(s).
    #secret_token:


# ================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true

[stephenb (Stephen Brown)]

@Elasticisti

Also there filebeat and Elastic Agent are 2 different things...

If you are already running and Elastic Agent on a host there is no reason to run filebeat ... just use one of the Elastic Agent Integrations.

Now back to your question

Did you run filebeat setup -e I suspect you did not therefor the Data View was not created...

Filebeat quick start: installation and configuration | Beats

Filebeat quick start: installation and configuration | Beats

I would review the Quick start

In short the logs are probably flowing but you have no data view

You could check in

Kibana - Stack Management -> Index Management - > Data Streams and see if there is one named filebeat-9.0.0

[Elasticisti]

Hi Stephen,

thank you.

Unfortunately, I have no such datastream:

I try with

filebeat setup -e 

I did not run it ...

Regards

EI

[Elasticisti]

As I run the command, I have got a lot of Logs on the console and a real error:

{"log.level":"error","@timestamp":"2025-08-04T21:33:17.708+0200","log.origin":{"function":"github.com/elastic/beats/v7/libbeat/cmd/instance.handleError","file.name":"instance/beat.gofile.line":1355},"message":"Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at http://172.30.68.64:9200: Get \"http172.30.68.64:9200\": EOF]","service.name":"filebeat","ecs.version":"1.6.0"}
Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at http://172.30.68.64:9200: Get "http://172.30.68.64:9200": EOF]

Somehow Filebeat cannot reach ELK ... Hmmm.

I will check it out.

[stephenb (Stephen Brown)]

Is elasticsearch running on https?

What do you get...

curl -k -v -u user:pw https://172.30.68.64:9200

[Elasticisti]

Hi Stephan,

thank you , the result:

[root@ESXELX1377 filebeat]# curl -k -v -u elastic:XXXXXXXXXXXXXXX https://172.30.68.64:9200
*   Trying 172.30.68.64:9200...
* Connected to 172.30.68.64 (172.30.68.64) port 9200 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Unknown (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Unknown (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=alma92vorlage
*  start date: Jul 31 12:47:16 2025 GMT
*  expire date: Jul 31 12:47:16 2027 GMT
*  issuer: CN=Elasticsearch security auto-configuration HTTP CA
*  SSL certificate verify result: self-signed certificate in certificate chain (19), continuing anyway.
* Server auth using Basic with user 'elastic'
* TLSv1.2 (OUT), TLS header, Unknown (23):
> GET / HTTP/1.1
> Host: 172.30.68.64:9200
> Authorization: Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> User-Agent: curl/7.76.1
> Accept: */*
>
* TLSv1.2 (IN), TLS header, Unknown (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Unknown (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< X-elastic-product: Elasticsearch
< content-type: application/json
< content-length: 534
<
{
  "name" : "ESXELX1300",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "cnk1pzR2Q1KKwszRXXXXXXXXX",
  "version" : {
    "number" : "9.1.0",
    "build_flavor" : "default",
    "build_type" : "rpm",
    "build_hash" : "00e7d33bf08f1476229d9d1642e2da46cfebdXXXXX",
    "build_date" : "2025-07-23T22:09:53.891289976Z",
    "build_snapshot" : false,
    "lucene_version" : "10.2.2",
    "minimum_wire_compatibility_version" : "8.19.0",

[Elasticisti]

@stephenb,

as I have a standalone agent as well, I would not invest more time to filebeat.

Which integration can be used to "import" Logs from an additional path

/var/atlassian/application-data/jira/log/audit/*.log

"Upload a file" seems to be OK.

I will try to add this integration to my "agent policy"

Regards

[stephenb (Stephen Brown)]

So that above shows that your Elasticsearch is running on HTTPS so all connection will need to be via HTTPS that is why filebeat does not work.

Well if you want Jira Audi Logs, I would try that.

Atlassian Jira Integration | Elastic integrations

There is always Custom Logs as well, I recommend looking at the available integrations.

Elastic integrations | Elastic integrations

[Elasticisti]

Thank you Stephan!