Skip to main content
Support Center
Help ArticlesAcademyCommunity
HomeCommunitySDK/APIData connectorExtracting DebugData (debug records) via the MyGeotab MCP Connector

Extracting DebugData (debug records) via the MyGeotab MCP Connector

Open
SDK/API
Data connector
A
A
AtaydeMM-8256
Original Poster

Hi everyone,
I am currently evaluating advanced device troubleshooting capabilities and would like to know if it is possible to query or stream DebugData (debug records) directly through the MyGeotab MCP Connector.

While we can successfully stream standard telematics data (such as LogRecords, StatusData, etc.) using the MCP Connector, I haven't found specific documentation regarding the synchronization of the DebugData API object.

For instance, we are interested in evaluating various debug record types to monitor device health, such as:

  • ModemConnectionSuccess
  • GprsModemPowerOff
  • DebugErrorRestartModemManager (these are just a few examples of the debug logs we would like to analyze)


Has anyone successfully pulled the DebugData object through the MCP Connector, or is it currently limited to standard API calls? If it's not supported yet, is there any roadmap to include it?

3 Replies
Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

3 Replies

E
E
EishiFUN
Community Administrator

Hey @AtaydeMM-8256 ,

Thank you for asking your question in our community. I apologize for the delay in responding to you on this post. This is a really interesting use case and I want to make sure the right people get into this conversation. I have brought this up to our team that works on the MCP. I will either have them come in here or relay what they tell me after they have some time to review and look into this a little.

I appreciate your patience and encourage you to reach out if you have any other questions in the meantime. We are always happy to help.

Have a great day!
Eishi FUN

F
F
Felipe_Hoffa
Geotabber

I tried this against one of our internal databases, and I was able to retrieve DebugData through the MCP connector, including examples of:

  • ModemConnectionSuccess
  • GprsModemPowerOff
  • DebugErrorRestartModemManager

The records also include the raw binary data payload, along with the device and timestamp.
So the basic retrieval part appears to work.
Can you clarify what you are looking to do beyond retrieving the records? For example, are you trying to decode the binary payload for those specific debug reasons, interpret the sequence of events for device-health monitoring, or continuously synchronize the records?
That distinction will help us understand whether the current MCP support already covers your use case or whether there is an additional gap.

A
A
AtaydeMM-8256
Original Poster

Hi Eishi and Felipe, thank you both for your responses and for looking into this.

@Felipe_Hoffa, to answer your question: we are looking to interpret the sequence of events for device cellular connectivity health monitoring, specifically to calculate accurate uptime and availability metrics.

To give you a bit more background on our current process, we have been using a report template from the "Log Data and Collisions" module, and recently implemented a script that queries debugData via the MyGeotab API.

I appreciate any insights you and the MCP team can share on this!

Still have questions?
Learn with AcademyBrowse documents