Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
There are a few components to this, which I suspect have the same root cause.
When using the JSON authentication in combination with a database, active connections are not visible in the web app for administrators and history for them is not logged. They also don't appear in the activeConnections API endpoint and no datasource named 'json' is present. This is not ideal for dashboards monitoring active connections.
If someone familiar with the work needed to address any of those would like to give some direction, I'd be happy to look at making the necessary updates. (Assuming it's possible for these to coexist in this way)