Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Image Added

Get Event Log Entries

This activity gets a collection of Event Log Entries based on the parameters specified.

...

The Get Event Log Entries activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

  • Computer IP Address (text box editor type) (type: string): the computer ip IP address or computer name where you want to log the message. Not required when used locally.
  • Date Start (calendar control) (type: string): the starting date of the entries you want to retrieve. Date should be in the following format: 'dd/MM/yyyy HH:mm:ss', for example "17/05/2016 07:00:00", which will search for all event logs starting May 17, 2016, 07:00 AM.
  • Event Log Entry Type level (combo box control) (type: string): the Event Log Entry Type Level of the log which will be createdretrieved. By default, Flowster Studio provides Critical, Error, Info, Warning and Verbose as options.
  • Event Log Name (combo box control) (type: string): the port of the Citrix Host - example: '80'the Event Log Name of the log which will be retrieved. By default, Flowster Studio provides Application, System, Security, Setup and ForwardedEvents as options.
    NOTE: this field is also editable. By double clicking the field, it can be inserted the desired Event Log Name. For example, Windows PowerShell, as seen in Event Viewer:

    Image Added

  • Full Username (text box editor type) (type: string): the domain and username which will be used when accessing event logs from a remote computer (e.g. "fmrp\demouser").
  • Password (text box editor type) (type: string): the password for the remote computer username.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted value for the remote computer username.
  • Source (text box editor type) (type: string): the source name or leave blank if you want to retrieve all.

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Get Event Log Entries activity:

...

  • The source name should be entered with the exact name as in Event Viewer, for example "PowerShell".
    NOTE: the Source Name is not necessarily the one seen in  the event logs table (Source/Quelle). This name should be taken from Event Viewer by following the next steps:
    • select an event log
    • go to Details
    • expand System
    • select the value from Provider - Name:

      Image Added


The Read Only Output variable are the possible output values that the activity will provide:

  • Entries Collection (type: collection<collection<string>>): outputs a collection containing Event Log entries.


Execution: the activity will retrieve event logs based on the given input. The output will be a collection of event logs and their attributes:

Image Added



 

Send Event Log Message

This activity creates an entry in the Windows Event Log within the selected folder.

...