New source: IPMI Log input

root@server:~# ipmitool sel elist 
   1 | 01/15/2017 | 15:27:10 | Physical Security Chassis Intru | General Chassis intrusion () | Asserted
   2 | 01/16/2017 | 15:04:48 | Physical Security Chassis Intru | General Chassis intrusion () | Asserted
   3 | 02/13/2017 | 12:37:16 | Physical Security Chassis Intru | General Chassis intrusion () | Asserted
   4 | 06/18/2017 | 07:42:09 | Drive Slot HDD Status | Drive Fault () | Asserted
   5 | 06/18/2017 | 10:08:38 | Drive Slot HDD Status | Drive Present () | Asserted
   6 | 06/18/2017 | 10:08:39 | Unknown #0x52 |  | Asserted
   7 | 12/03/2017 | 01:14:02 | Unknown #0x52 |  | Asserted
   8 | 12/03/2017 | 01:14:04 | Physical Security Chassis Intru | General Chassis intrusion () | Asserted
   9 | 12/03/2017 | 01:14:06 | Drive Slot HDD Status | Drive Fault () | Asserted
   a | 12/03/2017 | 02:17:59 | Unknown #0x52 |  | Asserted

Telegraf already get metric info:
https://github.com/influxdata/telegraf/tree/master/plugins/inputs/ipmi_sensor
Or exporter for Prometheus:
https://github.com/soundcloud/ipmi_exporter

But will be awesome if vector get Baremetal server logs as different channel.

Hardware monitoring is the big deal. Log level will be awesome and ipmi is great tool.
And many vendors use it.
https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface#Implementations

Detection is simple:

dmidecode -t 38

https://medium.com/@semnanweb/how-get-dedicate-server-metrics-123b5dffada7

Start with the proposed ipmitool sel elist output and the dmidecode -t 38 detection command. Review Vector's existing input sources and the referenced Telegraf ipmi_sensor and Prometheus exporter implementations to define the source scope, parsing behavior, and log output. Done means a documented IPMI log source with clear detection and output behavior.