I think part of this enhancement requires stuff on the Kibana end, but I think the work would start with Heartbeat. If this is incorrect please feel free to close, and I can open in Kibana repo.

Describe the enhancement:

Currently when there is an error somewhere in the actual browser source configuration (i.e. syntax error), the monitor runs, but exists with an error code. These error never make it to the Kibana interface. This makes it hard for users who are writing the monitors, but don't have access to the underlying heartbeat to see the logs.

Describe a specific use case for the enhancement or feature:

If you have users writing the playwright source, but they don't have access to heartbeat to view the logs, then they need to contact the person who has access to Heartbeat to pull the logs.

Example: using zip_url source, user can write the code to a git repo, but never actually have access to heartbeat.

Here is an example of the errors I'd like to see show up in Kibana from Heartbeat:

{"level":"info","timestamp":"2021-09-14T18:35:21.848Z","caller":"synthexec/synthexec.go:224","message":"stderr: SyntaxError: Invalid or unexpected token"}

Note; the errors I'm talking about specifically refer to the source section, I wouldn't expect heartbeat to show errors within its own config.