Content
- MarketFactory guarantees that every API client or Venue message sent or received is logged.
- Additional logging is also in place to be able to trace internal message flows, state changes etc.
Rolling Frequency
Logs are rolled on a schedule appropriate to the Venue, connection type and customer usage. This may be driven by log file size, or clock time (for example, either hourly or daily).
Retention
The MarketFactory log file retention policy is as follows:
- 0-7 days - logs available on the server itself
- 0-1 year - logs stored on a network-attached storage file system
- 1-7 years - logs stored at archival storage site
Overview
Content Tools
3 Comments
Unknown User (jkasakya)
Oct 16, 2017Question
(Question - are they also copied to gluster?)
Yes...logs stored on the host itself are periodically evicted to gluster
Matthew Whitaker
Oct 19, 2017What does 'periodically' mean?
Unknown User (jkasakya)
Oct 19, 2017What I mean by periodically is that logs are evicted to gluster on what appears to be a rolling basis, waiting random time periods before beginning the process of ejecting the logs (the benefit of this being that it prevents high demand on the gluster array with multiple hosts all attempting at the same time). This is documented in the eviction script on every PROD host at /app/sre/bin//app/sre/bin/mf-log-management.
With every 1 log file created for FeedID=X (through log rollover), the oldest 1 logfile on the host for FeedID=X would then be identified for eviction.
Hopefully, this makes sense?