Beat Check Event_log message could include the path to the event_log

[strawgate]

Describe the enhancement:
The beat event_data logger is new and for many customers, especially those using docker, they find themselves confused as to where to go next to troubleshoot their data.

"message":"Cannot index event (status=400): dropping event! Look at the event log to view the event and cause."

It would be nice if we included some info here as to where the event log is located so the user knows where to head next for troubleshooting their issue. This is also true with Elastic Agent where a user has to download a diagnostic from Fleet to obtain the event_data.

Or alternatively, we could change the error message to include a reference to the event_data logger so that when a user searches "filebeat event_data logger", the user finds the right documentation.

References:

• https://discuss.elastic.co/t/where-is-the-filebeat-event-log/371789

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)