Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, May 23, 2013 9:12 PM
For some reason I don't know, I have these files being created in C:\ProgramData\Windows Fabric\Fabric\log\Traces called fabric_traces...etl. I have no idea what they are and how to shut them off. They appear to be log files. Each file is about 132MB and the files accumulate very quickly.
Anyone know how to shut these off?
All replies (7)
Thursday, May 23, 2013 10:18 PM ✅Answered | 1 vote
It could be a tracelog output file, try from a command window:
tracelog -stop debugtrace
Regards John Timney http://www.johntimney.com
Friday, May 24, 2013 4:57 AM ✅Answered | 1 vote
ETL -> Event trace log
Fabric traces store all the event trace logs in this file ( you might want to verify)
Mark this post as answer if this resolves your issue. Everything about SQL Server | Experience inside SQL Server -Mohammad Nizamuddin
Friday, May 24, 2013 1:13 PM
Very interesting. I went looking for that command yesterday on my system and couldn't find it. So I thought, it must not apply or it was a powershell command I was unfamiliar with.
I did another search today, and did not find tracelog.exe but I did find tracelogSM.exe but it was tied to System Center Operations Manager (aka SCOM or SCCM).
It seems that you can turn off the trace for the AppFabric using this command instead of tracelog.exe. What I am still not sure about is why I started getting the logging in the first place.
Thanks very much for your help.
Wednesday, December 4, 2013 10:06 PM
Very interesting. I went looking for that command yesterday on my system and couldn't find it. So I thought, it must not apply or it was a powershell command I was unfamiliar with.
I did another search today, and did not find tracelog.exe but I did find tracelogSM.exe but it was tied to System Center Operations Manager (aka SCOM or SCCM).
It seems that you can turn off the trace for the AppFabric using this command instead of tracelog.exe. What I am still not sure about is why I started getting the logging in the first place.
Thanks very much for your help.
Just had the same prob today. both fabric collector traces under data collector sets were running and I'm not sure why they were started in the first place. tracelog.exe grabbed 25%CPU and 4GB of ram which was noticeable. Please share if you find out why it was started. I'm curious.
Wednesday, January 8, 2014 2:59 PM | 2 votes
Hi,
Just to add some info to this thread, those traces are configured by default as data collector sets.
There are also some bat files that can be used to start/stop/collect the .etl into .trace files.
http://mariusene.wordpress.com/
Wednesday, January 8, 2014 3:12 PM | 1 vote
Also make sure they are configured as below so you don't have .etl files eating up all the free space.
http://mariusene.wordpress.com/
Tuesday, December 20, 2016 6:51 AM
Tracing has been started on the machine but never stopped back. To see which traces you have running, start CMD>logman
This will show started traces on the computer. To stop the trace just type in the same CMD "logman stop <RunningTraceName>"