Capture and analyze logging and telemetry

%3CLINGO-SUB%20id%3D%22lingo-sub-2302721%22%20slang%3D%22en-US%22%3ECapture%20and%20analyze%20logging%20and%20telemetry%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2302721%22%20slang%3D%22en-US%22%3E%3CP%3EI%20guess%20I'll%20give%20this%20a%20shot%20-%20not%20sure%20if%20this%20is%20where%20I%20ask%20my%20question.%20We%20are%20partnering%20with%20the%20FUSE%20Labs%20folks%20on%20building%20our%20first%20production%20call%20flow%20on%20Bot%20Framework.%20One%20area%20we%20are%20struggling%20with%20is%20how%20we%20capture%20and%20analyze%20the%20logging%20and%20telemetry%20related%20to%20our%20inbound%20ACS%20calls%20to%20our%20bot%20channel.%20Also%2C%20how%20are%20call%20detail%20records%20captured%2C%20and%20what%20reporting%20might%20we%20have%20available%20to%20us%20that%20could%20give%20a%20business%20perspective%20on%20the%20service%20itself%20(e.g.%20concurrent%20calls%20in%20progress%2C%20average%20call%20length%2C%20dropped%20calls%2C%20who%20terminated%20the%20call%20(e.g.%20called%20party%20or%20calling%20party)%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2302721%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAMA%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2302908%22%20slang%3D%22en-US%22%3ERe%3A%20Capture%20and%20analyze%20logging%20and%20telemetry%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2302908%22%20slang%3D%22en-US%22%3EWe%20recommend%20using%20Application%20Insights%20to%20collect%20your%20bot%20channel%20insights%20from%20the%20bot%20side%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbot-service%2Fbot-builder-telemetry-analytics-queries%3Fview%3Dazure-bot-service-4.0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbot-service%2Fbot-builder-telemetry-analytics-queries%3Fview%3Dazure-bot-service-4.0%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20would%20need%20to%20do%20some%20work%20to%20combine%20the%20data%20you%20are%20seeing%20from%20ACS%20with%20the%20data%20generated%20by%20the%20bot%20(And%20refer%20to%20an%20ACS%20team%20member%20for%20more%20details%20on%20that%20aspect%20of%20your%20stack)%2C%20but%20feel%20free%20to%20reach%20out%20to%20me%20directly%20and%20we%20can%20find%20out%20the%20best%20person%20to%20do%20that.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2303059%22%20slang%3D%22en-US%22%3ERe%3A%20Capture%20and%20analyze%20logging%20and%20telemetry%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2303059%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F127653%22%20target%3D%22_blank%22%3E%40Peter%20Nilsson%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EAlso%2C%20how%20are%20call%20detail%20records%20captured%2C%20and%20what%20reporting%20might%20we%20have%20available%20to%20us%20that%20could%20give%20a%20business%20perspective%20on%20the%20service%20itself%20(e.g.%20concurrent%20calls%20in%20progress%2C%20average%20call%20length%2C%20dropped%20calls%2C%20who%20terminated%20the%20call%20(e.g.%20called%20party%20or%20calling%20party)%2C%20etc.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1039690%22%20target%3D%22_blank%22%3E%40peterswimm%3C%2FA%3E%26nbsp%3BI%20agree%2C%20this%20information%20will%20be%20imperative%20for%20our%20use%20case%20(a%20customer%20support%20IVR)%20-%20is%20the%20only%20way%20to%20gather%20this%20info%20via%20App%20Insights%20at%20the%20moment%3F%20Any%20plans%20to%20surface%20it%20in%20another%20fashion%20at%20some%20point%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2303338%22%20slang%3D%22en-US%22%3ERe%3A%20Capture%20and%20analyze%20logging%20and%20telemetry%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2303338%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F97202%22%20target%3D%22_blank%22%3E%40Christopher%20Polanish%3C%2FA%3E-%20I%20was%20wondering%20if%20you%20could%20help%20me%20understand%20your%20question%20a%20bit%20better.%20Are%20there%20any%20specific%20ways%20in%20which%20you%20would%20need%20that%20information%20delivered%20that%20is%20different%20from%20App%20Insights%3F%20Is%20there%20a%20reason%20why%20App%20Insights%20is%20not%20something%20you%20would%20want%20to%20use%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

I guess I'll give this a shot - not sure if this is where I ask my question. We are partnering with the FUSE Labs folks on building our first production call flow on Bot Framework. One area we are struggling with is how we capture and analyze the logging and telemetry related to our inbound ACS calls to our bot channel. Also, how are call detail records captured, and what reporting might we have available to us that could give a business perspective on the service itself (e.g. concurrent calls in progress, average call length, dropped calls, who terminated the call (e.g. called party or calling party), etc.

6 Replies
We recommend using Application Insights to collect your bot channel insights from the bot side:
https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-telemetry-analytics-queries?view=azur...

You would need to do some work to combine the data you are seeing from ACS with the data generated by the bot (And refer to an ACS team member for more details on that aspect of your stack), but feel free to reach out to me directly and we can find out the best person to do that.

@Peter Nilsson wrote:

Also, how are call detail records captured, and what reporting might we have available to us that could give a business perspective on the service itself (e.g. concurrent calls in progress, average call length, dropped calls, who terminated the call (e.g. called party or calling party), etc.


@peterswimm I agree, this information will be imperative for our use case (a customer support IVR) - is the only way to gather this info via App Insights at the moment? Any plans to surface it in another fashion at some point?

Hi @Christopher Polanish- I was wondering if you could help me understand your question a bit better. Are there any specific ways in which you would need that information delivered that is different from App Insights? Is there a reason why App Insights is not something you would want to use?

Absolutely, we plan to support multiple types of scenarios but will be working from the framework of app insights as to the method for data insights, and along the way people should be able to use those reference materials as a basis for alternative solutions. Would love to hear more about your requirements, please feel free to drop me a line: peterswimm@microsoft.com
We ultimately want to surface some of that info in a dashboard for our phone answerers - current calls, people on hold, average call length, etc.
In our (bot framework) ecosystem, there are lots of ways to accomplish this, but we have not done much in helping customers build their own solutions.

Starting this year we are beginning to invest in out of the box telemetry solutions, but the first wave of these will likely be around bot performance and measurement and built with Application Insights in mind, and then move into more sophisticated hosted dashboards like you would see in dynamics or pva
https://dynamics.microsoft.com/en-us/ai/customer-insights/
https://docs.microsoft.com/en-us/power-virtual-agents/analytics-overview

Again, please feel free to reach out to me directly, would love to hear more about what you are trying to buid,
We support Ukraine and condemn war. Push Russian government to act against war. Be brave, vocal and show your support to Ukraine. Follow the latest news HERE