927 status API endpoint and UI

[GustaafL]

Description

API endpoint sensor/<id>/status that will give the status of a sensor. This is checked by confirming data has been posted within an expected time before now (for measurements - forecasts & schedules will be treated next).

Look & Feel

The new page at http://localhost:5000/assets/ID/status/ is the main contribution. It shows a traffic light (green / red) system to indicate which sensor of the asset has "stale" data.

Buttons to reach this page have been added to the account page and asset page (for the shown asset and also for child assets)

How to test

Go to an account page, an asset page or the assets page and click on the "status" button.

Further Improvements

• Handle staleness for schedules / forecasts
• Do not show all sensors, maybe only those which have status_specs?
• Add relevant sensors from flex_context
• Add caching for faster loads (plus "Check now" button?)

Related Items

Related issue: #927

Flex-context: #1016

• I agree to contribute to the project under Apache 2 License.
• To the best of my knowledge, the proposed patch is not based on code under GPL or other license that is incompatible with FlexMeasures

[GustaafL]

Currently the UI shows a list of the last values in the table (not formatted properly yet). Issue #927 describes a tooltip that might show the last values, since there is quite some space it might be better to show them in the table directly.

I would suggest showing a list of the last values and the timestamps in the table. They could also be in a tooltip. @nhoening Please let me know what your preferred option is.

[nhoening]

Currently the UI shows a list of the last values in the table (not formatted properly yet). Issue #927 describes a tooltip that might show the last values, since there is quite some space it might be better to show them in the table directly.

I would suggest showing a list of the last values and the timestamps in the table. They could also be in a tooltip. @nhoening Please let me know what your preferred option is.

I agree it is interesting to show for now. Let's keep it.
As I said earlier, the page will grow and the extra space might be taken by other things, and then we do not want to show too much information. When we remove it, one can always go to the sensor page and have a look.

[nhoening]

Good start, although I recommend not creating a dedicated REST endpoint.

Review was made on a phone, excuses if I overlooked something.

[GustaafL]

As discussed with @Flix6x:

• If there are values shown on the status page it's better to show the times of the values than the values themselves.
• For the status we want to know what the latest possible times for which there should be values are and if those values are there. In the case of posted data this is just the last 4 values but for day ahead prices the status page needs to show if the prices for the next day have been added at the time they are expected. (This might be out of scope and should be a future improvement)
• The structure, functions and tests should already be made with the above improvements in mind.

I will refactor the code so there is no new endpoint and make a utils function or staticmethod that can be used to query the relevant status data.

[nhoening]

Another good step, thanks for the extra testing.

I have to be a stickler about naming and docstrings, though.

And there is also something I would improve about staleness search when thinking about the existence of forecasts in the sensor data.

[nhoening]

Almost there. Two issues in review next to code.
Also, when I look at the UI, namely the asset page, I miss two things:

• The asset page should also show the status column in the table for its child assets ("All child assets for... ")
• And it should have a button for its own status. There is already a double button at the top left, not sure how an added "Status" button would look there (or move the content to the right). But let's try.

[nhoening]

Great thanks!

[Flix6x]

Just noticing that the changelog will need a small fix.

[Flix6x]

PR #941