Open umar-qureshi2 opened 5 years ago
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.
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.
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.
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.
I am following the document from Setup User Journey Recorder - B2C which mentions to change
UserJourneyRecorderEndpoint
attribute ashttps://<mycustomweb>.azurewebsites.net/stream?id=1a6bee1c-2d3f-4a95-a6a4-440a2c61d336
I have already set
DeploymentMode="Development"
but on uploading the policy file I get the following error.The web app is already deployed. I have also tested with my custom policies and out of the box starter pack policies but get the same error every time.