espenhh / panopticon Goto Github PK

SuccessrateSensor threw an exception in our logs, and it seems it actually stopped the Panopticon client library from sending more data to the server. There was no stack trace, but the following text appeared in the logs:

• Something went wrong when counting SUCCESS for ...
• ArrayIndexOutOfBoundsException: null

The frontend refetches data every 10 seconds (both list of components and details), but there is no indication of when this is done, or when the last successful request was made. The GUI should probably both indicate when data was last fetched, and if it was successfull or failed.

Add some form of authentication when accessing the dashboard. Maybe basic auth on the API calls?

The API should also have some form of authentication. Basic Auth there as well? Token in a HTTP header?

Right now the detail page don’t update itself like the components overview does. This is a bit tricky to do because the component module itself does not really know about the routing logic. Ideally, it should auto update when the detail view is active, and don‘t do anything when other routes are active.

Needs investigation, as I’m not sure how to accomplish this.

Panopticon should post a message to Slack when a component has a bad status (possibly with a link to the status page for said component).

We have application logs residing on a separate server with its domain. I would really like to link directly from an app in Panopticon to our logs. If the client supported sending "links" (together with and icon and text, maybe) together with sensor data, the app itself could tell Panopticon where to link to.

Store and expose the history of measurements sent to the system.

Render it beautifully (graphs and stuff!) in frontend.

Right now the details for a component are still kept in memory even if you navigate away from it. This looks a bit weird if you navigate to a new component, because you first see the old details. The detail model should be cleared when navigating away from it.

Some kind of database, NOSQL, Elasticsearch etc...?

Preferably some place where it's easy to query historic data, to be able to effectively fetch long durations of the data and make graphs etc. Ref. issue #3.