|
|
@@ -1,5 +1,7 @@
|
|
1
|
1
|
// @flow
|
|
2
|
2
|
|
|
|
3
|
+import { jitsiLocalStorage } from '@jitsi/js-utils';
|
|
|
4
|
+
|
|
3
|
5
|
import { getAmplitudeIdentity } from '../analytics';
|
|
4
|
6
|
import { CONFERENCE_UNIQUE_ID_SET, getConferenceOptions, getRoomName } from '../base/conference';
|
|
5
|
7
|
import { LIB_WILL_INIT } from '../base/lib-jitsi-meet';
|
|
|
@@ -72,12 +74,18 @@ MiddlewareRegistry.register(store => next => action => {
|
|
72
|
74
|
// This is done in order to facilitate queries based on different conference configurations.
|
|
73
|
75
|
// e.g. Find all RTCPeerConnections that connect to a specific shard or were created in a
|
|
74
|
76
|
// conference with a specific version.
|
|
|
77
|
+ // XXX(george): we also want to be able to correlate between rtcstats and callstats, so we're
|
|
|
78
|
+ // appending the callstats user name (if it exists) to the display name.
|
|
|
79
|
+ const displayName = options.statisticsId
|
|
|
80
|
+ || options.statisticsDisplayName
|
|
|
81
|
+ || jitsiLocalStorage.getItem('callStatsUserName');
|
|
|
82
|
+
|
|
75
|
83
|
RTCStats.sendIdentityData({
|
|
76
|
84
|
...getAmplitudeIdentity(),
|
|
77
|
85
|
...options,
|
|
78
|
86
|
endpointId: localParticipant?.id,
|
|
79
|
87
|
confName: getRoomName(state),
|
|
80
|
|
- displayName: localParticipant?.name,
|
|
|
88
|
+ displayName,
|
|
81
|
89
|
meetingUniqueId
|
|
82
|
90
|
});
|
|
83
|
91
|
} catch (error) {
|