Cloud proxies that have not been configured for these known addresses are the leading cause in dropped telemetry. Please review the network requirements and contact your network team to ensure you have added all listed addresses to your allow lists. If you receive an error such as "failed to fetch" or a "CORS" error, this indicates a problem reaching our CDN. Troubleshooting errors with the License CDN Connection Test If you need to update any of the values, please contact Support. excludeSiteUrls - site URLs that are not to have data collected.disableUserProfileCollection - true if you have opted not to collect user profile information.disableTelemetry - true if you have opted out of tyGraph telemetry.obfuscateUserFields - list of fields that you have opted to obfuscate.User's countries are compared using the Usage Location associated with the user's Microsoft 365 license obfuscateCountries - list of all countries whose users that should be obfuscated when obfuscate has a value of partial.obfuscate - obfuscation settings (none, partial, or all) - controls whether user names and E-mail addresses are obfuscated for requirements such as GDPR.modifiedDate - date values were retrieved from the API.isActive - true if your subscription is active.expirationDate - license expiration date.instrumentaitonKey - your Application Insights instrumentation key.tenantId - your Azure Active Directory tenant id.The meaning of the values are as defined below: The License CDN Connection Test shows both the values retrieved directly rom the API as well as when the last values were cached in your browser. A successful CDN Connection Test will look like the screen below. For a browser to successfully log telemetry, this call must be successful at least once. Each user will make a call to this endpoint once per day but the data is cached locally and is valid for thirty days if the CDN cannot be reached. The License CDN Connection Test will validate that the tyGraph Pages Engine can connect to the tyGraph License CDN to get the instrumentation key and license information. The Health Check validates that the tyGraph Pages Engine can connect to the tyGraph API as well as capture telemetry. After you have configured the web part as described in the instructions with an Application Id and API key, edit the web part and check the box Show tyGraph Pages Engine health check under the Debugging section. If you have not installed and configured the web part, follow these instructions. You can enable Health Check from the tyGraph Pages Site Analytics web part. ![]() ![]() Troubleshooting the API Connection Test.Troubleshooting errors with the License CDN Connection Test.If you suspect multiple users or locations may have issues, you should try the health check with those users and locations. The health check validates connectivity for the current user viewing the web part. Support may ask you to use the health check to troubleshoot issues collecting telemetry. The tyGraph Pages Engine Health Check allows customers to verify that the engine is installed correctly and collecting telemetry.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |