Filebeat httpjason input

[pankaj]

I tried configure the test httpjson input but that failing filebeat service to start.

filebeat.inputs:

Fetch your public IP every minute.

• type: httpjson
  url: https://api.ipify.org/?format=json
  interval: 1m
  processors:
  • decode_json_fields
    fields: [message]
    target: json

[MarianaD]

hi @pankaj, what do you mean by filebeat failing to start, can you provide us with the filebeat log? That might provide some information on the issue you might be having (you can also set the logging level to debug for more information).

[pankaj]

Mariana

Please find below the service status details

root@elk-filebeat:/home/elkadmin# service filebeat status
● filebeat.service - Filebeat sends log files to Logstash or directly to Elasticsearch.
Loaded: loaded (/lib/systemd/system/filebeat.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-11-18 22:12:42 UTC; 5h 26min left
Docs: https://www.elastic.co/products/beats/filebeat
Process: 1766 ExecStart=/usr/share/filebeat/bin/filebeat --environment systemd $BEAT_LOG_OPTS $BEAT_CONFIG_OPTS $BEAT_PATH_OPTS (code=exited, status=1/FAILURE)
Main PID: 1766 (code=exited, status=1/FAILURE)

Nov 18 22:12:42 elk-filebeat systemd[1]: filebeat.service: Service hold-off time over, scheduling restart.
Nov 18 22:12:42 elk-filebeat systemd[1]: filebeat.service: Scheduled restart job, restart counter is at 9.
Nov 18 22:12:42 elk-filebeat systemd[1]: Stopped Filebeat sends log files to Logstash or directly to Elasticsearch..
Nov 18 22:12:42 elk-filebeat systemd[1]: filebeat.service: Start request repeated too quickly.
Nov 18 22:12:42 elk-filebeat systemd[1]: filebeat.service: Failed with result 'exit-code'.
Nov 18 22:12:42 elk-filebeat systemd[1]: Failed to start Filebeat sends log files to Logstash or directly to Elasticsearch..