All Apps and Add-ons

Linux DHCP new regex,New dhcp log format

nocsolcon
Explorer

We've upgraded our DHCP server to debian 9. Now the dhcp log is written differently then on our old server
log lines contains now: dhcpd[1569]: instead of dhcpd:

Jul 18 09:12:43 dhcp-server-name dhcpd[1569]: DHCPACK on ip-address to 00:00:00:00:00:00 (modem-type) via ip-address

the app: Linux DHCP can not handle this

can we change the regex in transform.conf

from:
\s(dhcpd):\s

to:
\sdhcpd(:\s|[\d+]:\s)

or should we change more? I tested it, but this change to transform.conf does not work

0 Karma

FrankVl
Ultra Champion

Try escaping those [ ] characters. They have special meaning in regular expressions, so if you want to match actual brackets, they need to be escaped: \sdhcpd(\:\s|\[\d+\]\:\s) https://regex101.com/r/pRwz3z/1

nocsolcon
Explorer

I've fixed it by changing all the regex in the transforms.conf

from:

\s(dhcpd)\:\s

to:

 \sdhcpd(\:\s|\[\d+\]:\s)

Also we need to change the file: eventtypes.conf

from:

[dhcpd_event]
search = process=dhcpd

to:

[dhcpd_event]
search = dhcpd

After this, it is working for the old and new log lines

0 Karma

FrankVl
Ultra Champion

Why the double backslashes?

0 Karma

nocsolcon
Explorer

Sorry, my mistake. I changed it.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...