No data from filebeat cisco module

hi, guys
i'm new to this platform and want to do some cisco device monitoring , in my lab i've setted netflow and syslog on asa firewall , and now i can see data from netflow and make dashboards on kibana.
which now perplexed me is that i can find syslog messages in Observabillity--> logs like this:

but there is nothing on dashboard : [Filebeat Cisco] ASA Firewall

here is the configuration on /etc/filebeat/modules.d/cisco.yml , what's wrong and what i should do more?

     - module: cisco
          enabled: true
          var.input: syslog
          var.syslog_port: 9001
          var.log_level: 7

btw , the version is 7.8
the configuration on my firewall

logging enable
logging timestamp
logging standby
logging buffer-size 409600
logging console debugging
logging monitor debugging
logging buffered debugging
logging trap debugging
logging history debugging
logging asdm debugging
logging device-id ipaddress inside system
logging host inside 10.226.xx.xx 17/9001
logging debug-trace


flow-export destination inside 10.226.xx.xx 2055

elasticsearch, kibana, logstash and filebeat are all installed on one server

it seems the pipeline not working

Could you please share your complete filebeat.yml configuration here?



1 Like

hi shaunak
thanks for reply , here is my filebeat.yml configuration
after i turned the output from logstash to elasticsearch , the module working

- type: log
  enabled: true
    - /var/log/*.log
  level: debug
  review: 1
  json.keys_under_root: true
  json.overwrite_keys: true
  json.add_error_key: true
  json.message_key: message
  multiline.pattern: ^\[
  multiline.negate: false
  multiline.match: after

  index.number_of_shards: 1
setup.ilm.enabled: auto
setup.ilm.overwrite: true

  host: "localhost:5601"

  hosts: ["localhost:9200"]
  pipeline: geoip-info

  - add_host_metadata: ~
  - add_cloud_metadata: ~
  - add_docker_metadata: ~

after i turned output to elasticsearch , the dashboard get working now

but i can not find log meessage on this page now , is that a normal behavior ?
oservability --> logs

Is that your entire filebeat.yml file? I was expecting to see a filebeat.config.modules section as it is responsible for loading up external module configuration files, e.g. /etc/filebeat/modules.d/cisco.yml. Without that section it would seem that you are not using the Cisco module but instead are ingesting and parsing the logs using manual configuration, which is not ideal.

Also, could you call the Elasticsearch Get Index Template API and post the Filebeat 7.8 template here please? If it's large, please feel free to use or and post the link here instead.

1 Like

The cisco/asa fileset is removing the original message field in it's ingest pipeline, which is why you don't see it in the Kibana Logs UI. There is an issue to fix this in the future:

1 Like

really thanks , i will have a try

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.