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
I think telemetry server should have a way to override the application name and that override the application name that is indexed on each metric. We might could have no ownership on the installation configuration so the ultimate solution is to override this.
Overriding the application name could trigger a reindex of the event. While we wait for configuration updates we could work on allowing overrides on our side.
Also, event can be sent with an application application name different from the initial configured app name. This leads to inconsistency of indexed metrics. Installation name should override event data and not the other way around.
Proposal:
Store initial and last known installation name in reported_name field (ie. rename current name field)
Update reported_name on each event sent to the server.
Add overrided_name field editable from the UI in a details view of the installation (where the reported name is also shown)
Define name as overrided_name || reported_name and use this for listings and indexing event.
Reindex all events when the effective name is updated.
This sounds like a very complete and solid solution @bcardiff, and it would allow us to decouple 'showing good aggregates' from 'having others fix their installations'. My only concern would be effort required. If this is less than 40hs, go ahead, if not, let's talk.
There are some misnamed applications currently: verboice-cdc-cambodia, verboice-cambodia, (empty).
The (empty) application seems to have been renamed since it was created. So it might be the case that there is some data to remove or migrate.
The text was updated successfully, but these errors were encountered: