What is diagnostic data and how is it used in Skype?

Using diagnostic data, Skype keeps its security and updates current, detects, diagnoses and fixes problems, and improves its products. Users’ names and email addresses are not included, nor do their files’ contents.

Microsoft collects diagnostic data about the Skype client software installed on the user’s device and sends it to them. Depending on the situation, diagnostic data can either be required or optional. Additionally, we offer you the option of providing us with diagnostic data that is mandatory or optional through the use of privacy controls to allow you to choose whether or not you would like to provide us with this data.

Skype’s required data is the minimum amount of information that is required for it to function properly on the device in which it is installed, as well as keeping it secure, up-to-date, and secure.

There is a requirement for diagnostic data in order to be able to identify problems with Skype that may be related to the configuration of a device or software on a computer in order to resolve the problem. This information can be used to determine whether certain Skype features crash more frequently with a particular operating system version, with newly introduced features, or when certain Skype features are disabled. By collecting diagnostic data, we are able to identify, diagnose, and fix these problems more quickly, thereby reducing the impact on users.

Data that is required for providing and improving Skype connected experiences and ensuring that they are up-to-date and secure is the type of required service data that is collected.

In the optional data we collect, we are able to improve the quality and performance of our products, as well as use the data for diagnosing and resolving problems more effectively.

include both the optional diagnostic data and the required service data if you choose to send us optional diagnostic data.

• TimedOut – This is the information about the fact that the time limit has been exceeded. There are only two types of data that can be sent: the truth or the lie.
• StatusCode – This is a number that is used to identify the root cause of a problem with joining a server. For example, the problem may arise due to a problem with the connectivity to the server.
• Url – This information about the url address is used to identify the reason why the guest user was unable to join.

join_link_resolution

A collection of events that monitor the functionality of the join link when used.

Join_link_resolution events are commonly associated with the following attributes.

join_link_resolution(JoinLinkResolutionError)

Here is the information regarding the problem with the join link.

• ResolutionError – A description of what caused the problem when trying to join using the link. The problem may be related to the identification of the thread, for example.
• Action – This is the information about the status of an action attempt, whether it was successful or there was an error. In order to calculate the success ratio, the information collected is used.

join_link_resolution(ShortIdResolutionServiceSuccess)

In this section you will find information regarding the creation of short identifiers for short links. We send this data in order to calculate the success ratio of this service and to keep track of its proper functioning.

• ShortId In order to be able to detect problems that are reoccurring in the situation if a user attempts to join the conversation dozens of times due to some problem, it is important to have information about the short identifier. This information can be used to distinguish the case from the situation in which the same problem is occurring for a dozen different users at the same time.
• ConversationId – By using the information about the conversation ID, we can be able to identify the problems that are reoccurring in the situation when the user tries to join the conversation dozens of times due to some sort of technical issue, as well as distinguish between a situation where the same problem appears for a dozen different users.
• Action – This is the information about the status of the action attempt, whether it was a success or an error. In order to calculate the success ratio, the information is used in the calculation.

join_link_resolution(ShortIdResolutionServiceError)

This information relates to problems encountered during the creation of the short identifier for the short link. It is tracked to find out if there are any problems with joining the meetings by using the link provided in the email.

• RequestId –   In this case, the information about the request identifier is used to be able to detect the reoccurring problems if a user tries to join the conversation a dozen of times because of some problem, and to be able to distinguish between the situations in which the same problems are occurring for a dozen different users at the same time.

• TimedOut – The information regarding the fact that the time limit has been exceeded. It should be noted that the data sent may only be truthful or false.
• StatusCode – In the case of a status code, it is a number that gives us information about the type of error that occurred when joining, for example, a problem with a server to diagnose the root cause of the error.
• ShortId – As a result of the information that the short identifier contains, we are able to identify problems that are reoccurring in a situation and differentiate them from situations where the same problems are occurring for several users at the same time due to some problems if the user tries to join a conversation dozens of times due to some problem.
• ConversationId -When the coversation identifier is used for the purpose of detecting the problems that occur repeatedly in the conversation, if for example a user tries to join the conversation a dozen times because of some problem, this information can be used to distinguish between situations where the same problem occurs for a dozen different users.
• Action – An indication of the success or failure of the action attempt can be found in this information. The success ratio is calculated based on the information provided.

join_link_retrieval

An event bundle that monitors the creation of join links and the functionality that goes along with it.

Common attributes for join_link_retrieval events.

• Action – This is a record of what happened when the link was retrieved successfully or failed during the retrieval of the join link.

join_link_retrieval(JoinLinkRetrievalServiceSuccess)

Join links are created successfully when an event is sent when the link is created. The purpose of sending this information is to track the success ratio of the project.

• ConversationId – A combination of the information about a conversation identifier and the information about the user’s experience allows us to identify successes and problems that are recurring in a given situation. For example, if a user tries to join the conversation a dozen times due to some problem, we will be able to distinguish that situation from the situation where the same problems appear for a dozen different users..
• ShortId – If the user attempts to join the conversation several dozen times due to some problem, the information about the short identifier allows the system to be able to detect reoccurring successes and problems that are occurring in the situation. The system uses the information about the short identifier to distinguish this situation from the situation in which the same problems are occurring for a dozen different users at the same time.

join_link_retrieval(JoinLinkRetrievalServiceError)

In the event of an unsuccessful creation of a join link, an event will be sent. As a result of this information, any problems with a service’s operation can be detected in the future.

• RequestId – If a user tries to join the conversation dozen of times because of some problem, the information about the request identifier helps to be able to detect the problems that are reoccurring in the situation. In addition, this information is used to differentiate between the situation where the same problem occurs for dozens of different users.
• IsTimedOut – In the event that the time limit has been exceeded, the following information is provided. There are only two types of data that can be sent: true or false.
• StatusCode – A status code is a number which is supplying you with an indication of the root cause of the problem with your joining, such as a problem with a server.
• Url – It is very important to have the information about the url address in order to verify why there were problems with the guest user joining.
• ConversationId – The information about the coverage identifier is used to be able to detect successes and problems that are re-occurring in the situation if the user tries to join the conversation dozen of times because of some problem. This information is used to distinguish between cases in which the same problem occurs for dozens of different users, and those situations in which the same problem occurs for dozen different users simultaneously..
• ShortId – In order to be able to detect success and problems that recur in the situation, information regarding the short identifier can be used to be able to distinguish between a case in which the same issue is occurring for a dozen different users and a case where the same problem occurs for a dozen different users at once.

navigation_deeplink(OpenDeepLink)

There is an event that is triggered when an attempt is made from the outside to resolve a link from the external to the internal to the target.

• JoinLinkPath – Explicitly uses the JoinLinkPath to let the app know that the access link being processed is a JoinLink, and where the access link is coming from (within or external to the app).

• UrlAction – An access link to Skype has an action url parameter associated with it, which tells you what kind of action the user is attempting to use in order to access it. For example, in aсcess link “skype:?action=captureavatar”, captureavatar is a UrlAction and it will open the Avatar capturing dialog.
• Action – This is the name of the access link event that is currently being tracked.

message_sent

Sends a message when a user sends it, this information is used for evaluating the health of the delivery of messages from end to end.

• ReceiverMri – A technical identifier that is used to identify the receiver across multiple chat services.
• ReceiverUserId – Receiver skype id.
• ClientMessageId – Message id constructed on senders client side.
• EndpointId – Unique messaging endpoint id.
• RegistrationId – Unique device registration id.
• OneOnOneThreadId – Unique 1:1 thread id in case message was sent into 1:1 conversation.
• CharacterCount – Message content characters count (0 -> message delete).
• PostSource – This is the point from where the message request has originated, the name of the place from where it was initiated.
• EmoticonCount – Counting how many emoticons Skype provides in the message as a means to ensure that the Skype emoticons are working.
• NativeEmojiCount – This counter keeps track of how many emojis are in the message which are not provided by Skype in order to make sure that these are functioning as well.
• HasWikiMarkup – This program monitors the status of the usage of additional editing options that are available for messages.
• MessageCorrelationId – This is an identifier used to identify a unique message correlation between two systems.
• MessageType – High level message type (Text, Photo, File, …).
• MessageRawType – Detailed message type (RichText/Media_Video, RichText/Sms, …).
• IsOwnMessage – Flag stating that user is sender of related message.
• ConversationId – Unique conversation id.
• IsBotConversation – Flag if conversation is with bot.
• IsGroupConversation – Flag if conversation is group conversation.
• IsEncryptedConversation – Flag if conversation is private conversation.
• IsBookmarkConversation – Flag if conversation is bookmarks conversation.
• IsMeetNowThread – Flag if conversation is Meet Now conversation.
• MriNamespace – Conversation namespace to understand type of conversation Interop, Bot, Group etc.
• ThreadSuffix – This suffix identifies the type of thread, i.e. it may simply be a group of threads or it may be a feature-specific thread (encrypted, oneToOne …).

message_read

Tracks when message is read in 1:1 conversations, used as part of definition of an active user.

• MessageCorrelationId – Unique message correlation id used for E2E correlation between systems.
• MessageRawType – Detailed message type (RichText/Media_Video, RichText/Sms, …).
• IsOwnMessage – Flag stating that user is sender of related message.
• ConversationId – Unique conversation id.
• IsBotConversation – Flag if conversation is with bot.
• IsGroupConversation – Flag if conversation is group conversation.
• IsEncryptedConversation – Flag if conversation is private conversation.
• IsBookmarkConversation – Flag if conversation is bookmarks conversation.
• IsMeetNowThread – Flag if conversation is Meet Now conversation.
• MriNamespace – Conversation namespace to understand type of conversation Interop, Bot, Group etc.
• ThreadSuffix – Thread suffix helps identify type of thread which may be simply a group as or be feature specific (encrypted, oneToOne …).

people_presence_error

The application should be notified of any problems that are encountered when a user wishes to change the status of a presence (Online, offline, busy, etc.) and the application is not able to do so with success.

• Origin –
•  In order to change the status of the presence in the application, information about what element was used in the application.  It is important to collect this information so that it can be determined which part of the application is causing the problem and then fixed.

people_presence_failure

An explanation about the types of failures the user gets when he or she is attempting to fetch or set the status of his or her presence.

• ServiceType – Contains information about the service provider that failed CS or UPS.
• Scenario – Since this method passes all presence requests to the server it is of great importance to identify which of those died.
• StatusCode – Http response status code.
• StatusText – Http response status text.
• DidTimeOut – This is the “yes” or “no” information that will indicate if a problem is causing the timeout.
• CorrelationId – Correlation IDs are unique identifiers used for E2E message correlation between systems.

my_presence

This information is used for ensuring that the presence of the user is correctly fetched and set.

• UpsStatus – This presence was provided by UPS.
• CsStatus – This presence is coming from a chat service.
• CsCorrelationId – Unique message correlation id used for E2E correlation between client and Chat Service.
• UpsCorrelationId – Unique message correlation id used for E2E correlation between client and UPS(Universal Presence Service).
• Scenario – Because two methods are making use of this event, we need to know which of those methods is the initiator.

presence_for_mris

This information is used in order to make sure that the presence of contacts on the display is accurate.

• Total – The number of users whose presences we have been able to retrieve the presences of.
• Same – The number of users who had the same presence across both service UPS and CS.
• CsCorrelationId – Unique message correlation id used for E2E correlation between client and Chat Service.
• UpsCorrelationId – Unique message correlation id used for E2E correlation between client and UPS(Universal Presence Service).

people_syncAddressBookDialog

The address book dialog is loaded by the process of loading a set of information concerning the loading process. A dialog file consists of a series of fields that describe the steps that are required for the dialog to load correctly. If a step has gone well, the status of that step is set to true/granted, and if it has failed or has not yet been performed, the status is set to false/denied. The address book import flow is being collected in order to determine whether the flow is healthy.

• DidPressNextOnValueProp – There is a field in this form that confirms if a user has clicked on the button “next”. In this field, only true or false values are allowed to be set up.
• DidHavePermission – In this field, you will be able to find out if the user has granted permission for the contacts to be synchronized with the calendar. There is only one possible value for this field, which is granted or false.
• DidPromptBefore -There is also an option for DidPromptBefore which passes the information if the user has previously been asked to synchronize contacts.
• DidRequestPermission – A field such as this tells us whether the user has been asked to grant permission before the contacts are synchronized. Only true or false can be set as a value for this field.
• DidGrantPermission – The value of this field will be set to true if the user has granted permission to use the contact list of the user. If the opposite is true, then it will be false in this case.
• DidStartSync – The information about how to start the process of syncing your contacts’ lists is given in the following paragraph. As far as I know, it is only possible to set it up to a true or false value.
• DidVisitPrivacyStatement – If the user has visited the Privacy statement then this field will be set to true, otherwise it will be set to false. There is a default value of false for the value of this field.
• DidSeeLearnMoreButton – A value of true is sent when this field can only be set up to be set to true or false when it is set to true.
• DidVisitLearnMorePopup- When the user has visited the “Learn More” popup, this value will be set to true. If the user has not visited it, then it will be false.
• Origin – During the start of the dialog box, the user was where he or she was when it was launched.
• Duration – Indicates how long it has taken for the dialog box to have been opened and closed after it was started and closed.
• OnboardingDisplayOrder – Describes the order in which the dialog boxes are displayed during the onboarding.
• OnboardingStepsCount – Counts how many steps are involved in the onboarding process.
• Exit – This is the type of dialog close that is used.
• IsNewUser – This field is used to describe whether the user is a new.

people_contacts_action(GetContacts)

This measure is used to determine the health of the application by evaluating the ratio of successful synchronizations to failed synchronizations of the contacts list.

• IsFromServer – The information that is provided by this parameter is extremely important for identifying the source of the potential problem.
• ErrorCode – Error code that indicates what the specific error type is in order to identify the cause of the error.
• Action – There are different types of actions that can be performed, such as receiving a contact list, adding a contact, removing a contact, etc.
• Status – The status of the action that has been performed can be either a success or an error.

settings_privacy(SendFullTelemetry)

As a way of helping Skype improve, all the user’s preferences as well as all the telemetry that is required and optional will be sent along with the information about Skype users’ preferences.

• DidGrantPermission – Providing permission for the transmission of all telemetry information is an important part of giving the permission. There is only one possible answer, “yes” or “no”.
• Origin – In the application, the place or element where the option was displayed, is the location where the option is displayed.
• Actions – These are the places, the types of actions that have been initiated that have resulted in the logging of information.

chat_service_bundle_processing_failure

A problem that occurred during the processing of the bundle of tasks that were created for updating and synchronizing information about conversations, messages, etc., was reported.

• description – If the problem occurred during preprocessing or processing, you will need to know what stage the problem occurred in.

messaging_e2ee

An event group that monitors the health of the privacy conversation feature so that it ensures the encryption of the conversations is working as intended.

Common attributes for messaging_e2ee events.

• Action – This is the type of event that has happened such as an invite, acceptance, confirmation, rejection, decryption failure, and encryption failure.
• Status – As a result of establishing a connection, this is the final result of the process. The value of a success or failure can only be one of two values.
• Reason – We need to further investigate what is likely to be causing the problem in order to determine how to fix the problem.

messaging_e2ee(Confirm)

The confirmation event is triggered when the encryption conversation has been successfully established. In order to calculate the success ratio and track the health of the service, we collect the information mentioned above.

• IsAutoConfirm – Information regarding the fact that the end-to-end encryption has been established during the conversation.

messaging_e2ee(Reject)

When an encrypted conversation is unable to be created, a failure event is sent. The failures in the infrastructure are detected by comparing them to the successful events.

• RejectionReason – This is an informational field about the causes of the problem with the encrypted conversation. As an example, if the user had made a voluntary decision not to attend the private (encrypted) conversation or if there was an issue with the encryption/decryption itself, it was not related at all to the user’s action at all.

messaging_e2ee(Retry)

It contains information about how the connection was re-established after the first attempt failed.

• RetryType – This is the information about what kind of retry is being made.

messaging_e2ee(EncryptionFailure)

This is the information about the encryption process that has encountered a problem.

messaging_e2ee(DecryptionFailure)

Describes how the decryption process failed due to an error, and what the problem was.

people_census

A summary of the census telemetry provides you with a snapshot of your contact lists and different conversation counts, such as how many Skype or phone contacts you have or how many encrypted conversations you have participated in. We can use this information to identify critical features that we need to address.

• ConversationsCountTotal – This value indicates the total number of conversations that are known to the user.
• ConversationsCountDisplayable – Calculates the number of displayable conversations as some conversations aren’t displayed because they aren’t displayable (empty conversations, users who aren’t members anymore, blocked etc..).
• ConversationsCountDisplayed – This is the number of conversations displayed, or rather the subset of conversations that are displayed based on the current filtering conditions.
• RecentListConversationsCount – This indicates how many conversations have been held in the last 24 hours.
• RecentListSkype1on1ConversationsCount – Count of Skype 1on1 conversations.

• RecentListSkypeGroupConversationsCount – This is the number of conversations that are taking place within a group.
• RecentListSkypeBotConversationsCount – Number of bot conversations.
• RecentListPstnConversationsCount – Number of PSTN conversations.
• RecentListPrivateConversationsCount – This is the number of private conversations.
• RecentListConversationsWithTabsCount – This is a count of all the conversations that are displayed on the screen to the user.
• RecentListOtherConversationsCount – Number of conversations excluding bots, 1on1, PSTN, private or group.
• Muted1on1ConversationsCount – This is a count of how many muted one-on-one conversations.
• MutedGroupConversationsCount – This shows how many muted group conversations there are in the group.
• SmartMutedConversationsCount – This is a count of how many smart muted conversations are a part of the conversation.
• TranslatedConversationsCount – Count of conversations for which the user has elected to have them translated.
• ManuallyAddedContactsCount – This is a count of how many profiles have been manually added by the user.
• BlockedContactsCount – This is the number of contacts that have been blocked by the user.
• BotsContactsCount – This is a count of how many bots have been added by the user.
• FavoritesContactsCount – The number of profiles that have been marked as selected.
• AllNonBlockedContactsCount – This allows the user to easily determine how many profiles out of the total are not blocked by the user.
• OneWayShortCircuitContactsCount – This is a number representing how many profiles were suggested to the user.
• TwoWayShortCircuitContactsCount – This is a measure of the number of profiles that were automatically added as buddies by a system that is older than January 2017.
• PstnContactsCount – This is the number of contacts that the user has on their phone according to the user.
• EngagedContactsCount – The number of profiles that have been engaged with by the user in the last 30 days.
• AllShownContactsCount – The number of contacts that are shown to a user, in addition to the number of profiles they have.
• RemovedAuthorizedContactsCount – This is the number of profiles that are authorized but have not been manually added to the profile by the user.

messaging_notification

Information about toast notifications is used for tracking the delivery of messages and informing the user when it has been delivered.

• NotificationAction – Indicates the action to be taken by the notification, it can be InterruptUser, InformUserExternal, Ignore.
• IsSystemNotification – This is a boolean value which indicates whether the notification is a system notification.
• Action – What actions should be taken in response to the notification, such as a Tap, Panned, Ignored, Shown, or QuickAction.
• ToastType – This is the type of notification to be sent. For example, a quote could be sent, or a mention could be sent, or a regular message could be sent, or a system alert could be sent.
• IsGroupConversation – This parameter indicates whether the notification is related to a group conversation, and is a boolean value that indicates whether it is a boolean value.
• ConversationId – Unique conversation Id to.

messaging_share_to_skype

Share to Skype is a feature that provides information about the use of the feature as well as how it is being used.

• Action – Action to be tracked (Share, Open).
• IsSharedToContact – This variable tracks if a file has been shared with a particular contact.
• ErrorCode – This is a specific error code that is used to identify the type of error.
• IsSendingVideo – The IsSendingVideo property tracks whether the content being shared is a video.
• IsSendingImage – This field tracks whether the content that is to be shared is an image.
• Type – This is used to keep track of the type of shared content.

messaging_action

In this event, the user takes action on a message in order to gain an understanding of the health and usage of basic message interactions.

Common attributes for messaging_action events.

• Action – The kind of message action that was performed (Copy/Edit/Delete/Forward/Quote…).
• Origin – Refers to the component of the application from which message actions originated.
• TimeToActionDuration – Is the amount of time that has passed since the message was originally sent and when the user took the action.
• DocId – In the case where a message has been sent but cancelled or retried due to a failure, this document ID will provide more insight into the failure reason.
• MessageCorrelationId – This is an identifier which is unique to each message correlated between systems.
• MessageType – High level message type (Text, Photo, File, …).
• MessageRawType – Detailed message type (RichText/Media_Video, RichText/Sms, …).
• IsOwnMessage – Flag stating that user is sender of related message.
• ConversationId – Unique conversation id.
• IsBotConversation – Flag if conversation is with bot.
• IsGroupConversation – Flag if conversation is group conversation.
• IsEncryptedConversation – Flag if conversation is private conversation.
• IsBookmarkConversation – Flag if conversation is bookmarks conversation.
• IsMeetNowThread – Flag if conversation is Meet Now conversation.
• MriNamespace – Conversation namespace to understand type of conversation Interop, Bot, Group etc.
• ThreadSuffix – By using the ThreadSuffix, it is possible to identify the type of thread, which may be simply a group or may be feature-specific (encrypted, oneToOne…).

messaging_action(Forward)

Monitoring message forward action.

• SkypeConversationCount – This number represents how many Skype conversations that have been forwarded to with the selected message having been forwarded.
• PrivateConversationCount – This is an indicator of the number of private/encrypted conversations which have been forwarded.
• SmsConversationCount – An indication of how many sms conversations have been sent to which a selected message has been forwarded.

messaging_action(ShareFile)

Monitoring file sharing action.

• IsShared – Flag if the sharing was succesfull.
• Error – Error details in case sharing of file failed.
• FileExtension – File extension.

messaging_action(Quote)

Monitoring message quoting action.

• QuotesTriggerType – Type of the trigger that initiated original quote (Menu, Swipe, CopyPaste …).
• QuotesMessageType – Type of the quoted message (Text, Photo, File, Audio, Poll, etc.).

messaging_action(ClearQuote)

Monitoring clearing of the previously selected message quote.

• QuotesTriggerType – Type of the trigger that initiated original quote (Menu, Swipe, CopyPaste …).
• QuotesMessageType – Type of the quoted message (Text, Photo, File, Audio, Poll, etc.).

messaging_action(KeyboardCopy)

Monitoring copy via keyboard action.

• MessagesCount – This indicates how many selections have been made since the last keyboard action was taken on.

messaging_action(KeyboardPaste)

Monitoring paste message via keyboard action.

• MessagesCount – This is a count of how many messages were selected by keyboard action at the time the action was taken on.

messaging_action(SelectMessages)

Monitoring action on multiple selected messages.

• SelectedMessagesCount – Defines how many messages are selected when an action is taken on.
• SelectedMessagesAction – This describes the action taken on the selected messages that was selected by the user.
• ForwardToConversationCount – This is a count of the number of conversations the messages have been sent to after being forwarded.
• SelectedMessagesDisabledCopy – Shows the number of messages in the selected list that do not have the copy option enabled.
• SelectedMessagesDisabledRemove – This is a measurement of the number of messages in the selection that have been disabled.
• SelectedMessagesDisabledForward – This parameter specifies the number of messages from the selection that have the Forward option disabled.

messaging_action(Cancel)

Sending a message has been canceled, and this monitoring is being performed.

messaging_action(CancelRejected)

Monitoring the cancelation of messages that have already been sent but have failed to be delivered.

messaging_action(RetryFailed)

Retrying a failed message send after a retry action has been taken.

messaging_action(ShowReportedMessage)

The showing of reported messages is being monitored on a regular basis.

messaging_action(Copy)

A message is being monitored for copy actions that are taking place.

messaging_action(CopyLink)

A monitoring system is in place to track the action taken on the copy link.

messaging_action(Delete)

Keeping track of the deletion process of the message.

messaging_action(Edit)

Keeping track of the edits being made to messages.

messaging_action(MarkMessageUnread)

Keeping track of the unread status of a conversation in the message.

messaging_action(DismissActionMenu)

Watching the dismissal of the action menu of a message when no options are selected.

messaging_action(DragDropFromConversationToRecentLists)

The drag and drop action to a conversation is being monitored on a regular basis.

messaging_action(AddBookmark)

It is being monitored whether or not an action has been taken to add a message bookmark.

messaging_action(RemoveBookmark)

Keeping track of the removal of bookmarked messages from the user’s inbox.

conversation_action

To understand the health and usage of basic actions over conversations, we use events that are triggered when the user takes actions on conversations.

Common attributes for conversation_action events.

• Action – The kind of message action that was performed.
• Conversation_NameSpace – Conversation namespace to understand type of conversation.
• Conversation_Id – Unique conversation id.

conversation_action(conversation_list_item_clicked)

It is important to monitor the action of clicking on items in the conversation list.

• Item_id – identifier of the conversation list item.

conversation_action(translation_action)

Monitoring translation actions (disable/request/pending/enabled/cancelled/declined).

• TranslationAction – Action (Requested/Accepted/Declined/Canceled/Disabled).
• FromLanguage – From which language to translate.
• ToLanguage – To which language to translate.

people_user_actions

A list of actions performed by an individual within people list, such as starting a call, starting a video, viewing a profile, sending a message, etc., provided information about the actions performed.

• Action – This refers to the type of action that was performed.
• Duration – The length of time it took to complete the action.
• Scenario – Scenario name.
• IsFirstSuccessfulSearch – Whether or not the action is a search and it has been performed for the first time and whether or not it was successful or not.

notificationsPrompt_action

Information about actions around notification permissions.

Common attributes for notificationsPrompt_action events.

• Action – This is a description of what kind of action has been performed.
• Origin – In the context of an application, it is the place, element, or component where the action was originated.

notificationsPrompt_action(displayed)

In response to monitoring notifications, an action prompt is displayed on the screen.

notificationsPrompt_action(opened)

A monitoring notification prompt settings opens an action when a notification is received.

• Enabled_Notifications – Indicates the status of the setting, which is false or true.

notificationsPrompt_action(closed)

Closed actions are prompted by monitoring notifications.

onboarding_setup

Bundle of events related to the first run experience (FRE) wizard. This data is collected to determine whether or not the FRE wizard is functioning properly.

Common attributes for onboarding_setup events.

• DialogOrigin – An identifier for the place within an application where a dialog was called from.
• IsNewUser – If it is the first time that this user signs in to Skype, the Skype federated profile is created. In the Skype search directory, for example, users can now be found by using the search box.

onboarding_setup(started)

The events is sent when the FRE wizard is started.

• DialogOrigin – Identifies the location within the application from which the dialog was invoked from.
• AppState – Current application state, “in-background” or “active”.
• StepSequence – Ordered List of steps shown during FRE wizard.
• NotificationsPermission – Contains the permissions assigned to the system in regards to notifications.
• CameraPermission – Contains the current permissions for the camera.
• MicrophonePermission – The current permissions associated with the microphone.
• ContactsPermission – The permissions that are currently set for contacts.

onboarding_setup(failed)

Tracks errors during FRE wizard.

• DialogOrigin – Provides an indication of where the dialog originated from, within the application, where it was called from.

onboarding_setup(finished)

Upon the completion of the FRE wizard, the event is sent out.

• Duration – This is the time in seconds between when the FRE wizard starts and when it ends.
• DialogOrigin – Determines where the dialog originated from within an application within which it was called from.
• Success – This is the result that has been obtained by the FRE wizard.
• StepSequence – Shows a list of steps ordered in order of how they appear in the FRE wizard.

onboarding_user_status

A user settings summary event is sent after the FRE wizard has been finished to provide a summary of the user’s settings. The information collected by the FRE wizard is used to measure the health of the software.

• AvatarPolicy – Controls the visibility of avatars for other users.
• AvatarState – This indicates whether or not a user has created an avatar or not.
• SetupWizardCompletionTimestamp – This time stamp is the time when the FRE wizard has been completed.
• UserIsNew -Skype federated profile will be created for this user if this is the first time the user signs into Skype for the first time. It is now possible to find a user by using the Skype search directory as an example.
• NotificationsPermission – In order to receive system notifications, you must have the current permission.
• CameraPermission – The permissions that are currently set for the camera.
• MicrophonePermission – This is the permission that is currently set for the microphone.
• ContactsPermission – The permissions that are currently in effect for contacts.

onboarding_landing_page_with_cards

The home screen on desktop has a lot of events that are related to it. This information is collected in order to determine how well the desktop home screen is functioning.

• CardName – The name of the card that appears on the landing page.
• ActionPerformed – This action tracks the number of clicks that are made on the landing page card.
• It is created a Skype federated profile for a user if this is the first time the user signs in to Skype for the very first time. For instance, users can be searched for via the Skype search directory in order to find them.

settings_permission_status

Tracks what you consented to, such as the use of your microphone, for example. In order to make sure that your consent is applied accurately to Skype, we use this information.

• Type – This field keeps track of the type of permission.
• Status – Keeps track of whether the permission has been granted or denied according to its type.
• Origin – When the permission status is changed, this is the location inside the application where it is changed.

perf

Provides performance metrics for the entire Skype process, so it can be monitored in order to improve Skype’s performance.

• Scenario – This is the name of the process that is being measured, such as the startup process, the search process, the render process, etc.
• Duration – In milliseconds, the duration of the time it took the process to complete.
• IsZeroTermSearch – Determines if the search query contains a single term, or if the query is empty.
• Endpoint – This is the endpoint that is used to search for messages.
• SearchLimit – The maximum size of the message search page.
• ErrorCode – This is the error code that appears when search results cannot be retrieved.
• ErrorMessage – A description of the error that occurred when the search results were not retrieved.
• WasNetworkAvailable – Indicates whether the client has access to the network.
• AdditionalLoading – Indicates if a message is still being loaded despite not being cached.

• QueryLength – is the number of characters that will make up your search query.
• Origin – This is the component that is responsible for where the search originated.
• SearchResultsListOrigin – This is the component that originated the search when the search took place in SearchResultsList.
• RequestStepDuration – it is a measure of how much time elapses between the first request for a search and the time it takes for the last request to receive its results, in the case of a composite search.
• PublicDirectoryRequestDuration – Measures the time that has passed since the public directory search request has been sent until the results have been received.
• MessageRequestDuration – This is the period of time between the time that the message search request was sent and the time that its results were received.
• IndexedDbRequestDuration – The time between the time of sending the IndexedDB search request and the time when the search results have been received.
• BotsRequestDuration – It indicates the time from the time a bot’s search request was sent until the time when the results of the search were received.
• AllPeopleRequestDuration – This is a measurement of the amount of time between when you sent your all people search request and when you received the results.
• FastContactsRequestDuration – This is an indicator of how long it takes between the sending of the fast contact search request and the results being received.
• MessageInConversationRequestDuration – This is the duration of time between sending the request for a message search and the results was received.

notif_perf

Using notification metrics, the Skype notification performance can be monitored and improved by monitoring and tracking notification lifecycle metrics.

• Provider – This is the name of the notification system used to deliver the notifications.
• NotificationInitializedJS – Indicates whether there was a JavaScript initialization triggered by the notification.
• IncomingCallScreenDisplayed – Indicates whether incoming call notifications were displayed on a screen or whether they were notified as a system notification.
• Phase_Waiting_For_JS_Initialization – Defines the length of time the notification will take to complete phase 1.
• Phase_Initial_Native_Processing – This is a measurement of the duration of the notification phase 2.
• Phase_JS_Processing – Defines the duration of time for which the notification should be sent during phase 3.
• Phase_Native_Displaying – Time duration of notification phase 4.
• Phase_Total – The amount of time elapsed between the time the notification was sent and when it was processed.
• NotificationProcessing – There are a number of methods available for notification processing.

scenario

Common attributes for scenario events.

• ScenarioName – The name of the scenario that is currently being tracked.
• ScenarioId – A unique identifier that allows the grouping and organization of several steps within this scenario instance.

scenario(LoginAuth)

The purpose of these messages is to monitor the health of the sign in/up service at different stages of the sign in/up process.

• ScenarioAction_service – Service name, such as ‘MSA’.
• ScenarioAction_scenario – Scenario name.
• ScenarioAction_errorName – Error name.
• ScenarioAction_statusCode – Status code of error.
• ScenarioAction_requestId – Unique ID for request.
• ScenarioAction_attempt – Number of attepts for request.
• ScenarioAction_step_name – Name of this senario step.
• ScenarioAction_step_duration – Scenario step duration. Indicator of performance of this step.
• ScenarioAction_total_duration – Total duration of this scenario.
• ScenarioAction_is_final – Indicator whether this is a final step of the scenario.
• ScenarioAction_target_duration_ms – Target step duration.
• ScenarioAction_step_name_started – Duration of ‘started’ step.
• ScenarioAction_error_description – If an error occurred, the error description is passed here.

scenario(AppStartup)

Startup duration measure by different phases, used to identify bottlenecks and health of the application.

• ScenarioAction_currentIntent – Startup intent (Push, Chat, Call, Dialpad, Recents, JoinMeetNow, Other).
• ScenarioAction_intentBased – Flag if the startup is intent based.
• ScenarioAction_step_name_phase0 – Duration of startup phase 0.
• ScenarioAction_step_name_phase1 – Duration of startup phase 1.
• ScenarioAction_step_name_phase2 – Duration of startup phase 2.
• ScenarioAction_step_name_phase3 – Duration of startup phase 3.
• ScenarioAction_step_name_phase4 – Duration of startup phase 4.
• ScenarioAction_step_name_phase5 – Duration of startup phase 5.
• ScenarioAction_step_name – Name of this senario step.
• ScenarioAction_step_duration – Scenario step duration. Indicator of performance of this step.
• ScenarioAction_total_duration – Total duration of this scenario.
• ScenarioAction_is_final – Indicator whether this is a final step of the scenario.
• ScenarioAction_target_duration_ms – Target step duration.
• ScenarioAction_step_name_started – Duration of ‘started’ step.
• ScenarioAction_error_description – If an error occurred, the error description is passed here.

scenario(AppStartupIntent)

This manual process measures the length of time it takes for each phase of the startup process based on the context of the intent and different phases of the process, thus identifying bottlenecks and detecting the health of the application.

• ScenarioAction_AppState – This is a number that represents what state the app is in, such as “Active” or “Background”.
• ScenarioAction_StartupContext – In the scenario, this type of context is used when starting the scenario (Unknown, Push, Recents, Chat, IncomingRing, Dialpad).
• ScenarioAction_ColdStartup – A flag that indicates if this is a “cold startup”.
• ScenarioAction_ColdStartup_step_duration – Duration of “cold startup” scenario step.
• ScenarioAction_ColdStartup_total_duration – Time that has elapsed from the beginning of the scenario, until the “cold startup” step.
• ScenarioAction_intentBased – This flag indicates if the startup is intent-based (for example, launching a chat or a call).
• ScenarioAction_reason – The reason for triggering the app in the first place (ColdStartup, AppStateChange, Push, LocalNotification, TrouterMessage).
• ScenarioAction_Phase0_step_duration – The time it takes to complete phase 0 of the startup process.
• ScenarioAction_Phase0_total_duration – This is the total time that has elapsed up until this point of the measurement.
• ScenarioAction_Phase1_step_duration – This is the duration of the startup phase 1.
• ScenarioAction_Phase1_total_duration – This is the total amount of time spent up to this point in the measurement.
• ScenarioAction_Phase2_step_duration – The amount of time required for phase 2 of the startup process.
• ScenarioAction_Phase2_total_duration – Describes how much time has passed so far up until this point in the measurement.
• ScenarioAction_Phase3_step_duration – Time spent by the startup process during phase 3.
• ScenarioAction_Phase3_total_duration – This is the total duration so far between the beginning of the measurement and the end of the measurement.
• ScenarioAction_Phase4_step_duration – Time taken for the startup phase 4 to complete.
• ScenarioAction_Phase4_total_duration – This is the total duration of the measurement up until this point in the measurement.
• ScenarioAction_Phase5_step_duration – The amount of time it will take to complete phase five.
• ScenarioAction_Phase5_total_duration – This is how long the scenario has taken so far up until this step in the measurement.
• ScenarioAction_CheckAppState_step_duration – Duration of “checking app state” step.
• ScenarioAction_CheckAppState_total_duration – This is the total length of time that has been spent so far up to this point in the measurement.
• ScenarioAction_StartedProcessingLocalNotification_step_duration – Time taken by the action “Started processing local notifications” to complete the step.
• ScenarioAction_StartedProcessingLocalNotification_total_duration – Counts the total amount of time that has been spent up until this point of the measurement.
• ScenarioAction_StartedProcessingPush_step_duration – This is the amount of time it takes to process the “started processing push notification” step.
• ScenarioAction_StartedProcessingPush_total_duration – Time period since the scenario started processing push until the current point of measurement.
• ScenarioAction_PushProcessingComplete_step_duration – Determines when the “push notification processing has been completed” step.
• ScenarioAction_PushProcessingComplete_total_duration – This is the total duration so far that has been recorded up until this point of the measurement.
• ScenarioAction_IncomingCallPush_step_duration – Timeframe for the moment that an “incoming call push notification” is sent to the user.
• ScenarioAction_IncomingCallPush_total_duration – The total amount of time that has been recorded so far up until this point in the measurement.
• ScenarioAction_NotifyingCallee_step_duration – This is the time it takes for the “notifying the callee” step to complete the step.
• ScenarioAction_NotifyingCallee_total_duration – This is the total time that has been spent so far up until this step of the measurement.
• ScenarioAction_DisplayIncomingCallNotification_step_duration – Time taken to display the incoming call notification during the ‘display incoming call notification’ step.
• ScenarioAction_DisplayIncomingCallNotification_total_duration – The total duration of the time spent on this step so far in the measurement.
• ScenarioAction_PresentIncomingRing_step_duration – This is the time taken for the “present incoming ring” step.
• ScenarioAction_PresentIncomingRing_total_duration – The total duration of the present incoming ring up to the present point in the measurement.
• ScenarioAction_CallPanelRendered_step_duration – The time taken by the call panel to render during the step.
• ScenarioAction_CallPanelRendered_total_duration – This is the total duration of the call panel rendered up to the current stage of the measurement.
• ScenarioAction_WillNavigateToRecents_step_duration – The length of time that will be spent in the “will navigate to recents” step.
• ScenarioAction_WillNavigateToRecents_total_duration – The total amount of time that has been spent up until this point in the measurement.
• ScenarioAction_RecentsWillMount_step_duration – The length of time it takes for the recents to mount step.
• ScenarioAction_RecentsWillMount_total_duration – The duration that has been accumulated so far up to this point of the measurement.
• ScenarioAction_ConversationListPanelRendered_step_duration – Describes how long it will take to render a conversation list panel step.
• ScenarioAction_ConversationListPanelRendered_total_duration – This is the number of seconds that have elapsed since the beginning of the measurement.
• ScenarioAction_RecentsRendered_step_duration – Time taken by the “recently rendered” step.
• ScenarioAction_RecentsRendered_total_duration – This is the total duration that has been measured up to this point in the measurement.
• ScenarioAction_WillNavigateToChat_step_duration – This determines how long it will take for a user to navigate to the chat step.
• ScenarioAction_WillNavigateToChat_total_duration – This is the total time spent up until this point in the measurement.
• ScenarioAction_MessaggeStreamRendered_step_duration – This is the duration of the “message stream rendered” step.
• ScenarioAction_MessaggeStreamRendered_total_duration – This is the total duration of the measurement up to that point in the measurement.
• ScenarioAction_WillNavigateToDialpad_step_duration – Defines how long it will take the user to navigate to the dialpad step.
• ScenarioAction_WillNavigateToDialpad_total_duration – The total duration of the measurement up until the point at which the scenario will navigate to the dialpad.
• ScenarioAction_DialpadRendered_step_duration – It is the time it takes for the “dialpad rendered” step to complete.
• ScenarioAction_DialpadRendered_total_duration – The total duration of the measurement up to this point in the measurement.

• ScenarioAction_step_name – The name of this scenario step.
• ScenarioAction_step_duration – Duration of a scenario step, a measure of the performance of this step in a scenario.
• ScenarioAction_total_duration – This is the total amount of time you are going to spend on this scenario.
• ScenarioAction_is_final – This indicates whether the scenario action is the last step before the end of the scenario.
• ScenarioAction_target_duration_ms – The target duration of the action.
• ScenarioAction_step_name_started – Time in seconds that has elapsed since the start of the ‘started’ step.
• ScenarioAction_error_description – In the event that an error occurs, the error description will be passed here.

scenario(TimeToConnected)

Tracks the amount of time it takes for a chat service to establish a connection with a user. Connectivity issues associated with chat can be tracked and improved by using this tool.

• ScenarioAction_ConnectionType – Connection type, such as “REST”.
• ScenarioAction_ReasonForConnecting – This is the reason for the chat service connecting to the client computer, such as “Foreground”.
• ScenarioAction_step_name – The name of this scenario step.
• ScenarioAction_step_duration – A scenario step’s duration can be determined by its duration. The performance of this step is a good indicator of how well the process went.
• ScenarioAction_total_duration – The amount of time that has elapsed since the start of this scenario.
• ScenarioAction_is_final – Whether this is a final step in the scenario, or if it is an intermediate step within the scenario.
• ScenarioAction_target_duration_ms – The duration of the target step in the scenario.
• ScenarioAction_step_name_started – This is the duration of the ‘started’ step.
• ScenarioAction_error_description – When an error occurs during the scenario action, then the error description will be passed here.

scenario(AnswerCall)

The scenario health and reliability are tracked using the information collected when the user answers the call.

• ScenarioName – AnswerCall.
• ScenarioAction_step_name- This is the name given to the action step that will be taken in the scenario.
• ScenarioAction_step_duration – Scenario step duration. This is an indicator of how well this step is performing.
• ScenarioAction_total_duration – This value indicates how long the scenario will be running for in total.
• ScenarioAction_is_final – A flag that indicates whether this action is the last action of this scenario.
• ScenarioAction_target_duration_ms – The target step duration.
• ScenarioAction_step_name_started – This is the duration of the ‘started’ step.
• ScenarioAction_error_description – The error description is passed to the user if an error occurred during this action.

scenario(HtmlNotification)

Tracks reliability of HTML notifications.

• ScenarioAction_step_name – Name of this senario step.

• ScenarioAction_step_duration – Scenario step duration. This indicator will tell you how this step is performing in terms of its performance.
• ScenarioAction_total_duration – This value indicates how long the scenario will last at the end of the scenario.
• ScenarioAction_is_final – This is a way of indicating whether or not the action is the last step in the scenario.
• ScenarioAction_target_duration_ms – This is the target step duration.
• ScenarioAction_step_name_started – This is the duration of the ‘started’ step.
• ScenarioAction_error_description – If a scenario action has failed, the description of the error is passed here.

scenario(Responsiveness)

Track the responsiveness of the individual UI elements – e.g. elapsed time between the click of the mute button and the actual muting of the microphone after the button is clicked.

• ScenarioAction_cause – Contains the reason why a scenario was completed (e.g. ActionClosed, Timeout, or Error).
• ScenarioAction_step_name – This is the name of the scenario action step.
• ScenarioAction_step_duration – Duration of each scenario step in the scenario. This is an indicator of the performance of this step.
• ScenarioAction_total_duration – This value indicates the length of the entire scenario.
• ScenarioAction_is_final – The value of this parameter indicates whether or not this is the final step in the scenario.
• ScenarioAction_target_duration_ms – The duration of the target step in the scenario.
• ScenarioAction_step_name_started – This is the duration of the ‘started’ step.
• ScenarioAction_error_description – When there has been an error in the scenario actions, a description of the error will be passed here.

scenario(ResponsivenessSelectHubTab)

Track responsiveness of Hub Tab switching – how long it takes the user to click on the tab control and for the content to start displaying.

• ScenarioAction_cause – Indicates the reason why the scenario was closed (e.g. ActionClosed, Timeout or Error).
• ScenarioAction_tab – Indicates which tab of the scenario was selected.
• ScenarioAction_step_name – The name of this scenario action step.
• ScenarioAction_step_duration – The duration of each scenario step in the scenario. This is an indicator of how well this step is performing.
• ScenarioAction_total_duration – This field specifies the duration of the scenario.
• ScenarioAction_is_final – Is an indicator that this is the last step in the scenario.
• ScenarioAction_target_duration_ms – The duration of the target step in the scenario.
• ScenarioAction_step_name_started – This is the duration of the ‘started’ step.
• ScenarioAction_error_description – In the case of an error occurring, the description of the error is passed here.

scenario(StreamFrom)

In order to monitor the performance and the health of navigating to chat, it tracks the time it takes for the navigation to happen.

• ScenarioAction_origin – This is the location in the app from which the conversation was initiated in the first place. Identifies problematic entry points and helps to resolve them.

• ScenarioAction_browserOrigin –
•  From where the conversation was initiated in the browser, you can find the source location in that browser. Assists in the identification of problematic entry points.
• ScenarioAction_step_name – This is the name of the scenario action step.
• ScenarioAction_step_duration – The duration of each step in the scenario. This is an indicator of how well this step has performed.
• ScenarioAction_total_duration – The total amount of time spent in this scenario.
• ScenarioAction_is_final – Indicates whether or not this is the last action in the scenario.
• ScenarioAction_target_duration_ms – This is the target step duration.
• ScenarioAction_step_name_started – This is the duration of the ‘started’ step.
• ScenarioAction_error_description – Whenever an error occurs in a scenario action, the error description is passed here.

sisu_welcome_screen

There are a number of events associated with the main welcome screen that make up this bundle. The purpose of this collection is to measure the health of the main welcome screen on the website.

Common attributes for sisu_welcome_screen events.

• Action – This is used to identify the exact stage of the process so that we can group the events and measure the health of the particular stages.
• IsMSASignUpWebViewLoaded – Indicates whether the Microsoft Account flow has been loaded so that signing in/up to Skype is possible.

• IsFirstTimeSignIn –
• It is created a Skype federated profile for this user the first time the user signs in to Skype. It is now possible to find users via Skype search directory, as an example.

sisu_welcome_screen(WelcomeScreenLoaded)

In the event of a successful loading of the welcome screen, this event is sent. To measure the quality of the experience before a user signs up or signs in.

sisu_welcome_screen(GetStartedPanelLoaded)

After the “Get Started” screen has been loaded successfully, the “Get Started” event will be sent. The purpose of this metric is to measure the health of the pre-signup experience for new users.

sisu_welcome_screen(LoginFlowStarted)

After the sign-in/sign-up flow has been initiated, an event is sent that indicates the process is complete. To measure the health of the pre-sign-in or pre-sign-up experience, this tool is used.

sisu_welcome_screen(CreateAccountFlowStarted)

After the registration flow has been launched, the event is sent after it has been initiated. The purpose of this metric is to determine how well the signup experience is going.

sisu_welcome_screen(CreateAccountFlowCanceled)

As soon as the sign up flow has been canceled, an event is sent to the user. Measuring the health of the signup experience is used to determine the overall success.

sisu_app_entry_start

This is a bundle of events that relate to the intent of the user to sign up for Skype or to sign in. This data is collected to measure the health of the sign-up/sign-in process.

• Method – This indicates whether or not it was a sign-in or a sign-up. Sign-in and sign-up flows can be monitored by using this tool.
• IsFirstTimeSignIn –
•  It is created a Skype federated profile if this user signs in for the very first time to Skype. By using Skype’s search directory, for instance, users can now be found by using the name of the user.

sisu_app_entry

It contains a collection of events relating to the successful completion of the sign-in/sign-up process by the user. In order to measure the health of the sign-up/sign-in process, this information is collected.

• Method – This indicates whether it was a sign-in or a sign-up. The purpose of this tool is to monitor the flow of people signing up and signing in.
• IsFirstTimeSignIn –
•  This user will be created a Skype federated profile as soon as he or she signs in for the very first time to Skype. For instance, a user can now be found in the Skype search directory by using the search function.

sisu_msa_signup_funnel

This is a bundle of events that pertain to the user going through the individual steps of the Skype sign up process. The purpose of this data collection is to measure the health of the sign up process.

• FunnelPageName – This is used to indicate the exact name of the step during the sign up process for Skype.
• ErrorCode – This is the error code that is displayed if there is an error during the sign up flow.
• IsFirstTimeSignIn – If this is the first time a particular user has signed in to Skype, then a new Skype federated profile will be created. In the Skype search directory, you can now find a user by searching for their name as an example.

sisu_msa_signin_funnel

As part of the sign-in flow to Skype, a group of events is triggered when the user goes through each step of the process. This information is collected in order to measure the health of the sign-in process.

• FunnelPageName – This is the name of the specific step during the sign-in process for Skype.
• ErrorCode – An error code that is displayed in case of an error occurring during the sign up flow.
• IsFirstTimeSignIn – It is created a Skype federated profile for this user if this is the first time they have signed in to Skype. It is now possible to find a user through the Skype search directory, as an example.

sisu_msa_interrupt_handler

The re-authentication popup is a collection of events related to it. In some cases, these pop-ups will appear when the system detects that there has been an unexpected change or activity on the account. The device may be a new one, for example. The purpose of this data collection is to measure the health of recovery flows from those scenarios.

Common attributes for sisu_msa_interrupt_handler events.

• Action – Designates a particular event so that we can group them together in order to measure the health of the specific stages.
• IsFirstTimeSignIn –
•  This user will be created a Skype federated profile as soon as he or she signs in for the first time to Skype. It is now possible to find users via Skype’s search directory, as an example.

sisu_msa_interrupt_handler(RefreshTokenStored)

When user re-authentication flow is started, an event is sent when the user re-authenticates.

sisu_msa_interrupt_handler(UserSwitchedAccounts)

This event is sent to the user shortly after he or she has successfully re-authenticated with a different account for the first time.

sisu_msa_interrupt_handler(UserSignedIn)

An event is sent after a successful re-authentication has been completed by the user.

sisu_sso_screen

It is a bundle of events related to the single sign-on (SSO) flow to Skype for Android devices. The purpose of this collection is to measure the health of the SSO process.

Common attributes for sisu_sso_screen events.

• Action – Defines the exact event that takes place in order to group these events and to measure the health of each stage.
• IsFirstTimeSignIn –
• When this user signs in to Skype for the first time, a Skype federated profile is created for the user. It is now possible to search for users via the Skype search directory, for instance, as an example.

sisu_sso_screen(SsoTokenSignIn)

When the user signs in using the SSO flow, an event is sent to the system.

• ProviderPackageId – When Microsoft account credentials are used from a product other than that of Microsoft, this attribute contains the identifier of the product from which the credentials are being used, like “com.microsoft.teams”.

sisu_sso_screen(SsoTokenAutoRefreshed)

Whenever a user’s login is automatically refreshed as a result of SSO authentication, this event is sent.

• ProviderPackageId – In the event that Microsoft account credentials are being used from a different product, then this attribute contains the identifier of the product from which the credentials are being used, for example, “com.microsoft.teams”.

sisu_sso_screen(SsoTokenInterrupted)

In the event that the automatic SSO authentication refresh fails, an event is sent to the user.

• ProviderPackageId – It is possible to use the Microsoft account credentials from another product, and in this case, this attribute will contain the identifier of that product in the event that the credentials are being used from another product, for example “com.microsoft.teams”.

sisu_sso_screen(SsoTokenSignedIn)

Whenever a user successfully signs in using the SSO flow, an event is sent to the user’s account.

• ProviderPackageId –
•  It is important to mention that this attribute contains the identifier of the product from which the Microsoft account credentials are being used, for instance the vendor name “com.microsoft.teams”, if the credentials are being used from another product.

sisu_refreshtoken_error

If the automated login refresh fails, then this event will be sent as a result. The purpose of this collection is to measure the health of the automated login refresh process.

• ErrorCode – This is the failure error code.
• TokenSource – Indicates which system is involved in the re-login.

• ErrorName – An error name is a description of what the actual error is that is causing the issue, which allows us to refer back to the related code.
• ErrorMessage – This is a more detailed description of the error.
• IsFirstTimeSignIn –
• The first time this user signs in to Skype, a Skype federated profile is created for that user. You can now find users via Skype’s search directory, for example, if you’re looking for a particular user.

sisu_auto_signin

This is a bundle of events related to the auto sign in process which utilises Windows Account Manager (WAM) in order to automate the process. The user has a pre-filled option to sign in with the same personal account as that of the Windows operating system. You have the option of selecting any of the personal accounts from Windows that are available. In order to measure the health of the autosign in flow, this data is collected.

Common attributes for sisu_auto_signin events.

• Action – When you designate a specific event, then it is possible to group the events together and measure the health of each of the specific stages.
• IsFirstTimeSignIn –
•  The Skype federated profile will be created if the user signs in for the very first time through Skype. It is now possible to search for users within the Skype search directory, for example, as an example.

sisu_auto_signin(WAMCacheInvalidated)

When the WAM authentication data needs to be refreshed, the system sends this event to notify the user.

sisu_auto_signin(WAMLoginFailure)

In the event that the user has been unable to sign in using WAM, the event will be sent.

sisu_auto_signin(WAMLoginCompleted)

WAM sends an event when the user has successfully signed in using WAM for the first time.

sisu_auto_signin(WAMTokenRequested)

As soon as the system requests the login of a user, the event is sent.

• IsRefreshRequest – Indicates whether a login refresh has been requested.
• SignInSource – Describes the point at which a user is signed in, for example, the point at which the Skype app was started.
• WamCorrelationId -nThe identifier that we need to be able to group these events together is the one that we need in order to do that. To determine how well the auto sign-in process is working, we collect this information in order to determine how well it is working.

sisu_auto_signin(WAMTokenRetrieved)

In this event, the system sends an update when the login information has been updated.

• IsRefreshRequest – The value of this property indicates whether the login has been refreshed or not after a refresh request has been made.
• SignInSource – The SignInSource of an application can be used for identifying where the user logs in to the application from, for example, where Skype is started.
• WamCorrelationId – As a result of this identifier, we are able to group together the events that occur at the same time. The purpose of this data collection is to determine the health of the auto sign-in process.

sisu_auto_signin(WAMTokenRetrievalFailure)

In the event that the system is unable to update its login information, the event is sent.

• ErrorCode – This is the failure error code.
• ErrorMessage – This is a very detailed description of the error.
• HResult – This is the descriptive name of the error which allows us to refer to the code that is related to this error code.
• IsRefreshRequest – This field indicates whether or not the login refresh has been requested.
• SignInSource – Describes the point at which a user is asked to sign in, such as when the Skype application was started.
• WamCorrelationId – In order to categorize events together, we need to use this identifier. This data is collected to measure the health of the automatic sign-in process.

sisu_auth_background_refresh

There are a number of events associated with automatic login updates in this bundle. This information is collected to measure the health of the flow of automatic login updates.

Common attributes for sisu_auth_background_refresh events.

sisu_auth_background_refresh(RefreshScheduled)

As soon as the automatic login update has been scheduled, an event is sent to the user.

• Action – This action identifies the specific event that occurred so it can be grouped with other events and we can measure the health of those stages.

sisu_auth_background_refresh(UpdateTriggered)

When the automatic login update has been performed, the event is sent to the user.

• Action – Identifies the exact event that has occurred so that we may group the events and measure the health of the specific stages.

sisu_auth_background_refresh(HasValidToken)

The system will send the event whenever the current login has been determined to still be valid by the system.

• Action – Is used for identifying the exact event in order to group the events and measure the health of the particular stages.

sisu_login_logout

Bundle of events related to the process of logging out for a user. Logout flow data is collected to measure how well the logout process is working.

Common attributes for sisu_login_logout events.

• Action – This action identifies the exact event so we can group the events and measure the health of the specific stages.

sisu_login_logout(RedirectToLogin)

The event is sent after successful logout.

• Reason – This is a description of what/where the logout was initiated.
• ErrorCode – This is the failure error code.
• TimeSinceLastRefresh – This is the exact time at which the login system was last updated.
• ErrorCorrelationId –
• By using this identifier, we are able to group the events together in a logical manner. This information is collected to provide a measure of the health of the logout process.

sisu_login_logout(StartupError)

When the user logs out during the startup of the application, this event is sent to the system.

• Error – This is a descriptive name that describes the error and allows us to refer to the associated code.

sisu_login_logout(Logout)

As soon as the user initiates the log out process, the event will be sent out.

• Reason – This is a description of what/where the logout was initiated.
• IsSaveCredentials – A user’s account will be remembered if he or she selects to do so. In order to measure the health of the one-click sign in flow, this data was collected.

sisu_login_logout(KeychainFailure)

The notification is sent when a user attempts to log out of the application due to the application not being able to retrieve the user’s password from the system password manager at the time.

• Error – This is a verbose description of what caused the error.
• FailureType – This is the descriptive name of the error that is used by the system to refer to the associated code.
• TokenType – Indicates what type of system is involved in the logout flow.

sisu_login_logout(TokenIssue)

An event is sent when there is a corruption or malformation in the system login. This information is collected in order to measure the health of the logout process.

• TokenType – Indicates the type of system that is involved in the logout flow.
• TokenIssueType – This is a verbose description of the problem that is occurring when logging in.
• Source – This is a description of the system that is involved in the login.

sisu_phone_verification

An event bundle related to the Microsoft account phone number and email verification process in Skype is a collection of events. User accounts are becoming more secure as a result of phone number and email flows. The purpose of this data collection is to measure the health of the flow of phone number and email verifications.

Common attributes for sisu_phone_verification events.

• Stage – Describes the state at which the phone number or email address is in during the process of verification.
• Error – This is a description of errors which may occur during the phone number or email verification.

sisu_phone_verification(UIStart)

The event is fired when a popup appears on the screen for the verification of the phone number or email address.

• Actions – Defines the exact event to be grouped so that we can measure the health of specific stages, and we can monitor the progress of each stage.

sisu_phone_verification(MsaPhoneAccrualStart)

The event is sent when the pop-up that appears to verify your phone number starts the verification process.

• Action – We use this to designate the exact event in order to group the events and measure the health of the events in the specific stages.

sisu_phone_verification(MsaPhoneAccrualVerified)

In order to properly verify the phone number, an event is sent if the popup confirms the phone number successfully.

• Action – Specifies the exact event that has occurred, in order to group these events and be able to measure the health of each of these stages.

sisu_phone_verification(MsaPhoneAccrualRegistered)

A notification is sent when the login system has successfully verified the verified phone number and has registered it as a user.

• Action – Specifies the exact event that occurred so that we can group the events together and measure the health of the specific stages.

sisu_phone_verification(MsaEmailAccrualVerified)

If the email address entered in the popup has successfully been verified in the popup, this event will be sent.

• Action – Identifies the exact event so that we can group the events together in order to determine the health of the individual stages.

sisu_phone_verification(MsaEmailAccrualRegistered)

This event is sent once the login system has successfully registered the verified email address as a user.

• Action – Interact with a specific event in order to be able to group the events and to measure the health of the particular stages.

sisu_phone_verification(MsaPhoneAccrualCancelled)

As soon as the user aborts the process of verifying the phone number, this event is sent.

• Action – By defining the exact event, we are able to group the events together and measure how health is being maintained during the specific stages.

sisu_phone_verification(MsaPhoneAccrualError)

The event is dispatched when a phone number verification error occurs during the flow of verifying the number.

• Action – Defines the exact event that will allow us to group the events in a way that allows us to measure the health of the specific stages.

sisu_qso

This is a bundle of events related to the user going through the quick sign on flow (QSO). With QSO, the user is able to sign out of the application with an option to “Remember the account” when signing out of the application. As a result, the user is able to sign in to Skype with just a single click of the mouse. In order to measure the health of the QSO flow, this data is collected.

Common attributes for sisu_qso events.

sisu_qso(Started)

When a user starts the flow of QSOs, an event is sent to the system.

• Action – We must be able to identify the correct event so that we can group the events and measure the health of the stages.

sisu_qso(AutoRefreshed)

After the login has been successfully refreshed, the system sends this event.

• Action – In order to be able to group the events and measure health of each stage, we must designate the exact event for each of the stages.

sisu_qso(Interrupted)

When an error occurs during a QSO, this event is sent to indicate that the QSO has been interrupted.

• Action – Specifies the specific event so that we are able to group the events in a particular order and measure the health of those stages.

sisu_qso(SignedIn)

As soon as the user has successfully signed in, the event is sent to the server.

• Action – Identifies the exact event that took place so that we can group the events and measure the health of those specific stages.

sisu_qso(AccountListFetched)

As a result of this event being sent, the device will give you a list of all the user accounts we have on the system that are available for use with QSO flow.

• AccountListSize – This is the number of accounts that are available for QSO.
• Action – Identifies the particular event in order to be able to group those events together and measure the progress of the particular stages.

sisu_guest_meetnow

An event bundle tracking the functionality of a guest user to create a conversation is bundled together into this event bundle.

• SisuPageName – This is the name of the page inside the application where the creation of the conversation was initiated from.
• IsPresentedAsMainCTAButton – For the purpose of indicating whether or not the creation of guest conversations is considered the primary action.
• IsFirstTimeSignIn – When this user signs in to Skype for the first time, a federated user profile will be created if it is the first time it is ever created. In the Skype search directory, for example, you can now find a user by searching for his or her name.

sisu_msa_qr_sign_in

Monitored to ensure the QR sign-in is working.

Common attributes for sisu_msa_qr_sign_in events.

• Action – Identifies the type of action that is being tracked.
• QrShowType – Depending on which flow is used to display the QR code, this will track which flow was used.
• ErrorType – An error type in the QR code sign-in process that the user encountered during the sign-in process.
• ErrorStatus – This request is for the status of the failed authentication that occurred in the QR code sign-in process.
• IsFirstTimeSignIn –
• The first time a user signs in to Skype for the first time, a Skype federated profile will be created by Skype for that user. It is now possible to find a user by using the Skype search directory, for example.

sisu_msa_qr_sign_in(QrSignInSuccessful)

This tracker is used for monitoring the health of QR sign-in processes for the purpose of tracking the success of QR code sign-in processes.

• Action – This is the base for QR sign-in actions.

sisu_msa_qr_sign_in(QrSignInTokenExchangeFailed)

In order to monitor the health of QR code sign-in, it keeps track of failed QR sign-in processes.

• Action – This is the base for QR sign-in actions.

sisu_msa_qr_sign_in(QrSignInQrCodeRenderedSuccessfully)

It keeps track of the successful rendering of QR codes for the purpose of monitoring the health of QR code sign-ups.

• Action – This is the base for QR sign-in actions.

sisu_msa_qr_sign_in(QrSignInQrCodeRenderFailed)

In order to monitor the health of QR code sign-ins on the Web client, this function tracks unsuccessful QR code rendering on the Web client.

• Action – The base class for QR sign-in actions.

sisu_msa_qr_sign_in(QrSignInNotAvailable)

Keeps track of scenarios in which QR code sign-in is not available at the moment.

• Action – The base class for QR sign-in actions.

sisu_msix_background_task

Monitoring of the user’s authenticated state to ensure that it is correctly preserved while the user is not using the app to ensure that it is preserved correctly.

Common attributes for sisu_msix_background_task events.

• Action – This is the name that is assigned to the action that is being tracked.
• IsSuccessful – This variable is used to keep track of the success rate of the background refresh process.

• CorrelationId – This is a unique identifier that is used to correlate the events that are linked to the background refresh process. Monitors the health of the process in order to ensure it is operating properly.
• BackgroundTaskName – This is the name of the background task that has been started.
• BackgroundTaskTriggerType – Indicates that a background task is the type that was triggered when it was started.
• TimeTriggerInterval – The number of minutes until the background task fires again.

sisu_msix_background_task(Register)

It keeps track of the number of background task registrations that have been successful in order to monitor the health of the background token refresh process in the future.

sisu_msix_background_task(Unregister)

In order to monitor the health of the background token refresh process, this tracker keeps track of the successful unregistration of a background task.

sisu_msix_background_task(UnregisterAll)

It keeps track of all background tasks which have successfully been unregistered so that health of the background token refresh process can be monitored.

Examples of Required Service Data events.

calling_call

When the user answers the call, this data is collected, which helps to track the health and reliability of the scenario.

• CallingStack – This is a method used to identify the type of technology used for calls in order to evaluate the performance of different technologies.
• IsMeetNow – Use this attribute to determine whether this is a “Meet Now” call.
• IsGroupCall – This is an indicator of whether this particular call is a group call.
• IsPSTNCall – This field is used to indicate whether this call is a PSTN call.
• IsCallCreator – This variable is used to indicate whether the current user initiated the call.
• IsTranslatedCall – This value indicates whether or not this call is being translated by the Skype Translator service.
• StartCaptioningCount – This is the number of times the user has attempted to start captioning the call per call.

• StopCaptioningCount – The number of times a user has attempted to stop call captioning during a call.
• StartPstnTranslationAttemptCount – This is the number of times the user has attempted to start PSTN translation of a call per call, to ensure that the translation is working.
• DidReceiveCaptions – Provides information whether captions have been received, which helps to determine the health and reliability of captioning and translation services.
• FirstCaptionReceivedLengthSeconds – This is the number of seconds between the time the captioning session began and the time the first caption was received.
• FailedCaptioningConfigCount – Defines how many times the captioning service has failed during the current call.
• ReceiverSetupCount – Indicates how many times the captioning service has set up the receiver setup.
• ConversationId – The number identifies the call in the context of the conversation it is attached to.
• StartVideoCount – This is the number of times during the current call a video stream has been started during the call.
• StartScreenSharingCount – Indicates the number of times a screen-sharing session has been launched within the current call.
• StopScreenSharingCount – The number of times the screen sharing has been paused during the current call.
• StartSoundSharingCount – Indicates how many times sound sharing has been initiated during the current call.
• CancelScreenSharingCount – Indicates how often screen sharing has been canceled during the current call.
• ScreenSharingDroppedCount – This is a count of how many times screen sharing has been cancelled during the current call due to an error.
• StartRecordingCount – Indicates how many times a call recording has been initiated during the current call.
• StopRecordingCount – Counts the number of times the recording of the call has been stopped during the current call.
• StartNdiCount – Indicates how many times NDI has been started during the current call.
• StopNdiCount – Indicates how many times NDI has been stopped during the current call.
• MaxConnectedParticipants – This is the number of times NDI has been stopped during the current call.
• ToggleVideoSuccessfulCount – This value indicates how many times the video camera was switched on or off during the current call.
• StartBackgroundBlurCount – Indicates how many times the background blur has been enabled during the current call.
• StopBackgroundBlurCount – This value indicates how many times background blur has been disabled during the current call.
• StartBackgroundEffectBlurCount – Indicates how many times background blurs have been enabled during the current call.
• StopBackgroundEffectBlurCount – This value indicates how many times background blur has been disabled during the current call.
• StartBackgroundEffectImageCount – This is a count of how many times background replacement has been activated during the current call.
• StopBackgroundEffectImageCount – Indicates how many times the background replacement has been disabled during the current call.
• BingBackgroundEffectCaptionClickCount – This is a count of the number of times users clicked on the Bing Background Info Caption during the current call.
• ScreenShareControlSentControlRequestCount – This is the number of requests for control over the screen sharing that have been sent during the current call.
• ScreenShareControlRequestAcceptedCount – This is the number of requests for control over screen sharing that have been accepted during the current call.
• ScreenShareControlRequestDeniedCount – This is the number of times that a request for control over screen sharing has been denied during the current call.
• ScreenShareControlGrantedCount – This is a count of how many requests for control over screen sharing have been granted during the current call.
• HadNewCallStageEnabled –  Indicates whether a new stage has been used on the call. Performance tracking is used to keep track of how well a system is performing.
• HadOldCallStageEnabled –  Indicates if the old stage was used during the call. Tracks the performance of the application.
• AverageCallingStoreUpdateTime – This is a measure of how long it averages for the calling store update to take place over time. For the purpose of tracking performance, this file is used.
• Source – Lets us know how and where the conversation was created (outside of the client), which helps us track the performance of the partners’ flows.
• ZoomedInCount – This is the number of times the screen share zoom in feature was used during the current call.
• ZoomedInDuration – This is a measurement of the length of time that the screen share zoom has been used during the current call.
• ZoomedOutCount – Indicates how many times the screen share zoom out function was used during the current call.
• ZoomDragUsed – Indicates whether or not zoomed-in screen sharing drag was used during the current call.
• ZoomUIControlsUsedCount – Indicates how many times the zoom controls on the screen share were used during a call.
• ZoomScrollWheelUsedCount – This is the number of times the mouse wheel was used to control the zoom of the screen share during the call.
• ZoomKeyboardUsedCount – This is the number of times the keyboard has been used to control the zoom of the screen share during a call.
• ZoomTrackPadUsedCount – The number of times the track-pad was used to control the zoom of the screen share during the course of a call.
• ShowShareTwinCamConnectionCount – This is the number of times that the Share QR code was shown.
• TwinCamConnectionUsedCount – Counts the number of times TwinCam has been used to connect to the call.
• TwinCamConnectionFailedCount – This parameter is a count of the number of times TwinCam failed to connect to the call.
• StopTwinCamCount – This is the number of times that the Stop TwinCam button has been pressed.
• AbleToStartTwinCam – This is an indicator of how many times the possibility existed to add TwinCam.
• CallManagerUsed – Indicates whether the current call manager was used during the current call.
• IsIgnoringBatteryOptimizations – This is an indication of whether or not the battery optimization settings are ignored for Skype on Android devices. To reduce issues with the notification of incoming calls, this feature is used.
• CaptionsPositionModeChangeCount – This is the number of times the captions position mode has been changed.
• LastCaptionsPositionMode – The view of the captions that was last used by the user.
• CaptionsStartingMessageClickedCount – The number of times the captions start message has been clicked.
• CallId – An identifier which uniquely identifies this call within Skype’s systems.
• CallDurationSeconds – This is the duration of this call measured in seconds.
• ParticipantId – Unique identifier of this user as a participant in this call.
• ToggleCameraCount – This is the number of times that the camera has been toggled on and off during this call.
• LocalMuteCount – This is the number of times the microphone was turned off during this call.
• LocalUnmuteCount – This is the number of times that the microphone was turned on during the course of this call.
• Origin – Indicates the location from within the Skype client where this call was initiated.
• CallConversationMriNamespace – The type of the conversation to which this call is attached specifies what type of call this is. You can engage in a private chat with another Skype user, participate in a group call or have a conversation with another user of Teams, for instance.
• CallConnectionDurationMilliseconds – Measures how long it took for the current call to be connected to the previous one (in milliseconds).

messaging_sms

The One Way SMS Feature is tracked by this event. This is used to keep track of errors that occur when sending one way SMS messages.

• Action – A specific action relating to the one-way SMS feature (e.g. SMS Delivery Failed).
• ClientMessageId – The ID of the message where the error occurred.
• ErrorCategory – This is a category that describes the type of error that occurred.
• Status – Indicates the error code that was assigned when the error ocurred.

It is only from installed desktop clients that the following events are sent.

Common attributes for all events.

• Platform_Uiversion –  This is the combination of the platform id and the Skype version number. Our data can be classified according to platform and version pivots by using this classifier.
• Platform_Id – Numeric id for a platform type (1418 – Web, 1419 – Android, etc.). Provides us with the ability to establish health metrics for a platform based on the platform id.

• Locale – This is the user-configured display locale of the operating system or device. As a result, we are able to recognize issues related to the location of the operating system or device.
• Locale – Skype display locale. Provides us with the ability to recognize issues related to display locales.
• Version – Used to correlate telemetry data to a specific Skype version. As a result, we can determine if the version is healthy or not.
• Language – This is Skype’s display language. This allows us to recognize issues that are related to display languages.
• Language – The language in which the user has configured the display of the operating system or device. This allows us to identify any issues relating to the language of the operating system or device.
• TimeZone – This is a user-configurable time zone.
• Id – Anonymized (hashed) unique ID of user. This enables us to establish core health metrics based on user impact and Skype usage statistics in order to determine how we are doing.
• OsName – Operating system name. As a result, we are able to identify any issues related to the operating system.
• OsVersion – Operating system version. We are able to recognize problems that are related to the version of the operating system.
• Id – Id that uniquely identifies the specific device. As a result, we can gain a better understanding of the impact of various factors. As an example, if a certain issue is only affecting one or more devices at a time.
• BrowserName – The name of the browser (Edge, Chrome, …). Using this information, we can determine health metrics based on a particular web browser.
• BrowserVersion – This is the version of the browser. We are able to establish health metrics based on the version of the web browser we are using.
• OsBuild – The build number of the operating system. Identifies issues relating to the build of the operating system and allows us to fix them.
• Name – The name given to this telemetry event.
• SdkVersion – This is the SDK version of the telemetry management system that is used by the application (ARIA).
• Source – This identifies a specific sub-component, for example a library or component, used to identify a specific point in the code where instrumentation is taking place in the code.
• Time – This is the UTC time on the client when this event occurred.

Required events.

client_startup

In order to measure the quality of service, this is a measure of startup performance on Windows, Macintosh and Linux.

• startup_time – This is the time at which the desktop client starts up. Provides us with the ability to establish performance health metrics.
• is_background_token_refresh_startup – This is a flag that specifies whether or not the main process has woken up to refresh the login token. As a result, we are able to establish health metrics.
• correlation_id – Unique id of current session. In this way, we are able to better understand the impact of various things that are happening. We are able to correlate issues and establish health metrics as a result of this.
• DeviceInfo_OsVersion – This is the name of the operating system. Provides us with the ability to recognize issues that are related to the operating system.

client_cert_selection

An authentication request is sent whenever a service requires the authentication of a client certificate. The purpose of this collection is to measure the health of the authentication procedures used by an application.

• endpoint_origin – The origin of the client certificate authentication request that was sent to the endpoint.
• DeviceInfo_OsVersion – This is the name of the operating system. As a result, we are able to recognize issues that are related to the operating system.

restart_for_update

Keeps track of when the operating system has to be restarted in order to complete the update process after it has been updated. In this way, we are able to identify issues with the update process as soon as possible so that they can be resolved in a timely manner.

• DeviceInfo_OsVersion – This is the name of the operating system. Provides us with the ability to recognize issues related to the operating system.

renderer_crashed

For health metrics purposes, this is sent when the renderer crashes on Windows, Macintosh, or Linux.

• CrashType – Crash type (e.g., process is unresponsive or process unexpectedly disappears).
• Reason – Crash reason (e.g., out of memory, killed, launch failed).
• CallStatus – State of the calling before the crash (e.g., no call was happening, during call or right after calling).

• DeviceInfo_OsVersion – Operating system name. Provides us with an opportunity to identify issues related to operating systems.

main_crashed

When a crash occurs in the main process on Windows, Macintosh or Linux, this is used as a health metric.

• CrashType – Crash type (e.g., exception occurred or native crash).
• DeviceInfo_OsVersion – This is the name of the operating system. As a result, we are able to identify issues that are related to the operating system.

main_quit_after_background_token_refresh

This is a notification that is sent when the main process quits gracefully after refreshing the token, which is used for health metrics, on Windows.

• TokenRefreshResult – The result of the token refresh (e.g. whether refreshing the token was successful, if it timed out, or if it errored).
• correlation_id – Unique id of current session. As a result, we are able to better understand how various things have an impact on our lives. As a result, we are able to establish health metrics and correlate issues.
• DeviceInfo_OsVersion – This is the name of the operating system. Provides us with the ability to recognize issues that are related to the operating system.

ComProcessStartedEvent

As soon as the operating system starts up the background process host, this message is sent. The background job can be monitored in order to establish health metrics for it.

• Action – A background job action that takes place in the background (e.g. it starts, it finishes, it stops, etc.).
• PackageVersion – The version number of the Skype MSIX app package. As a result, the health of the version can be established.
• PackageName – The name of the Skype MSIX app package. As a result, the health of the version can be determined.
• OsDescription – This is the operating system version information. As a result, we are able to recognize issues that are related to the build of the operating system.
• Timezone – This is the timezone in which the client is located. Provides us with an understanding of what time the event occurred on the client when it occurred.
• Version – The purpose of this field is to correlate telemetry data with the specific Skype version. As a result, the health of the version can be determined.
• Language – The language in which Skype displays information. Provides us with the ability to recognize issues related to display language.
• Language – This is the language that is configured by the user for the display of the operating system or device. It allows us to identify issues related to the language of the operating system or device.
• TimeZone – This is a user-configurable time zone.
• Id – Anonymized (hashed) unique ID of user. The Skype usage statistics and the user impact data will be used to establish a key health metric for the product.
• OsName – This is the operating system name. This allows us to identify issues related to operating systems that need to be addressed.
• OsVersion – This is the operating system version. We are able to recognize issues related to the version of the operating system by using this feature.
• Id – Id that uniquely identifies the specific device. As a result, we are able to understand the impact of various things better. When an issue affects only one or more devices at the same time, for instance.

• BrowserName – The name of the web browser (Edge, Chrome, …). By knowing the name of the web browser, we are able to measure the health of the system.
• BrowserVersion – This is the version of the browser. Provides us with the ability to establish health metrics based on the version of a web browser.
• OsBuild – This is the operating system build number. Provides us with the ability to recognize issues related to the operating system’s build.
• Name – This is the name of the telemetry event.
• SdkVersion – This is the SDK version of the telemetry management system (ARIA).
• Source – This is the name of the client-specific subcomponent, such as the library or component, which is used to identify the instrumentation point in the code.
• Time – This is the time in UTC on the client’s system when this event occurred.

ComProcessStoppedEvent

When the background process host is stopped, this message is sent. In order to monitor how well the background job is performing, we need to establish health metrics for it so that we can monitor its health.

• Action – Background job action (i.e. started, completed successfully, stopped, etc. ).
• PackageVersion – Skype MSIX app package version. Consequently, it is possible to determine the health of the version as a consequence of this.
• PackageName – Skype MSIX app package name. In this way, the health of the version can be established.
• OsDescription – Operating system version information. We are able to identify issues related to the operating system’s build if we have this information.
• Timezone – The client timezone. We are able to determine the time when the event occurred on the client by using this information.
• Version – This is used in order to correlate telemetry with the specific Skype version. By doing so, it is possible to establish the health of the version.

• Language – Skype display language. Detects display language related issues and allows us to resolve them.
• Language –  This is the language that is configured by the user for the display of the operating system or device. Provides us with the capability of recognizing language-related issues related to operating systems or devices.
• TimeZone – This is the time zone that is configured by the user.
• Id – Anonymized (hashed) unique ID of user. As a result, we are able to establish core health metrics for Skype based on usage statistics and user impact metrics.
• OsName – This is the operating system name. The ability to recognize issues that are related to an operating system allows us to identify them.
• OsVersion – This is the operating system version. We are able to recognize issues associated with a particular version of the operating system based on the information provided by this function.
• Id – Id that uniquely identifies the specific device. Allows us to better understand impact of various things. Suppose, for example, there is a problem that only affects one or a few devices at a time.
• BrowserName –  The name of the browser (Edge, Chrome, …). By doing this, we are able to put together health metrics based on the type of browser that is being used.

• BrowserVersion – Browser version. We can establish health metrics based on the version of the web browser that a user is using.
• OsBuild – The build number of the operating system. Provides us with the ability to recognize issues related to the build of an operating system.
• Name – This is the name of the telemetry event.
• SdkVersion – This refers to the SDK version of the telemetry management system (ARIA).
• Source – The name of the subcomponent that belongs to the client, such as the library or component, is used to identify the instrumentation point in the code.
• Time – This is the time in UTC on the client when the event occurred.

TokenRefreshBackgroundTaskEntryPointEvent

A notification is sent when an authentication token refresh action is started in the background process. Provides us with the ability to establish health metrics related to the background refreshing of the authentication token in the background.

• TaskName – The name of the background task. This feature allows us to establish health metrics for background authentication token refresh tasks that are running in the background.
• TaskInstanceId – The instance ID of the background task. The background authentication token refresh task can be monitored in order to establish health metrics for it.
• DaysUntilTokenExpires – This value indicates how many days are left until the authentication token expires. Provides us with the ability to monitor the health of background authentication tokens by establishing health metrics.
• TokenRefreshExpirationThresholdInDays –  The maximum number of days left before a token expires when we are allowed to skip the background token refresh. As a result of this function, we are able to establish health metrics for the background authentication token refresh process.
• ShouldTryToStartSkypeProcess – Indicates whether the background task intends to attempt to refresh the authentication token in order to continue processing or if it plans to skip it. The background authentication token refresh task can be tracked in terms of its health metrics in the background.
• Action – A background job action (for example, it can be started, completed successfully, stopped, etc. ).
• PackageVersion – Skype MSIX app package version. It is important to establish the health of the version through this process.
• PackageName – Skype MSIX app package name. In this way, the health of the version can be established.
• OsDescription – Operating system version information. Provides us with the ability to recognize any issues related to the build of an operating system.

• Timezone – This is the timezone of the client. This gives us the ability to determine when an event occurred on the client as a result of this.
• Version – This is used to correlate telemetry data with the specific Skype version. The purpose of this is to establish the health of the version.
• Language – The language in which Skype displays the messages. As a result, we are able to identify display language-related issues.
• Language – The language that is configured by the user for the display of the operating system or device. This allows us to recognize problems related to the language of the operating system or device.
• TimeZone – This is a user-configurable time zone.
• Id – Anonymized (hashed) unique ID of user. By analyzing user impact and Skype usage statistics, we will be able to establish core health metrics based on the impact of users.
• OsName – This is the operating system name. This allows us to recognize issues that are related to the operating system.
• OsVersion – This is the operating system version. Provides us with the ability to recognize issues that are related to the version of the operating system.
• Id – Id that uniquely identifies the specific device. Provides us with a better understanding of the impact of various factors in our lives. When, for example, a particular issue is affecting only one or a few devices at the same time.
• BrowserName – The name of the browser (Edge, Chrome, …). Using this parameter we can establish health metrics based on the browser we are using.
• BrowserVersion – This is the version of the browser. It allows us to establish health metrics based on the version of the web browser we are using.
• OsBuild – This is the operating system build number. Provides us with the ability to recognize issues related to the build of the operating system.
• Name – This is the name of the telemetry event.
• SdkVersion – This is the version of the SDK that represents the telemetry management system (ARIA).
• Source – Determines the name of the sub-component that is specific to the client, such as the library or component, for the purpose of identifying the instrumentation points in the code.
• Time – This is the time in UTC which was displayed on the client when the event occurred.

TokenRefreshBackgroundTaskCompletedEvent

A message is sent when the authentication token refresh action in the background process has been completed successfully. As a result of this feature, we can establish health metrics that can be used to determine the effectiveness of the background refresh process.

• TaskName – Background task name. The background authentication token refresh task can be monitored in order to establish a health metric for that task.
• TaskInstanceId – The instance ID of the background task. Providing us with the ability to establish health metrics for the task of refreshing authentication tokens in the background.
• Action – Describes the action taken as part of a background job (e.g. starting, completing, stopping, etc. ).
• PackageVersion – Skype MSIX app package version. This helps to establish health of the version.
• PackageName – Skype MSIX app package name. As a result, we are able to establish the health of the version.
• OsDescription – Operating system version information. This allows us to recognize issues that are related to the build of the operating system.
• Timezone – The client timezone. The time at which the event occurred on the client helps us to understand when the event occurred on the client.
• Version – This information is used in order to correlate telemetry with a specific version of Skype. In this way, we can determine whether the version is in good health.
• Language – The language of the Skype display. Detects display language-related issues and allows us to resolve them as soon as possible.
• Language – This is the language that the user has configured for the display of the operating system or device. We are able to recognize issues related to the language of the operating system and the device.
• TimeZone – This is a user-configurable time zone.
• Id – Anonymized (hashed) unique ID of user. Based on the impact of the application on the user and Skype usage statistics, we can establish core health metrics for the application.
• OsName – This is the operating system name. Provides us with the ability to recognize issues that are related to the operating system.
• OsVersion – This is the operating system version. As a result, we are able to recognize issues related to the operating system’s version.
• Id – Id that uniquely identifies the specific device. Provides us with a better understanding of the impact of various things on our lives. Suppose, for instance, that some issue is only affecting one or multiple devices at the same time.
• BrowserName – The name of the web browser (Edge, Chrome, …). Using this information, we can establish health metrics based on the web browser that is used.
• BrowserVersion – This is the version of the browser. Based on the version of the web browser that is being used, we can establish health metrics.
• OsBuild – This is the operating system build number. As a result, we are able to recognize issues related to the build of the operating system.
• Name – Name of this telemetry event.
• SdkVersion – This is the version of the SDK that contains the telemetry management system (ARIA).
• Source – This is the name of a sub-component that is specific to the client, such as a library or component, that is used to identify the instrumentation point in the code.
• Time – This is the time in UTC when this event occurred on the client at the time this event occurred.

TokenRefreshBackgroundTaskCancelledEvent

This event is sent when the operating system cancels the authentication token refresh action during the background process. As a result, we are able to establish health metrics to monitor the refresh of an authentication token in the background.

• TaskName – Background task name. The authentication token refresh task can be monitored in the background using health metrics that are collected.
• TaskInstanceId – Background task instance ID. The background authentication token refresh task can be used to establish health metrics so that the task can be monitored in the future.
• CancellationReason – This is the reason for the cancellation of the background task sent by the operating system. The background authentication token refresh task is able to establish health metrics that can be used to monitor its performance.
• Action – Describes the action that was taken in the background when the job was started, completed successfully, stopped, etc. ).
• PackageVersion – Skype MSIX app package version. As a result, the health of the version can be determined.
• PackageName – Skype MSIX app package name. In this way, you can determine whether the version is healthy or not.
• OsDescription – This is the operating system version information. It allows us to identify issues that are related to the build of the operating system.
• Timezone – This is the timezone in which the client is located. We are able to determine the time on the client when the event occurred by using this information.
• Version – Creates a link between telemetry information and the specific Skype version. In this way, the health of the version can be determined.
• Language – Skype display language. Provides us with the ability to identify issues related to display languages.
• Language – User configured display language of the operating system or device. As a result, we are able to recognize any language related issues that may exist with the operating system or device.
• TimeZone – This is a time zone that is configured by the user.
• Id – Anonymized (hashed) unique ID of user. By analyzing the user impact and Skype usage statistics, we are able to establish key health metrics based on the user impact.
• OsName – This is the operating system name. Provides us with the ability to identify issues related to the operating system.
• OsVersion – This is the operating system version. As a result, we are able to recognize issues related to the operating system’s version.
• Id – Id that uniquely identifies the specific device. As a result, we are able to better understand the impact of various things on each other. As an example, if some issue affects only one or several devices at the same time.
• BrowserName – The name of the browser (Edge, Chrome, …). Using this information, we are able to establish health metrics based on a particular web browser.
• BrowserVersion – This is the version of the browser. This enables us to establish health metrics based on the version of a web browser we are using.
• OsBuild – This is the operating system build number. This allows us to recognize any issues that are related to the build of the operating system.
• Name – This is the name of the telemetry event.
• SdkVersion – This is the version of the SDK that represents the telemetry management system (ARIA).
• Source – This is a sub-component name that is specific to the client, such as a library or piece of code, which identifies the instrumentation point in the code.
• Time – This is the UTC time on the client when this event occurred.

SkypeProcessStartFailedForTokenRefreshEvent

This message is sent when the authentication token refresh process for the background process fails to start. Provides us with the ability to establish health metrics for the background refresh of the authentication token in order to monitor its health.

• TaskInstanceId – The instance ID of the background task. It allows us to determine the health of the background task that is responsible for refreshing authentication tokens in the background.
• FailureReason – This is the reason why the background authentication token refresh process failed. Provides us with the ability to establish health metrics for the background authentication token refresh task in order to track its progress.
• HResultErrorCode – This is the error code that is sent by the operating system when the authentication token refresh process fails. Allows us to establish health metrics for the background authentication token refresh task in order to assess its performance.
• Action – The action performed by the background job (e.g. if it has started, completed successfully, stopped, etc. ).
• PackageVersion – Skype MSIX app package version. As a result, the health of the version can be established.
• PackageName – Skype MSIX app package name. In this way, the health of the version can be established.
• OsDescription – Information about the version of the operating system. Provides us with the ability to identify issues related to the build of the operating system.
• Timezone – This is the client’s timezone. As a result of this information, we will be able to determine when the event occurred on the client.
• Version – This is used to correlate telemetry data with the specific Skype version. As a result, the health of the version can be established.
• Language – Skype display language. Provides us with the ability to recognize issues that are related to the display language.
• Language – This refers to the display language that has been configured by the user for the operating system or device. It allows us to identify issues that are related to the language of the operating system or the device.
• TimeZone – This is the time zone that is configured by the user.
• Id – Anonymized (hashed) unique ID of user. Based on the usage statistics of Skype and the impact of users on the service, we are able to establish core health metrics.
• OsName – This is the operating system name. As a result, we are able to identify issues related to the operating system.
• OsVersion – This is the operating system version. This allows us to recognize issues that are related to a particular version of the operating system.
• Id – Id that uniquely identifies the specific device. Provides us with a better understanding of the impact of various things on our lives. Suppose, for instance, that there is a problem that is affecting only one or multiple devices at the same time.
• BrowserName – The name of the browser that you are using (Edge, Chrome, …). This information allows us to establish health metrics based on a browser that you are using.
• BrowserVersion – This is the version of the browser. This allows us to establish health metrics based on the version of the web browser that is being used.
• OsBuild – This is the operating system build number. This enables us to identify issues related to the build of an operating system.
• Name – This is the name of the telemetry event.
• SdkVersion – This is the SDK version of the telemetry management system (ARIA).
• Source – Name of a client-specific sub-component, such as a library or component, that is used to identify the instrumentation point in the code.
• Time – This is the UTC time on the client when this event occurred.

TokenRefreshBackgroundTaskFailedEvent

This message is sent when the authentication token refresh task in the background process fails for unknown reasons. As a result of this, we are able to establish health metrics for the background refreshing of the authentication token in the background.

• • TaskName – The name of the background task. This allows us to establish health metrics for the background process of refreshing authentication tokens in the background.
  • TaskInstanceId – This is the background task instance ID. This allows us to establish health metrics for the background task of refreshing the authentication tokens in the background.
  • ErrorMessage – This is an error message that is displayed when the authentication token refresh background task fails. As a result of this, we are able to establish health metrics for the background task to refresh authentication tokens.
  • HResultErrorCode – This is the error code that the operating system sends when the authentication token refresh background task fails. As a result, we are able to establish health metrics for the background authentication token refresh process.
  • Action – The action taken by the background job (i.e. the job is started, completed successfully, stopped, etc.).
  • PackageVersion – This is the version of the Skype MSIX app package that is available for download. As a result, the health of the version can be established.
  • PackageName – Skype MSIX app package name. By doing this, we are able to establish the health of the version.
  • OsDescription – This is a description of the operating system version information. Provides us with the ability to identify issues related to the build of the operating system.
  • Timezone – This is the client’s timezone. We can use this information to determine what time the event occurred on the client when the event occurred.
  • Version – This feature is used to correlate telemetry with the specific Skype version. As a result, the health of the version can be established.
  • Language – This is the Skype’s default display language. We are able to identify display language related issues based on the information provided.
  • Language – This is the language that is configured by the user for the display of the operating system or device. It allows us to identify issues that are related to the language of the operating system or device.
  • TimeZone – This is a user-configurable time zone.
  • Id – Anonymized (hashed) unique ID of user. As a result, we can establish core health metrics that are based on user impact and Skype usage statistics.
  • OsName – This is the operating system name. As a result, we are able to recognize issues related to the operating system.
  • OsVersion – Operating system version. As a result, we are able to recognize any issues related to the operating system’s version.
  • Id – Id that uniquely identifies the specific device. As a result, we are able to better understand the impact of various things on our lives. There may be instances where some issue is affecting only one or a number of devices at a time.
  • BrowserName – The name of the browser you are using (Edge, Chrome, …). This information allows us to establish health metrics based on the browser you are using.
  • BrowserVersion – Browser version. In this way, we are able to establish health metrics based on the version of a web browser.
  • OsBuild – Operating system build number. In this way, we are able to recognize issues that are related to an operating system’s build.
  • Name – This is the name of the telemetry event.
  • SdkVersion – This is the version of the SDK that comes with the Telemetry Management System (ARIA).
  • Source – This is the name of the client-specific sub-component, such as the library or component, that is used to identify the instrumentation point in the code.
  • Time – This is the UTC time on the client at the time when this event occurred.

Frequently Asked Questions

What information does Skype collect?

 

All images and contents credit goes to supportskype.com