log output messages (Experiment feedback)

Everything OAD-related that won't fit in the other categories: share general aspects of macro programming and discuss the OAD environment
Post Reply
Julien Toquant
Posts: 23
Joined: Fri May 29, 2020 1:54 pm

log output messages (Experiment feedback)

Post by Julien Toquant »

Hi,
Is there a way to get the content of the "output messages" window (experiment feedback interface) into a log file?
Thanks,
Julien
Marion Lang
Posts: 1
Joined: Mon May 18, 2020 8:57 am

Re: log output messages (Experiment feedback)

Post by Marion Lang »

Dear Julian,

at the moment there is no possibility to get the content of the "output messages" window written into a logfile.
A workaround could be to create your own logfile for debugging via

Code: Select all

ZenService.Xtra.System.WriteDebugOutput(string message)

Kind regards,
Marion
cfdgr dfhdrg
Posts: 1
Joined: Fri Aug 04, 2023 11:19 am

Re: log output messages (Experiment feedback)

Post by cfdgr dfhdrg »

Hello Julien,

Absolutely, there are ways to capture the content of the "output messages" window and save it into a log file without needing to write code:

Manual Copy-Paste: You can manually select the content in the "output messages" window, copy it (Ctrl+C or right-click and select Copy), open a text editor (like Notepad), create a new file, and paste the content (Ctrl+V or right-click and select Paste). Save the file with a .txt extension to create a log of the messages.

Screenshot: You can take a screenshot of the "output messages" window by pressing the Print Screen (PrtScn) button on your keyboard or using a screenshot tool. Then, open an image editor or word processor, paste the screenshot, and save it. This method doesn't capture the actual text, but it visually records the messages.

Print to PDF: If your operating system allows, you can "print" the contents of the window to a PDF file. Open the "output messages" window, go to the Print option (usually Ctrl+P or File > Print), and select a PDF printer from the available options. This will create a PDF file containing the messages. residential garage door service

Remember that these methods don't provide automation like scripting would, but they offer simple ways to capture and store the content from the "output messages" window in a log-like format.
lisa purnell
Posts: 1
Joined: Fri Sep 15, 2023 5:39 am

Re: log output messages (Experiment feedback)

Post by lisa purnell »

Marion Lang wrote: Mon Jul 13, 2020 10:12 am Dear Julian,

at the moment there is no possibility to get the content of the "output messages" window written into a logfile.
A workaround could be to create your own logfile for debugging via

Code: Select all

ZenService.Xtra.System.WriteDebugOutput(string message)

Kind regards,
Marion
Configure Mattermost to output logs to the console. true: (Default) Output log messages are written to the console based on the console log level configuration. Taylor Swift 2048
CarX Street
Posts: 1
Joined: Wed Nov 01, 2023 9:16 am
Contact:

Re: log output messages (Experiment feedback)

Post by CarX Street »

The content of the "output messages" window in the experiment feedback interface can be logged to a file by following these steps:

Open the experiment feedback interface.
Click the "Log Output Messages" button.
Select the location where you want to save the log file.
Click the "Save" button.
The log file will be saved in a plain text format and will contain all of the output messages that have been generated since the experiment started. https://carxstreat.com/

Here is an example of how to log output messages to a file using Python:

Code: Select all

Python
import subprocess

def log_output_messages(filename):
  """Logs the output messages from the experiment feedback interface to a file.

  Args:
    filename: The path to the file where the output messages should be logged.
  """

  with open(filename, "a") as f:
    subprocess.run(["experiment-feedback", "log-output-messages"], stdout=f)
# Log the output messages to a file named "output.log".
log_output_messages("output.log")
Use code with caution. Learn more
You can also use a tool like logrotate to automatically rotate and compress the log file. For example, you could create a logrotate configuration file like this:

Code: Select all

/var/log/experiment-feedback.log {
  rotate 7
  daily
  compress
  missingok
  postrotate
    /etc/init.d/experiment-feedback restart
  endscript
}
This configuration will rotate the log file every 7 days, compress the old log files, and restart the experiment feedback service after each rotation.

I hope this helps!
MATTHEW willson
Posts: 1
Joined: Fri Nov 03, 2023 2:04 pm

Re: log output messages (Experiment feedback)

Post by MATTHEW willson »

Having utilized <a href=https://smamepestimate.com/hvac-estimating-services/>HVAC Estimating Services</a> for our recent project, I am thrilled to share my positive experience. Their team demonstrated exceptional expertise, delivering accurate estimates promptly. The detailed insights provided not only ensured precise budgeting but also streamlined our project planning process. The transparency and professionalism exhibited by HVAC Estimating Services exceeded our expectations, making them our go-to choice for future projects. I highly recommend their services to fellow industry professionals seeking reliable HVAC estimation solutions. Their commitment to quality and efficiency significantly contributed to our project's success.
Nelly Aurora
Posts: 2
Joined: Wed Aug 23, 2023 11:05 am

Re: log output messages (Experiment feedback)

Post by Nelly Aurora »

I thought there is no way to obtain the information displayed in the "output messages" window and save it to a log file. Thank you all for sharing. It’s great that the problem is finally fixed.
Post Reply