On 23/05/17 06:39, Stuart Bishop wrote: > On 22 May 2017 at 20:02, roger peppe <roger.pe...@canonical.com> wrote: > >> not to show in the status history. Given that the motivation behind >> the proposal is to reduce load on the database and on controllers, I > > One of the motivations was to reduce load. Another motivation, that > I'm more interested in, was to make the status log history readable. > Currently it is page after page of noise about update-status running > with occasional bits of information. > > (I've leave it to others to argue if it is better to fix this when > generating the report or by not logging the noise in the first place) >
Since Juju 2.1.1, the juju show-status-log command no longer shows status-history entries by default. There's a new --include-status-updates flag which can be used if those entries are required in the output. There's also squashing of repeated log entries. These enhancements were meant to address the "I don't want to see it problem". The idea to not record it was meant to address the load issue (both retrieval and recording). As part of the ongoing performance tuning and scaling efforts, some hard numbers are being gathered to measure the impact of keeping update-status in the database. -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
