BES Logs ... What's in them? Part 8 of 20 (MDAT log)
Posted 07-01-2009 at 05:00 AM by hdawg
Tags bes log, bes mds cs, bes mds-ce, blackberry logs, blackberry mdat log, blackberry mds, blackberry mds cs, blackberry mds-cs, blackberry server logs, mdat log, mds cs, mds-cs, mobile data service
Welcome to Part 8 of the 20 part series looking at the BES logs. (Part 7).
We've hit the #1 log I don't even bother opening ... the Mobile Data Service (MDAT) log. I don't bother opening the log file (unless I'm really deep into troubleshooting some random HTTP/HTTPS thing ... which to be honest, I can't remember doing more than once) because its a beast to read through. I always use the BlackBerry Resource Kit (BRK) tool MDSPushvsPull.exe to process this file, and so should you.
Most importantly, this tool gives you easy to read output for when someone says: Hey, can we find out what websites people are going to on their BlackBerry? ... instead of grunting or shrugging your shoulders, you can say yes ... and have that data within minutes!
In case you don't believe me, below are two cuts from log files. The first is from an MDAT log and the second is from the output from the tool MDSPushvsPull.exe:
Type Source Destination Date Time Port Size
Pull XXXXXXXX m.nhl.com 6/1/2009 10:08:08.546 EDT 80 975
You can see the correlation between the log and the MDSPushvsPull.exe output ... here's the command to get that output:
C:\temp\logs>MDSPushvsPull.exe -p E
Checking for log files...
Starting processing of MDS logs...
Progress: |----10----20----30----40----50----60----70----80----90----100|
Starting generation of output...
MDSPushvsPull::GenerateOutput - Creating file .\MDSPushvsPull_0601.0.csv
Processing completed, Process time=1 second(s), Total time=1 seconds(s), Total events=41.
The MDAT log file had 61,125 lines of log in it and the output CSV file was 2,511 lines ... all csv formatted to be viewed easily with Excel. (The -p E above references the platform of the log file ... Exchange)
Each line in the output begins with Pull or Push, indicating what type of transaction it was ... we can see from the line above that it was a HTTP pull request on port 80 to m.nhl.com from PIN XXXXXXXX at 10:08 AM on June 1st ... does it get any sweeter than that?
Well folks, that is about it. I tried to find an MDAT log with a whole slew of errors, but its easier said than done. If you've got a log full of errors and want to send it over I'd be more than glad to look through it and put together something I can post.
If you've got any questions about other specific entries in the MDAT log feel free to post a question / comment in response to this post, or in the forum.
Tomorrow in Part 9 we'll dive into another log I'm sure most always never gets looked at ... the BlackBerry Manager (MNGR) log.
We've hit the #1 log I don't even bother opening ... the Mobile Data Service (MDAT) log. I don't bother opening the log file (unless I'm really deep into troubleshooting some random HTTP/HTTPS thing ... which to be honest, I can't remember doing more than once) because its a beast to read through. I always use the BlackBerry Resource Kit (BRK) tool MDSPushvsPull.exe to process this file, and so should you.
Most importantly, this tool gives you easy to read output for when someone says: Hey, can we find out what websites people are going to on their BlackBerry? ... instead of grunting or shrugging your shoulders, you can say yes ... and have that data within minutes!
In case you don't believe me, below are two cuts from log files. The first is from an MDAT log and the second is from the output from the tool MDSPushvsPull.exe:
Type Source Destination Date Time Port Size
Pull XXXXXXXX m.nhl.com 6/1/2009 10:08:08.546 EDT 80 975
You can see the correlation between the log and the MDSPushvsPull.exe output ... here's the command to get that output:
C:\temp\logs>MDSPushvsPull.exe -p E
Checking for log files...
Starting processing of MDS logs...
Progress: |----10----20----30----40----50----60----70----80----90----100|
Starting generation of output...
MDSPushvsPull::GenerateOutput - Creating file .\MDSPushvsPull_0601.0.csv
Processing completed, Process time=1 second(s), Total time=1 seconds(s), Total events=41.
The MDAT log file had 61,125 lines of log in it and the output CSV file was 2,511 lines ... all csv formatted to be viewed easily with Excel. (The -p E above references the platform of the log file ... Exchange)
Each line in the output begins with Pull or Push, indicating what type of transaction it was ... we can see from the line above that it was a HTTP pull request on port 80 to m.nhl.com from PIN XXXXXXXX at 10:08 AM on June 1st ... does it get any sweeter than that?
Well folks, that is about it. I tried to find an MDAT log with a whole slew of errors, but its easier said than done. If you've got a log full of errors and want to send it over I'd be more than glad to look through it and put together something I can post.
If you've got any questions about other specific entries in the MDAT log feel free to post a question / comment in response to this post, or in the forum.
Tomorrow in Part 9 we'll dive into another log I'm sure most always never gets looked at ... the BlackBerry Manager (MNGR) log.
Total Comments 1
Comments
-
when you have the mdat setting:
file logging destination: log level Informational,
mdspushvspull reports : No push/pull events detected.
with log level : Debug, the tool writes a correct .csv filePosted 11-15-2010 at 11:52 AM by dieter_m
