Problem

In high volume environments, transactions roll out of Traffic Monitor more quickly than desired.

Resolution

By design, Traffic Monitor removes older transactions and limits the total size of the data retained. One option is to increase these limits via the Traffic Monitor settings, though this can only be used to make small increases before performance becomes a concern. This should not be increased by more than a small multiple of its default size. So if you can only retain an hour of traffic, you probably won't be able to hold more than a few hours of traffic before volume becomes an issue.

Another option is the Axway Community project that integrates ElastiSearch into Traffic Monitor, though this is a significant customization project, it allows you to use Traffic Monitor on significantly larger amounts of data.

Finally, it is also possible to enable Open Logging and feed that information to an outside log processing program to get similar information outside of Traffic Monitor. Note that instances with Open Logging enabled will need more resources to process all of that data.