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 just upgraded our production instance to 4.13(.1) and was wondering about the telemetry that is now in DT:
We have 2 instances running; 1 production and 1 testing/staging to make sure the newest update will still work for us. Would it make sense for you guys to add an extra field (possibly with pre-defined values, might make queries on your side easier than free text) with information like this about the instance? Imho it might give even more insight in when/where updates are installed...
How/where is the 'system_id' saved? Is this in the database? As mentioned above, we have 2 instances running and we sometimes wipe the testing DB and import a copy from production. If the ID is in the database, this would then obviously send back 2 (possibly different) versions every day for the 'same' instance. If a field describing the instance (as mentioned above) would be added (possibly as a composite key with the system_id?), you would even have a relation between the 2 instances and have even more information regarding updating behavior! Of course, the value would (probably, depending on implementation/saving location) have to be changed after importing, but imho that would make more sense then allowing eg the system_id to be manually (re-)set.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I just upgraded our production instance to 4.13(.1) and was wondering about the telemetry that is now in DT:
Beta Was this translation helpful? Give feedback.
All reactions