Incidents not showing

Question

Incidents not showing

SamKr opened this issue 8 years ago · 6 comments

SamKr commented 8 years ago

The server's up and running and incidents are being reported. They show up in the DB so communication is OK.

However, in the webclient, the stats are shown but no actual incident information:

Tried multiple browsers. If you need login info for the dashboard I can provide them.

Answer 1 · 2018-03-15T13:16:55.000Z

Sorry for that. Was a bit too fast yesterday.

I'm on a winter vacation this week (downhill skiing), so I blame that.

Release v1.1.4 contains a fix.

The whisky/beer bar at the top of the mountain

Answer 2 · 2018-03-15T13:28:39.000Z

No problem =) Thanks for another quick assist. Great photo!

Do you have a paypal account so I can donate a whisky/beer for your time?

Related followup question; whenever I go to a specific application and look at the incidents, I see all incidents from all application (just like the main dashboard). Is that intended behaviour or am I missing a filtering setting or something?

Answer 3 · 2018-03-15T13:43:59.000Z

I'm just glad that you filed an issue. No need to donate.

That issue is related. We've changed the FindIncidents query a bit and had not regenerated the Typescript classes after the change. Hence the client side scripts did an incident search on the first page and the application page with outdated properties.

I've updated the zip file in the v1.1.4 release. Would you mind download it again and see if it works better.

Answer 4 · 2018-03-15T13:50:34.000Z

Grand, that fixed it.

Sorry but yet another followup question, when I zoom in on a report, I get no context info:

However I'm seeing more info in the DB. Perhaps related as well?

Answer 5 · 2018-03-15T14:27:48.000Z

Yep, it's part of the same changes I was working on before going here. I've made the context information searchable (will be part of the v2.0 release that we are working on). It can currently take up to one minute before context information is attached to the error report. Will be faster later on.

However, it was not processed properly in the background job, so I've corrected that. Updated the v1.1.4 release again.

Guess it's time to use source code branches better.

Answer 6 · 2018-03-15T14:42:05.000Z

Awesome, thanks yet again. Very thorough reports :)

Have a great vacation!