-
Notifications
You must be signed in to change notification settings - Fork 67
ProfileQueryEndpoint is not overridable => application identifiers cannot be resolved #853
Comments
This is by design. Please configure |
Chatted with @SergeyKanzhelev - the issue of not being able to override |
sorry for miunderstanding. Definitely should be fixed |
Adding some context to the conversation while planning how to fix this... This affects the Our current documentation says to override the TelemetryChannel's EndpointAddress if a user is behind a proxy. This is questionably incorrect. Microsoft Docs: "AppInsights Proxy" This should work for a configuration scenario but won't for programmatic configuration. Currently today, |
EDIT: |
@MS-TimothyMothra, tried to add above snippet to above repro and it doesn't look like that it helped. AppIDs are still resolved against main endpoint. |
Fix will be released with 2.6.0-Beta4 |
Description
Application ID resolution feature does not work in our own PPE environment. As a result we cannot use new correlation-based features for monitoring our production.
Repro Steps
Actual Behavior
Notice that application identifiers are still resolved (ProfileQueryEndpoint) against original endpoint. Application Insights doesn't allow to configure this endpoint.
Expected Behavior
Allow applications to configure ProfileQueryEndpoint or construct based on EndpointAddress
Version Info
SDK Version : 2.6-beta2
Code
The text was updated successfully, but these errors were encountered: