My Oracle Support Banner

How to Parse IMAP Telemetry Log Files? (Doc ID 1573415.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Communications Messaging Server - Version 5.2.0 and later
Information in this document applies to any platform.

Goal

Occasionally you need to enable IMAP telemetry to try to capture information about a problem for a specific user, but you do not know exactly when the problem will happen, or exactly what IMAP commands are involved.

Enabling IMAP telemetry for the user is easy. Leaving it run that way can accumulate a lot of data. Be careful not to let it fill the file system where telemetry is stored.

The telemetry feature captures all the data received from and sent to the client. There is a separate file for each session. The file name is the Unix date/time when the session started. If multiple sessions start in the same second, a .n is appended to the file name to keep them unique.

But once you have all that data, if you do not know exactly when the problem happened or what IMAP command is involved, how do you sort through all that data?
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 If you know when the problem happened
 If you know what IMAP command was involved
 Otherwise, you need a way to get an overview
 Find large time gaps
 Next comes the more tedious work
 Find the lines in those files where response time was bad
 A generalized example of some IMAP telemetry
 How to get a more general idea of what is going on?
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.