wmibeat icon indicating copy to clipboard operation
wmibeat copied to clipboard

Wildcard/Select all fields

Open stephanbuys opened this issue 8 years ago • 4 comments

I'm testing this beat now and it looks quite cool. Is there a way to automatically select 'all' fields?

stephanbuys avatar May 10 '16 10:05 stephanbuys

Not at the moment, but it's a nice idea!

eskibars avatar May 18 '16 15:05 eskibars

+1

ArtyomBaranovskiy avatar May 19 '16 08:05 ArtyomBaranovskiy

I tried manually adding all fields for the ones in your yml file but I keep hitting this error:

2016/07/29 05:42:57.545724 beat.go:273: CRIT Running the beat returned an error: Exception occurred. Start error: Exception occurred. 2016/07/29 05:42:57.545724 beat.go:126: CRIT Start error: Exception occurred. 2016/07/29 05:42:57.545724 beat.go:307: INFO Start exiting beat 2016/07/29 05:42:57.545724 beat.go:282: INFO Stopping Beat 2016/07/29 05:42:57.545724 beat.go:290: INFO Cleaning up wmibeat before shutting down. 2016/07/29 05:42:57.545724 beat.go:139: INFO Exit beat completed

The config section that bombs out is this: ` - class: Win32_PerfFormattedData_PerfOS_System fields:

  •   - AlignmentFixupsPersec
    
  •   - Caption
    
  •   - ContextSwitchesPersec
    
  •   - Description
    
  •   - ExceptionDispatchesPersec
    
  •   - FileControlBytesPersec
    
  •   - FileControlOperationsPersec
    
  •   - FileDataOperationsPersec
    
  •   - FileReadBytesPersec
    
  •   - FileReadOperationsPersec
    
  •   - FileWriteBytesPersec
    
  •   - FileWriteOperationsPersec
    
  •   - FloatingEmulationsPersec
    
  •   - Name
    
  •   - PercentRegistryQuotaInUse
    
  •   - Processes
    
  •   - ProcessorQueueLength
    
  •   - SystemCallsPersec
    
  •   - SystemUpTime
    
  •   - Threads
    

`

Win32_PerfFormattedData_PerfOS_Memory, Win32_PerfFormattedData_PerfDisk_LogicalDisk, Win32_OperatingSystem all work fine with all fields.

Any idea from the code line in the error?

bigtoerag avatar Jul 29 '16 05:07 bigtoerag

@bigtoerag I'd recommend to avoid using this wmibeat implementation in production, because there is a crucial resource leak inside. The pull request (https://github.com/eskibars/wmibeat/pull/2) fixing it was created quite a long time ago, so I assume @eskibars is no more interested in supporting the repository.

ArtyomBaranovskiy avatar Jul 29 '16 08:07 ArtyomBaranovskiy