Write to Windows event log: Difference between revisions

Write script status to the Windows Event Log

<br><br>

 

=={{header|AutoHotkey}}==

h := RegisterForEvents("AutoHotkey")

SendWinLogEvent(h, "Test Message")

; Return the number of characters copied.

return char_count

 

=={{header|AWK}}==

# syntax: GAWK -f WRITE_TO_WINDOWS_EVENT_LOG.AWK

BEGIN {

}

function error(message) { printf("error: %s\n",message) ; errors++ }

{{out}}

<pre>

=={{header|Batch File}}==

The "EventCreate" command does the task.

EventCreate /t ERROR /id 123 /l SYSTEM /so "A Batch File" /d "This is found in system log."

{{Out}}

<pre>>EventLog.BAT

></pre>

If you do not want the command to display its result or errors...

EventCreate /t ERROR /id 123 /l SYSTEM /so "A Batch File" /d "This is found in system log." >NUL 2>&1

EventCreate /t WARNING /id 456 /l APPLICATION /so BlaBla /d "This is found in apps log" >NUL 2>&1

 

'''NOTE:''' This will (...or might) not work if you do not have administrator privileges.

{{works with|BBC BASIC for Windows}}

Writes to the Application Log:

PROC_cominitlcid(1033)

PROC_releaseobject(WshShell%)

 

=={{header|C}}==

The following is a wrapper on the EventCreate utility provided in Windows. Note that to use this wrapper, the code must be executed from a console/IDE running as Administrator. The utility itself does extensive error-checking and validation, so apart from the check that 5 arguments have been supplied, no other validations or checks are performed.

#include<stdlib.h>

#include<stdio.h>

return 0;

}

Invocation and output on console :

<pre>

=={{header|C sharp}}==

In Windows Vista and later or Windows Server 2003, you must have administrative privileges to execute this code.

 

namespace RC

}

}

 

=={{header|C++}}==

{{trans|C}}

#include <sstream>

 

 

return 0;

 

=={{header|Clojure}}==

 

=={{header|D}}==

{{trans|Kotlin}}

import std.stdio;

 

writeln("Failed to execute command, status=", cmd.status);

}

 

=={{header|Delphi}}==

 

{$APPTYPE CONSOLE}

begin

WriteLog('Message to log.');

 

=={{header|F_Sharp|F#}}==

<p>Bare bone writing to the Application Eventlog giving no event-ID and using the default event type (information.)</p>

log.Source <- "Sample Application"

 

=={{header|Go}}==

This works on Windows 10 with administrative privileges.

 

import (

fmt.Println(err)

}

 

=={{header|Java}}==

import java.io.IOException;

import java.io.InputStream;

}

}

 

=={{header|Julia}}==

Run as an administrator.

cmd = "eventcreate /T INFORMATION /ID 123 /D \"Rosetta Code Write to Windows event log task example\""

Base.run(`$cmd`)

 

=={{header|Kotlin}}==

The following works on Windows 10 with administrative privileges:

 

fun main(args: Array<String>) {

 

Runtime.getRuntime().exec(command)

 

=={{header|Lingo}}==

{{libheader|Shell xtra}}

props = [:]

props["operation"] = "runas"

props["parameters"] = "/t INFORMATION /id 123 /l APPLICATION /so Lingo /d "&QUOTE&"Rosetta Code Example"&QUOTE

 

=={{header|Perl}}==

The Win32::EventLog module has the Report method to write in the EventLog

 

use strict;

use warnings;

};

$handle->Report($event);

 

=={{header|Phix}}==

{{out}} (when running as administrator)

<pre>

=={{header|PicoLisp}}==

PicoLisp doesn't run on Windows. In case of Linux, the equivalent of the event log is the syslog. It can be written with '[http://software-lab.de/doc/refN.html#native native]' C functions, or simply with the 'logger' utility:

-> T

 

: (call 'logger "This" 'is "another" 'test)

 

=={{header|PowerShell}}==

$EventLog=new-object System.Diagnostics.EventLog("Application")

#Declare Event Source; must be 'registered' with Windows

 

# Write the event in the format "Event test",EventType,EventID

''Note1:'' Thanks to PoSH Fan for posting information that got me started on this at [http://winpowershell.blogspot.com/2006/07/writing-windows-events-using.html Windows PowerShell Blog]

<br>

 

===Source and event log existing===

$MessageFreeLula = 'Global unions and union leaders from more than 50 countries came together ' +

'in Geneva today to stand in solidarity with former Brazilian President Lula, calling for ' +

Write-EventLog -LogName 'System' -Source 'Eventlog' -Message $MessageFreeLula -EventId 13 -EntryType 'Information'

'SUCCESS: The Lula Livre message (#FreeLula) has been recorded in the system log event.'

{{out|output}}

<pre>

</pre>

===New event log===

$MessageFreeLula = 'Global unions and union leaders from more than 50 countries came together ' +

'in Geneva today to stand in solidarity with former Brazilian President Lula, calling for ' +

Write-EventLog -LogName 'Free Lula!' -Source '#FreeLula' -Message $MessageFreeLula -EventId 13 -EntryType 'Information'

'SUCCESS: The Lula Livre message (#FreeLula) has been recorded in the "Free Lula!" log event.'

{{out|output}}

<pre>

 

=={{header|PureBasic}}==

 

Protected wNumStrings.w, lpString=@EventMessage$, lReturnX, CMessageTyp, lparray

 

ProcedureReturn Result

 

=={{header|Python}}==

{{libheader|PyWin32}}

 

import win32con

import win32evtlog

 

win32evtlogutil.ReportEvent(applicationName, eventID, eventCategory=category,

 

=={{header|Racket}}==

Racket's logging facility creates windows events when running on Windows.

 

#lang racket

(log-warning "Warning: nothing went wrong.")

 

=={{header|Raku}}==

(Same caveats as the others, needs to be run as administrator or with elevated privileges under Windows.)

 

when .is-win {

my $cmd = "eventcreate /T INFORMATION /ID 123 /D \"Bla de bla bla bla\"";

$logger.info("[$*PROGRAM-NAME pid=$*PID user=$*USER] Just thought you might like to know.");

}

 

=={{header|REXX}}==

 

===annotated===

 

eCMD = 'EVENTCREATE' /*name of the command that'll be used. */

eCMD '/T' type "/ID" id '/L' logName "/SO" source '/D' desc

 

{{out|output}}

<pre>

 

===bare bones===

/* [↓] cmd options have extra spacing.*/

 

'/D "attempting to add an entry for a Rosetta Code demonstration."'

 

{{out|output|text=&nbsp; is identical to the 1^st REXX version.}} <br><br>

 

=={{header|Ruby}}==

{{libheader|win32-utils}}

logger = Win32::EventLog.new

 

Instructions on setting up an Event Source is [http://rubyforge.org/docman/view.php/85/1734/mc_tutorial.html here]

 

=={{header|Rust}}==

#[cfg(windows)]

mod bindings {

println!("Not implemented");

}

add this to the build.rs:

fn main() {

#[cfg(windows)]

}

}

And this to cargo.toml:

[target.'cfg(windows)'.dependencies]

windows = "0.7.0"

[target.'cfg(windows)'.build-dependencies]

windows = "0.7.0"

 

=={{header|Scala}}==

The following works on Windows 10 with elevated (administrative) permission:

 

import sys.process._

println(s"\nSuccessfully completed without errors. [total ${scala.compat.Platform.currentTime - executionStart} ms]")

 

 

=={{header|Standard ML}}==

From bsd/linux/unix to log

OS.Process.system "logger \"Log event\" " ;

From MS Windows to MS Windows, taken from C:

OS.Process.system "EventCreate /t WARNING /id 458 /l APPLICATION /so SomeSource /d \"Settastring\"" ;

 

=={{header|Tcl}}==

{{libheader|TWAPI}}

 

# This command handles everything; use “-type error” to write an error message

 

=={{header|VBScript}}==

Sub write_event(event_type,msg)

Set objShell = CreateObject("WScript.Shell")

 

Call write_event("INFORMATION","This is a test information.")

 

=={{header|Wren}}==

{{trans|Go}}

This embedded program is untested as I no longer have a working Windows machine but should work when run with administrative privileges - what can possibly go wrong?

 

class Windows {

].join(" ")

 

<br>

Now embed this script in the following C program, compile and run it.

#include <stdlib.h>

#include <string.h>

WrenVM* vm = wrenNewVM(&config);

const char* module = "main";

char *script = readFile(fileName);

WrenInterpretResult result = wrenInterpret(vm, module, script);

free(script);

return 0;

 

=={{header|zkl}}==

{{trans|Clojure}}

{{out}}

<pre>

0

</pre>

{{omit from|Lotus 123 Macro Scripting|Would overwrite the log file}}

{{omit from|Mathematica}}

{{omit from|Maxima}}

{{omit from|PARI/GP}}

{{omit from|PostScript}}

{{omit from|Retro|No access to Windows APIs}}

{{omit from|TI-83 BASIC|Cannot run on Windows}}

{{omit from|zkl}}

{{omit from|ZX Spectrum Basic|Microdrive access is slow, and there is no real time clock, so event logging is not usually done}}