Unable to set `UserJourneyRecorderEndpoint` for use with journey recorder about active-directory-b2c-advanced-policies HOT 4 OPEN

This is really painful during development. First that truncation issue and secondly even in development mode App Insights take ages (at times) to show the data. It would be really nice to allow the possibility to setup your own telemetry service (any https endpoint from where one can setup serilog/logstash etc) to speedup the development process. Current solution is a real productivity killer and frustrating.

from active-directory-b2c-advanced-policies.

The use of a HTTP endpoint for UserJourneyRecorderEndpoint has been deprecated.

How silly. Perhaps un-deprecate it? It's surely not a technological hurdle to fire the same payload at an arbitrary HTTP endpoint. Or send AI telemetry in a more granular, sensible fashion?
Without an answer to the (enormous) event body being truncated, this is posing a significant issue and resource drain when trying to adjust and debug custom policies.

from active-directory-b2c-advanced-policies.

Hi @umar-qureshi2

The use of a HTTP endpoint for UserJourneyRecorderEndpoint has been deprecated.

You must use Application Insights for the user journey recording.

You can read more about this in the Azure Active Directory B2C: Collecting Logs article.

from active-directory-b2c-advanced-policies.

Hi @chrispadgettlivecom

Thank you for guidance. I have been using Application Insights but the trace messages get truncated at 32K character limit as mentioned in data model here. I have two questions about it.

1. Do you know of any workaround to avoid this limit of 32k characters?
   (This typically comes up when I set Development as true and use AD as IDP with custom claims).
2. How can I collect information about requests/responses to identity providers and how long they are taking?

from active-directory-b2c-advanced-policies.