Click here to Skip to main content
15,884,628 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
We are logging custom events from application to ETW. Now need to find the best compression technique as lots of data will be written to the file and the etl file is to be send with error report to the server.

How to specify the details? In System.Diagnostics.Tracing.EventSource itself, when setting it up?

What I have tried:

Not seeing what is the option/setting to specify compression details. So waiting for some guidance
Posted
Updated 5-Nov-18 1:05am
Comments
Patrice T 5-Nov-18 2:40am    
Why don't you ask the people making that software ?
We are not their support service.
johannesnestler 5-Nov-18 7:08am    
You mean Microsoft? Seems you don't know ETW - have a look https://docs.microsoft.com/en-us/windows/desktop/etw/event-tracing-portal

1 solution

Depend's how you use it, but Maybe this helps: ETW Trace Compression (and xperf syntax refresher) | Random ASCII[^]
 
Share this answer
 
Comments
nairnishitha 5-Nov-18 23:57pm    
Thanks @johannesnestler. But I am not allowed to use any third party tool. And the purpose is the messages written from our application, creates a new session and when a crash occurs, the reporting tool of ours acts to end current session, which writes the logs from memory to file. Instead of later compressing the file data, (before sending it to customer support), checking if any option to compress before the data goes to the file.
johannesnestler 6-Nov-18 7:00am    
xperf is part of the Windows SDK - so not really 3rd Party. if you have both sides in your Hands you can do the compression/decompression manually - but I think this is what you want to avoid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900