Task messages should be recorded in suite DBs.

[hjoliver]

(currently they're not).

[matthewrmshin]

@hjoliver I am currently in the middle of adding some new tables and doing some refactor to cylc.rundb. Please let me know the kind of things you would like to add.

[hjoliver]

@matthewrmshin - are you working on #864? I'll attempt to put a bit of thought into this tomorrow...

[matthewrmshin]

Not really. I am mainly working on #992 (and by extension #1052).

[benfitzpatrick]

E.g. cylc message -p WARN 'Oh no!' to be recorded in the suite database.

[hjoliver]

Non-output task messages can be sent with NORMAL, WARNING, or CRITICAL priority. This might seem a more-or-less useless feature. Thinking back, the intention was to log all messages in case of typos that caused output messages not to be recognized as outputs, and to allow deliberate recording of task errors centrally back when task job logs were not so easily accessed. There is probably little need for this now (although the first reason is still valid) but given that we do support such messages they should really be recorded in the DB as well as logged. Easy to do - the "message" column in the task_events table is already used for message outputs.

Changing the Issue title to "all messages" as there's no reason to single out WARNINGs...