Start-SbecSimpleLogSession

by Posted on

Start-SbecSimpleLogSession is accessible with the help of BootEventCollector module. To configure BootEventCollector, go through this link.

Synopsis

Starts a log session with the forwarding of events to the Collector.

Description

The Start-SbecSimpleLogSession cmdlet starts a log session in boot event mode with a simpler subset of parameters.

To start a log session with more parameters, use Start-SbecLogSession.

Parameters

-BufferSize

Specifies the buffer size for the session, in kilobytes. This is the size of one buffer, with the count of these buffers set by the MinimumBufferCount and MaximumBufferCount parameters.
Type:UInt32
Position:6
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-ClockType

Specifies the type of clock used for the events collected by this session: The acceptable values for this parameter are:
  • Default.
  • QueryPerformanceCounter. The high-resolution (period of 100 nanoseconds) clock that is typically used for performance measurement.
  • SystemTime. The lower-resolution system time similar to FILETIME (period of 10 milliseconds). This value is most typical for the data collection through SBEC.
  • CpuCycleCounter. The highest-resolution, with the frequency of the CPU, but may be unreliable depending on the CPU model and the thermal and power modes.
Type:ClientContext
Accepted values:Default, QueryPerformanceCounter, SystemTime, CpuCycleCounter
Position:5
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-FlushSeconds

Specifies the timeout, in seconds, for the session buffers to automatically flush. You can disable the flushing of buffers on timeout by setting this parameter to 0, then the buffers will be written only when full or on an explicit flush.
Type:UInt32
Aliases:FlushTimer
Position:9
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-KernelEnableFlags

Specifies flags for the NT Kernel Logger that enable the kernel events. For the setup and boot monitoring, the only reasonable flag is Process. This enumeration type is defined in $PsHome\Modules\BootEventCollector\SbecTraceHelpers.psm1. The acceptable values for this parameter are:
  • None
  • Process
  • Thread
  • ImageLoad
  • ProcessCounters
  • ContextSwitch
  • Dpc
  • Interrupt
  • SystemCall
  • DiskIO
  • DiskFileIO
  • DiskIOInit
  • Dispatcher
  • MemoryPageFaults
  • MemoryHardFaults
  • VirtualAlloc
  • NetworkTCPIP
  • Registry
  • Alpc
  • SplitIO
  • Driver
  • FileIO
  • FileIOInit
  • Profile
Type:EventTraceFlag
Accepted values:None, Process, Thread, ImageLoad, ProcessCounters, ContextSwitch, Dpc, Interrupt, SystemCall, DiskIO, DiskFileIO, DiskIOInit, Dispatcher, MemoryPageFaults, MemoryHardFaults, VirtualAlloc, NetworkTCPIP, Registry, Alpc, SplitIO, Driver, FileIO, FileIOInit, Profile
Position:11
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Level

Specifies the highest detail level value to enable for providers. This enumeration type is defined in $PsHome\Modules\BootEventCollector\SbecTraceHelpers.psm1. The acceptable values for this parameter are:
  • Undefined
  • Fatal
  • Error
  • Warning
  • Information
  • Verbose
  • All
Type:SeverityLevel
Accepted values:Undefined, Fatal, Error, Warning, Information, Verbose, All
Position:4
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-LogFileMode

Specifies the new flags for the log file mode. The EnableKd and DisableKd values parameters are applied on top of these flags. This enumeration type is defined in $PsHome\Modules\BootEventCollector\SbecTraceHelpers.psm1. The cmdlet automatically adds the RealTime and KdFilter values to this parameter. Other frequently used flags for this context are:
  • Secure. Restricts who can log events to the session to those with TRACELOG_LOG_EVENT permission.
  • UsePagedMemory. Use the paged memory for the buffers.
  • NoPerProcessorBuffering. Write the events from all processors to the same buffer. This preserves the order of the events, and is recommended for sending the events to the event collector.

The acceptable values for this parameter are:
  • None
  • FileNone
  • FileSequential
  • FileCircular
  • FileAppend
  • FileNewFile
  • Reserved0x00000010
  • FilePreallocate
  • Nonstoppable
  • Secure
  • RealTime
  • DelayOpenFile
  • Buffering
  • PrivateLogger
  • AddHeader
  • UseKilobytesForSize
  • UseGlobalSequence
  • Relog
  • PrivateInProc
  • BufferInterface
  • KdFilter
  • RealtimeRelog
  • LostEventsDebug
  • StopOnHybridShutdown
  • PersistOnHybridShutdown
  • UsePagedMemory
  • SystemLogger
  • Compressed
  • IndependentSession
  • NoPerProcessorBuffering
  • Blocking
  • Reserved0x40000000
  • AddToTriageDump
  • Fatal
  • Error
  • Warning
  • Information
  • Verbose
  • All
Type:LoggingMode
Accepted values:None, FileNone, FileSequential, FileCircular, FileAppend, FileNewFile, Reserved0x00000010, FilePreallocate, Nonstoppable, Secure, RealTime, DelayOpenFile, Buffering, PrivateLogger, AddHeader, UseKilobytesForSize, UseGlobalSequence, UseLocalSequence, Relog, PrivateInProc, BufferInterface, KdFilter, RealtimeRelog, LostEventsDebug, StopOnHybridShutdown, PersistOnHybridShutdown, UsePagedMemory, SystemLogger, Compressed, IndependentSession, NoPerProcessorBuffering, Blocking, Reserved0x40000000, AddToTriageDump
Position:10
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-MaximumBufferCount

Specifies the maximum number of buffers to allocate for this session.
Type:UInt32
Aliases:MaximumBuffers, maxbuf
Position:8
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-MinimumBufferCount

Specifies the minimum number of buffers to allocate for this session.
Type:UInt32
Aliases:MinimumBuffers, minbuf
Position:7
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Name

Specifies the name of the session to create.
Type:String
Position:0
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-PassThru

Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.
Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-ProviderGuid

Specifies the provider GUIDs to subscribe this session to. The providers are configured to include all events up to the level specified by the Level parameter.
Type:Guid[]
Aliases:pg
Position:3
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-ProviderName

Specifies the provider names to subscribe this session to. The providers are configured to include all events up to the level specified by the Level parameter.
Type:String[]
Aliases:pn
Position:2
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-SessionGuid

Specifies the GUID for the session. By default the GUID gets generated and assigned automatically.
Type:Guid
Position:1
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Syntax

Start-SbecSimpleLogSession [-Name] <String> [[-SessionGuid] <Guid>] [[-ProviderName] <String[]>] [[-ProviderGuid] <Guid[]>] [[-Level] <SeverityLevel>] [[-ClockType] <ClientContext>] [[-BufferSize] <UInt32>] [[-MinimumBufferCount] <UInt32>] [[-MaximumBufferCount] <UInt32>] [[-FlushSeconds] <UInt32>] [[-LogFileMode] <LoggingMode>] [[-KernelEnableFlags] <EventTraceFlag>] [-PassThru] [<CommonParameters>]

You can check the Version, CommandType and Source of this cmdlet by giving below command.

Get-Command Start-SbecSimpleLogSession
Get-Command Start-SbecSimpleLogSession powershell script command cmdlet

You can also read about
  • Get-SbecLogSession
  • Save-SbecLogSession
  • Set-SbecLogSession
  • Start-SbecLogSession
  • Start-SbecNtKernelLogSession
  • Stop-SbecLogSession

To know more PowerShell cmdlets(Commands) on BootEventCollector click here

Click on this Link for an Single place where you get all the PowerShell cmdlet sorted based on the modules.

You can also refer other blogs on PowerShell at link

You can also refer other blogs on Microsoft at link

And also if you required any technology you want to learn, let us know below we will publish them in our site http://tossolution.com/

Like our page in Facebook and follow us for New technical information.

References are taken from Microsoft

Published by Karthik S

Lead DevOps | Windows | AWS | Azure | Docker | Kubernetes | Jenkins

Leave a Reply

Your email address will not be published. Required fields are marked *