Improvement for audit log forward

[AllForNothing]

For the below case:

After the forward endpoint is configured and skip DB is enabled, the log will be recorded in core.log after the forward endpoint hangs midway. In this case, I think the bad experience is that unless the user takes the initiative to read the core.log or takes the initiative to ping the forward endpoint, he will not know that the forward endpoint is down.

so, maybe we can ping the forward endpoint every time when the user enters the config page. if the forward endpoint is down, then show a warning.

[stonezdj]

If add a function to ping a syslog endpoint, it could bring a security issue.

[AllForNothing]

Removed 2.7 label

[github-actions[bot]]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.