Fix report_broken_client about munkireport-php HOT 11 CLOSED

I'd like to turn some attention on this and implement at least a workaround

With the number of modules growing this will be becoming more important. Related discussion

from munkireport-php.

Ok, I'm thinking about an error/warning model that is accessible to all modules. It will collect errors and warnings that are triggered on a client. There needs to be a system that sets and resets errors in this table. We can then use this table for report_broken_client data as well.

I would like a simple table like:
id
serial_number
type - error, warning or some other type
module - module that triggered the error
message - short description of the error

We could put the errors on the dashboard and update them periodically.

from munkireport-php.

90bda14 does this arrange with what you had in mind?

from munkireport-php.

*report_broken_client should be bash, sorry

from munkireport-php.

I already wrote something similar, maybe you can build on that: 3b42f09

from munkireport-php.

sure but all I had in mind is done or almost done!
What else do you feel is missing? pointing other scripts to it?

from munkireport-php.

There are still some loose ends: for instance I don't know when to reset the messages for a particular machine.
Other scripts could use this framework as well, so we can show all errors and warnings together.

from munkireport-php.

This is already in place

from munkireport-php.

What is already in place? I just revisited the messages module, but is still a little rough.

from munkireport-php.

it is not, my bad. I confused this issue with the preflight script handling thread

from munkireport-php.

Fixed with bd9f972

from munkireport-php.