Unable to get appropriate server status through heartbeat-571

Unable to get appropriate server status through heartbeat-571






 Solution Document


ICICI || Unable to get appropriate server status through heartbeat

Overview

General/Customer specific

General

Author

Ashna Rajput

Reviewer

Deepak,Tejaswi

Approver

 Ravi

Release date

20/09/2022

Product Version

8.5r5


Audience: CSG/TechWarriors/PAC/Platform/Product teams


What’s the Issue? 

Unable to get appropriate server status through heartbeat.

Describe the Issue in Detail

Requirement :

As the servers are in DMZ zone, we are unable to get the server status through heartbeat.

Have installed heartbeat in one of the target server and tried getting the data through it yet for all servers we are still not getting proper ping data., i.e target state is seen as down.



Solution Summary

Resolution Steps followed :
1. Gave different key value in redis output.
2. Identified how the data is coming to redis ( have seen in raw data that the status is up. however its not reflecting same in index)
3. Checked and got to know that analyser and shipper has connection issue on port 6379. Enabled same via ipTables.
4. At analyser end, as we are placing this heartbeat in one of the target server, we have added hardcoded entry of target server Ip to pass through rest of the heartbeat filter and then able to parse the proper and actual data. 




Corrective actions if any to avoid in future


More Help: .


References: 






    • Related Articles

    • Unable to get OHS KPI's - 854

      Solution Document ICICI || Unable to get OHS KPI's Overview General/Customer specific General Author Komali Buddha Reviewer NA Approver NA Release date 23/03/2023 Product Version 8.5r5 Audience: CSG/TechWarriors/PAC/Platform/Product teams What’s the ...

    • What we should check and fix if we get ‘Internal Server Error’

      Lot of times we suddenly get ‘Internal Server Error’ on the page as below. What all should we check and what we can fix? Most common reason for this screen is kibana is not able to reach Elasticsearch. You may want to check the cluster status.  If ...

    • Unable to collect Single line log from Target Server 321

      VuNet Systems Private Limited Unable to collect Single line log from Target Server 321 Overview General/Customer specific RBL Author Rachitha H V Reviewer Seema Approver Manoj  Release date Product Version 8.5r5 Audience: ...

    • Unable to install logbeat version 6.8 on target server 599

      VuNet Systems Private Limited  Solution Document Ticket #599  Overview General/Customer specific RBL Author Rachitha H V Reviewer Seema Approver Sendil Release date Product Version 8.5r5 Audience: CSG/TechWarriors/PAC/Platform/Product teams ...

    • Unable to install healthbeat on target windows server 595

      VuNet Systems Private Limited  Solution Document Ticket #595   Overview General/Customer specific RBL Author Rachitha H V Reviewer Seema Approver Sendil Release date Product Version 8.5r5 Audience: CSG/TechWarriors/PAC/Platform/Product teams What’s ...