Wildcard/Select all fields

[stephanbuys]

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

[eskibars]

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

[ArtyomBaranovskiy]

+1

[bigtoerag]

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?

[ArtyomBaranovskiy]

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