Timeline for Observing progress of a distributed system
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2015 at 20:37 | vote | accept | Mare Infinitus | ||
| Jul 24, 2014 at 9:23 | history | edited | Mare Infinitus | CC BY-SA 3.0 |
clarified mixed infrastructure
|
| Jul 24, 2014 at 6:17 | history | edited | Mare Infinitus | CC BY-SA 3.0 |
edited title
|
| Jul 23, 2014 at 22:20 | answer | added | BobDalgleish | timeline score: 2 | |
| Jul 23, 2014 at 21:17 | history | edited | Mare Infinitus | CC BY-SA 3.0 |
added solution idea
|
| Jul 23, 2014 at 20:54 | history | edited | Mare Infinitus | CC BY-SA 3.0 |
added calculation for estimation
|
| Jul 23, 2014 at 20:33 | comment | added | Mare Infinitus | @Patrick Please have a look at the updated question | |
| Jul 23, 2014 at 20:31 | history | edited | Mare Infinitus | CC BY-SA 3.0 |
added more information
|
| Jul 23, 2014 at 20:20 | comment | added | Patrick | Some numbers would be good. 1, 10, 100, 1000 sites with controllers? Same with applications. Why is a database needed for the information on job progress? Can't you just put it in a ConcurrentHashMap and be done with it? | |
| Jul 23, 2014 at 20:07 | comment | added | Mare Infinitus | I have to confess that I have not heard of the most of those things. Will investigate, thank you! | |
| Jul 23, 2014 at 20:03 | comment | added | thorsten müller | Maybe something like syslog in combination with logstash or the whole elk stack (elasticsearch, logstash, kibana). You won't get around the extra traffic as such but most of those modules can be installed relative leightweight on the client with a very responsive logserver running Redis, logstash and elastic. | |
| Jul 23, 2014 at 19:56 | history | asked | Mare Infinitus | CC BY-SA 3.0 |