+1 888 340 6572
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Closed Feature request MC-754

Logs : save the logs automatically for at least 24 hours instead of erasing the logs when MC is relaunched

Go to the next issue (open or closed)
Go to the next open issue
icon_info.png This issue has been closed with status "Released" and resolution "Not determined".

It seems that the MC logs are automatically erased when MC is launched. As a result, when there is a crash, either the customer relaunches MC and then calls customer service who says "the logs are erased by your relaunch, it may be difficult to identify the cause" or the customer has to spend time in "run" saving the logs, then in "task manager" stopping all MC processes before relaunching MC.
For a trader, the priority is to have MC up and running, not to waste time with MC closed saving logs in the middle of a trading session.
If the logs were automatically saved for at least 24 hours, the customer would not need to waste time during active trading sessions saving the logs before relaunching MC. In addition, customer service could access the logs when it is open and customers could save and send their logs after their trading session is closed.
This issue is particularly important for customers who live in non-US time zones and trade in local markets which are open during times when when customer service is closed. For these customers, saved logs are the main way to fix issues happening during times when customer service is closed.

Steps to reproduce this issue

Not applicable.

Comments (1)
user-offline.png  MultiCharts Support (MultiCharts)
Apr 07, 2017 - 08:13
  1. Not all the Log files are erased now when MC is restarted.
  2. Feedback application can be used to send the Log files, screenshots, etc. outside Support working hours.
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    MultiCharts 10.0 (RELEASED)
  • Status
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates