Cosimo Damiano Prete

It seems to cause issues also when, from the homepage, the button to jump to the journal is pressed. The journal is then empty rather than showing all the events...

Hi @ulischulte Basically I can't explain to myself why there are those gaps as well as potential missed updates in the journal.

Not directly. I mentioned it, because the event is named INFO_CHANGED and its payload is the composed by info returned by the info endpoint. At least, for what I can...

> Hi [@cdprete](https://github.com/cdprete) I see. You're right, any InstanceInfoChangedEvent should trigger the InfoUpdater and result in a new entry in the journal. Since we're not able to reproduce your issue,...

> `InfoUpdater` in backend is called in whatever `spring.boot.admin.monitor.info-interval` (default: 1m) is set to. This is mainly used to check every minute wether the instance is still up. In addition...

> In this example I have set `lifetime` to 0s and `interval` to 10s. As you can see, every ten seconds, the info is updated. > > Mmm, have you...

> > Good to know this, but it doesn't explain why there are gaps in the events. > > I have set the update time to 10s and I get...

Can you please try with it? My suspect, as written initially in the ticket, it's that it may be caused by the clustering. If even with that you can't reproduce...

Hello. To confirm once more that in the journal there are missing entries, please see the following: where the claim is that the instances are up since roughly 40m, but...

Hello @ulischulte @SteKoe. For what we discussed so far, you told me that what gets displayed there is coming from the `auditevents` endpoint of Spring Boot Actuator. One of my...