Thanks for the follow-up there. The scenario I'm talking about is for browser-based applications, and my assumption as of right now is that I should just fit logging related to Web Messenger into my applications' overall logging strategy/frameworks. I assume I'll just put my logging statements (again, configured in my applications that use Web Messenger) in the event hooks and callback functions provided by the JavaScript SDK. Then I'll likely correlate those logs for my monitoring/observability.
If that sounds like the generally correct pattern, I feel pretty good about doing that.
------------------------------
Blair Billings
Software Engineer
------------------------------
Original Message:
Sent: 01-30-2026 04:40
From: Ralph John Quiaoit
Subject: Monitoring & Observability - Messenger
Hi Blair!
You can read our blog here that discusses Genesys Cloud SDK Configuration and Logging. Do take note that browser-based applications must specify configuration settings programmatically for logging.
Hope this helps.
Genesys Cloud SDK Configuration and Logging
------------------------------
Ralph John Quiaoit
Software Engineer (Developer Evangelist)
ralph_john.quiaoit@genesys.com
Original Message:
Sent: 01-29-2026 08:26
From: Blair Billings
Subject: Monitoring & Observability - Messenger
Hello all -
I'm curious to hear how others are generally handling their Monitoring/Observability for Web Messenger/Mobile Messenger across their experiences. I'm talking more specifically about monitoring and observability for the customers using your experiences powered by the Genesys Cloud Messaging framework. Genesys clearly allows for great integrations with their JavaScript SDK - but things become open to interpretation for how to observe/monitor beyond just utilizing their Commands and Events.
I'm looking for how you generally use SDK Command/Events (and their callback functions) to integrate into logging/monitoring frameworks, and if I'm missing anything about platform-native Genesys Cloud features to enable monitoring/observability. For example:
I can listen for:
Genesys("subscribe", "MessagingService.started", function({data}){ console.log(data)});
but logging to the browser console isn't very helpful for overall observability. I know Genesys enables me to do whatever I want inside the callback function, so I'm wondering if people are just generally plugging into their logging frameworks within these functions, and taking observability/monitoring from there? Is there anything Genesys-Cloud-native I'm missing here from a monitoring/observability perspective? Thanks in advance!
#Integrations
#MobileMessenger
#WebMessaging
------------------------------
Blair Billings
Software Engineer
------------------------------