7 unstable releases
new 0.3.0 | Oct 25, 2024 |
---|---|
0.2.2 | Feb 18, 2023 |
0.1.1 | Oct 31, 2021 |
0.1.0 | Jun 25, 2020 |
0.0.0 | Jun 25, 2020 |
#86 in Debugging
2,937 downloads per month
Used in 4 crates
(3 directly)
18KB
282 lines
eventlog
A log-compatible wrapper around the Windows Event Log API.
Thanks to Jeroen C. van Gelderen for creating the winlog project from which this is forked.
Features
- Writes Rust log messages to the Windows event log using the RegisterEventSourceW and ReportEventW APIs.
- Provides utility functions to register/unregister your event source in the Windows registry.
- Embeds a small (120-byte) message resource library containing the necessary log message templates in your executable.
- Does not panic.
The five Rust log levels are mapped to Windows event types as follows:
Rust Log Level | Windows Event Type | Windows Event Id |
---|---|---|
Error | Error | 1 |
Warn | Warning | 2 |
Info | Informational | 3 |
Debug | Informational | 4 |
Trace | Informational | 5 |
Requirements
- Rust 1.29+ on Windows with MSVC toolchain
- [Windows, optional] mc.exe and rc.exe (only required when
eventmsgs.mc
is changed) - [Windows, optional] PowerShell (used for the end-to-end test)
Usage
Cargo.toml
[dependencies]
eventlog = "0.1.0"
Register log source with Windows
Register the log source in the Windows registry:
eventlog::register("Example Log").unwrap();
This usually requires Administrator permission so this is usually done during installation time.
If your MSI installer (or similar) registers your event sources you should not call this.
Log events
eventlog::init("Example Log", log::Level::Trace).unwrap();
info!("Hello, Event Log");
trace!("This will be logged too");
Deregister log source
Deregister the log source:
eventlog::deregister("Example Log").unwrap();
This is usually done during program uninstallation. If your MSI installer (or similar) deregisters your event sources you should not call this.
Internals
Artifacts eventmsgs.lib
and eventmsgs.rs
are under source control so users
don't need to have mc.exe
and rc.exe
installed for a standard build.
- If
build.rs
determines thateventmsgs.mc
was changed thenbuild.rs
:- invokes
mc.exe
(which createseventmsgs.h
) - invokes
rc.exe
(which createseventmsgs.lib
) - creates
eventmsgs.rs
fromeventmsgs.h
.
- invokes
build.rs
emits linker flags soeventmsgs.lib
can found.- Standard
cargo build
follows.
Testing
The end-to-end test requires 'Full Control' permissions on the
HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application
registry key.
cargo test
Process:
- Create a unique temporary event source name (
eventlog-test-###########
). - Register our compiled test executable as
EventMessageFile
for the event source in the Windows registry. You can see a new key atHKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\eventlog-test-###########
. - Write some log messages to the event source.
- Use PowerShell to retrieve the logged messages.
- Deregister our event source. This removes the
eventlog-test-###########
registry key. - Assert that the retrieved log messages are correct.
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Dependencies
~129MB
~2M SLoC