TraceLogging events and tracing
Перейти к файлу
Doug Cook (WINDOWS) 52731c36b1 Python - use inline SHA1 implementation
TraceLoggingDynamic uses SHA1 hashing for non-security purposes.

To avoid potential problems on systems where SHA1 libraries are disabled
for security reasons, use a a local implementation of SHA1. This is
probably much slower than the library version, but it's not used in any
performance-critical code paths.

Also update some type annotations since I was getting warnings that the
`*` syntax is not supported. Seems like `Array` is as specific as you
can get with the annotations.
2024-08-15 17:15:00 -07:00
.github Add action for codeql and test (#66) 2024-06-05 16:01:25 -07:00
LTTng Add action for codeql and test (#66) 2024-06-05 16:01:25 -07:00
etw Python - use inline SHA1 implementation 2024-08-15 17:15:00 -07:00
.gitignore rust tracelogging_dynamic - make register non-mut (#54) 2023-03-24 19:00:21 -07:00
.gitmodules Switch LTTng tests to CTest (#65) 2024-06-03 20:06:11 -07:00
CONTRIBUTING.md Clean up docs (#33) 2022-04-22 11:43:36 -07:00
LICENSE Clean up additional OSS required work from checklist (#7) 2019-05-24 14:39:54 -07:00
README.md Add TraceLoggingDynamic.h (#29) 2022-04-13 17:06:12 -07:00
SECURITY.md Microsoft mandatory file (#45) 2022-08-19 12:36:40 -07:00

README.md

Build Status

TraceLogging

TraceLogging is a set of technologies for emitting structured events. It is primarily used with Event Tracing for Windows (ETW). Some parts of TraceLogging are also available on other operating systems.

TraceLogging for ETW (Windows)

TraceLogging for ETW provides helpers for using TraceLogging with Event Tracing for Windows (ETW).

TraceLogging for LTTng (Linux)

TraceLogging for LTTng provides an LTTng Helpers library and a TraceLoggingProvider.h header. This allows C/C++ developers to use the same TraceLoggingProvider syntax to generate events for both ETW and LTTng.

Reporting Security Issues

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at <secure@microsoft.com>. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct.

For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Contributing

Want to contribute? The team encourages community feedback and contributions. Please follow our contributing guidelines.

We also welcome issues submitted on GitHub.

Project Status

This project is currently in active development.

Contact

The easiest way to contact us is via the Issues page.