Well, we plan to make this even more dense, e.g drop the "none" lines. One Problem with the current view is that to many of those automated background jobs (reporter, dns_resolver, etc.) create an entry in this list (because they create a session with the system), even when they don't change a thing.
What do you think would be a good number of "Last X sessions"? Is 20 Ok? Would it be better to have 50 or more? The reason why we try to keep this number low is that there are performance concerns (ie. the accumulation of these information takes some processing power)
Hi, last session of about 10 is good from my point of view, but I am not a business that has many people accessing the ASG to manage it. A seperate storage area of just changelogs would be good especially for people like auditors to review or me to recover from stuffups in config.
I think that question might be better posed to the likes of balfson and barryg who deal with business installations.
Hi, last session of about 10 is good from my point of view, but I am not a business that has many people accessing the ASG to manage it. A seperate storage area of just changelogs would be good especially for people like auditors to review or me to recover from stuffups in config.
I think that question might be better posed to the likes of balfson and barryg who deal with business installations.
