search

Lothiraldan / saltpad

A gui and cli to manage saltstack deployments
Other
659 stars 146 forks source link

Docs: Feature "Access jobs details easily" #153

Open guettli opened 8 years ago

guettli commented 8 years ago

I read the README.

What do you mean with "Access jobs details easily"?

Is it possible to see what has happened on a minion on a given date?

I search a web front-end for salt's job cache.

Does saltpad offer this?

Lothiraldan commented 8 years ago

Hi @guettli,

yes saltpad will helps you see the content of the job cache and details about each job.

You'll be able to list and filter the existing job in job cache https://github.com/Lothiraldan/saltpad/blob/saltpad_v1/screenshots/job_history_filtered.png?raw=true (old version screenshot). Be aware that they could be performance issues as the salt-api only allow retrieval of all jobs of nothing.

For an highstate, details will looks like https://github.com/Lothiraldan/saltpad/blob/master/screenshots/highstate_result.png, for a non-highstate result, it will looks like (old version screenshot) https://github.com/Lothiraldan/saltpad/blob/saltpad_v1/screenshots/job_result_raw_details.png?raw=true.

I hope it answer your questions

guettli commented 8 years ago

You said:

Be aware that they could be performance issues as the salt-api only allow retrieval of all jobs of nothing.

I guess you mean "all jobs OR nothing".

I guess storing the result-cache in a DB would be better. Should be possible: https://docs.saltstack.com/en/latest/topics/jobs/external_cache.html

I ask myself what a good architecture should look like: Access the result cache via salt-api or directly via DB.