keepalive API: Inconsistent message field causes client to miss PING Success log

[gh-db]

Hi, thanks for your great project!

I found a small issue with the /process_send_keepalive/send_keepalive API:

The message field in the response sometimes returns "ping recored" and sometimes "ping recored." and sometimes "ping recored..".
This inconsistency causes client code to miss logging "PING Success" because it checks for an exact match(keepalive.get("message") == "ping recored").

Example responses:
{"success":true,"message":"ping recored.","data":"ping recorded","s":"ping11"}
{"success":true,"message":"ping recored.","data":"ping recorded","s":"ping12"}
{"success":true,"message":"ping recored..","data":"ping recorded","s":"ping13"}

Suggestion:
To avoid similar issues, I recommend that clients use substring or pattern matching (e.g., if "ping recored" in message) instead of exact string comparison when checking the message field.

Thank you!