Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

    • Filebeat is used to forward logs from our application nodes to Logstash or Elasticsearch.
    • Download and install 
    • Download http_ca.crt to the server (preferably in the filebeat installation location)
    • Create a Logs folder inside Wildfly 
    • Edit Filebeat.yml file do the changes 

Check Elasticsearch:

  • Test Elasticsearch by accessing its URL in a browser:  curl -X GET "localhost:9200/"
  • If Elasticsearch is running correctly, you should see a JSON response with Elasticsearch cluster details.

Check Kibana:

  • Navigate to the "Discover" section and check if logs are being indexed in Elasticsearch.

Switch to Wildfly/bin/ and edit standalone.conf.bat add below line under wildfly folder

...

check if traces are visible in APM section of kibana  

restart filebeat

check for logs under filebeat in kibana 

...

env.HWC_API_LOGGING_FILE_NAME='E:/AppServer/wildfly-30.0.0.Final/wildfly-30.0.0.Final/Logs/hwc-api.log'                   


Check Elasticsearch:

  • Test Elasticsearch by accessing its URL in a browser:  curl -X GET "localhost:9200/"
  • If Elasticsearch is running correctly, you should see a JSON response with Elasticsearch cluster details.

Check Kibana:

  • Navigate to the "Discover" section and check if logs are being indexed in Elasticsearch.


5.4. Check Application Logs:

...