Improvement of the graph

[ndeblauw]

Hi guys,

I'm a huge fan of the spike graph that you added to the overview page. This is really intuitive and easy to grasp an overview! Well done!!!

I would suggest to take it even one small step further, and not only use it for historical data, but also add today's errors to the graph. I imagine that this is more difficult to cache, and thus causes a heavier load on the server, but it really would add a lot of usability. Visual scanning of where to look for an issue in a multi-project environment will get a lot faster.

Below a quick visualisation of how I imagine it could look like.

[AlexVanderbist]

Interesting! I think this might even be considered a bug as you'd expect it would work like this. I'll add it to our internal issue tracker :)

[tomasvanrijsse]

It seems that this request has been implemented.
I can see the current day in the chart on the overview page.

[AlexVanderbist]

That's correct! We fixed this last week

[ndeblauw]

@AlexVanderbist (and team): and it is very appreciated! But it is not yet fully working, it seems. Please take the comments below as feedback on improving a function, and not as nagging of an annoying client. It's intended 100% as a helping hand.

I just re-invoked an (existing) error, and even though it is caught correctly (in the latest column), it doesn't show as a "today's spike"

Then I thought this might was because I reinvoked an existing error. So I invoked a "fresh" new error. Also this is correctly shown in the "latest" column, but doesn't show up as a today's spike.

[AlexVanderbist]

Hey @ndeblauw, thanks for the feedback, I've recently noticed this as well. This is due to caching (1 hour right now) and we're currently looking into getting this to work realtime without having a performance impact. I'll update this thread once I know more.