You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the now formal rename of the connection server from “autopush” to “autoconnect”, for clarity we should rename its metrics' historical “autopush” prefix to “autoconnect”.
Once deployed we can duplicate our Grafana dashboard and modify it to refer to the new names while continuing to use the old dashboard when needed to look at historical data until it expires (I believe in 6 months).
This is a very low priority task and more of a nice to have than anything else.
With the now formal rename of the connection server from “autopush” to “autoconnect”, for clarity we should rename its metrics' historical “autopush” prefix to “autoconnect”.
Once deployed we can duplicate our Grafana dashboard and modify it to refer to the new names while continuing to use the old dashboard when needed to look at historical data until it expires (I believe in 6 months).
This is a very low priority task and more of a nice to have than anything else.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: