Splunk Search

Formatting log data question

dbcase
Motivator

Hi,

I have the below log data. It appears to be all one line. What I'd like to do is:

  1. Have a separate event everytime there is a new LogMessage dateTime
  2. discard the <?xml version="1.0" encoding="UTF-8" ?><LogData version="1.0">
  3. extract the fields:
  4. dateTime severity pid pname client

I'm not quite sure where to begin.... Any thoughts?

`<?xml version="1.0" encoding="UTF-8" ?><LogData version="1.0">`<LogMessage dateTime="2017-02-14T20:17:06.000-08:00" severity="Notice" pid="7675" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7675) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:16:52.000-08:00" severity="Notice" pid="7629" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7629) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:16:36.000-08:00" severity="Notice" pid="7573" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7573) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:16:21.000-08:00" severity="Notice" pid="7521" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7521) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:16:05.000-08:00" severity="Notice" pid="7467" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7467) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:15:49.000-08:00" severity="Notice" pid="7397" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7397) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:15:34.000-08:00" severity="Notice" pid="7345" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7345) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:15:18.000-08:00" severity="Notice" pid="7283" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7283) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:15:03.000-08:00" severity="Notice" pid="7237" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7237) start to connect to server stunnel.</LogMessage>
0 Karma

mpreddy
Communicator

try this:

-If you want to discard the XML tag use transforms.conf and send it to null queue

0 Karma

somesoni2
Revered Legend

Give this a try

props.conf on indexer/heavy forwarder

[YourSourceType]
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]*)(?=\<LogMessage dateTime)
TIME_PREFIX = \<LogMessage dateTime=\"
TIME_FORMAT = %Y-%m-%dT%H:%M:%S.%N%z
MAX_TIMESTAMP_LOOKAHEAD =28
0 Karma

nickhills
Ultra Champion

Is that paste complete?

you seem to be missing a closing </xml> tag.

The reason I ask is that if your XML is well formatted you should be able to use SPATH to achieve what you need.

Otherwise your going to need to configure some custom index time line breaking

If my comment helps, please give it a thumbs up!
0 Karma

dbcase
Motivator

its a snippet..... Here is the beginning some of the middle and end entry

<?xml version="1.0" encoding="UTF-8" ?><LogData version="1.0"><LogMessage dateTime="2017-02-14T20:17:06.000-08:00" severity="Notice" pid="7675" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7675) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:16:52.000-08:00" severity="Notice" pid="7629" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7629) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:16:36.000-08:00" severity="Notice" pid="7573" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7573) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:16:21.000-08:00" severity="Notice" pid="7521" pname="stunnel">CLIENT: /usr/local/bin/stunnel(7521) start to connect to server stunnel.</LogMessage>pname="stunnel">CLIENT: /usr/local/bin/stunnel(5799) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:07:46.000-08:00" severity="Notice" pid="5739" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5739) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:07:31.000-08:00" severity="Notice" pid="5685" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5685) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:07:15.000-08:00" severity="Notice" pid="5635" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5635) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:07:00.000-08:00" severity="Notice" pid="5579" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5579) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:06:44.000-08:00" severity="Notice" pid="5529" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5529) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:06:29.000-08:00" severity="Notice" pid="5475" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5475) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:06:13.000-08:00" severity="Notice" pid="5423" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5423) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:05:58.000-08:00" severity="Notice" pid="5371" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5371) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:05:42.000-08:00" severity="Notice" pid="5313" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5313) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:05:27.000-08:00" severity="Notice" pid="5265" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5265) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:05:11.000-08:00" severity="Notice" pid="5203" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5203) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:04:56.000-08:00" severity="Notice" pid="5155" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5155) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:04:40.000-08:00" severity="Notice" pid="5109" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5109) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:04:25.000-08:00" severity="Notice" pid="5047" pname="stunnel">CLIENT: /usr/local/bin/stunnel(5047) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:04:09.000-08:00" severity="Notice" pid="4997" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4997) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:03:54.000-08:00" severity="Notice" pid="4943" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4943) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:03:38.000-08:00" severity="Notice" pid="4889" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4889) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:03:23.000-08:00" severity="Notice" pid="4841" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4841) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:03:07.000-08:00" severity="Notice" pid="4783" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4783) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:02:52.000-08:00" severity="Notice" pid="4735" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4735) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:02:36.000-08:00" severity="Notice" pid="4677" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4677) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:02:21.000-08:00" severity="Notice" pid="4627" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4627) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:02:05.000-08:00" severity="Notice" pid="4577" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4577) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:01:50.000-08:00" severity="Notice" pid="4517" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4517) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:01:34.000-08:00" severity="Notice" pid="4467" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4467) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:01:19.000-08:00" severity="Notice" pid="4419" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4419) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:01:03.000-08:00" severity="Notice" pid="4359" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4359) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:00:48.000-08:00" severity="Notice" pid="4313" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4313) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:00:46.000-08:00" severity="Notice" pid="4301" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4301) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:00:32.000-08:00" severity="Notice" pid="4253" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4253) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:00:17.000-08:00" severity="Notice" pid="4201" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4201) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T20:00:01.000-08:00" severity="Notice" pid="4147" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4147) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:59:46.000-08:00" severity="Notice" pid="4095" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4095) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:59:30.000-08:00" severity="Notice" pid="4045" pname="stunnel">CLIENT: /usr/local/bin/stunnel(4045) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:59:15.000-08:00" severity="Notice" pid="3988" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3988) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:58:59.000-08:00" severity="Notice" pid="3934" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3934) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:58:44.000-08:00" severity="Notice" pid="3828" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3828) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:58:28.000-08:00" severity="Notice" pid="3770" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3770) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:58:13.000-08:00" severity="Notice" pid="3724" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3724) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:57:57.000-08:00" severity="Notice" pid="3672" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3672) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:57:42.000-08:00" severity="Notice" pid="3612" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3612) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:57:26.000-08:00" severity="Notice" pid="3560" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3560) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:57:11.000-08:00" severity="Notice" pid="3508" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3508) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:56:55.000-08:00" severity="Notice" pid="3456" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3456) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:56:40.000-08:00" severity="Notice" pid="3402" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3402) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:56:24.000-08:00" severity="Notice" pid="3350" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3350) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:56:09.000-08:00" severity="Notice" pid="3294" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3294) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:55:53.000-08:00" severity="Notice" pid="3244" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3244) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:55:38.000-08:00" severity="Notice" pid="3192" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3192) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:55:22.000-08:00" severity="Notice" pid="3140" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3140) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:55:06.000-08:00" severity="Notice" pid="3080" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3080) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:54:51.000-08:00" severity="Notice" pid="3032" pname="stunnel">CLIENT: /usr/local/bin/stunnel(3032) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:54:35.000-08:00" severity="Notice" pid="2982" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2982) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:54:20.000-08:00" severity="Notice" pid="2924" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2924) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:54:04.000-08:00" severity="Notice" pid="2872" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2872) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:53:48.000-08:00" severity="Notice" pid="2820" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2820) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:53:32.000-08:00" severity="Notice" pid="2762" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2762) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:53:17.000-08:00" severity="Notice" pid="2710" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2710) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:53:01.000-08:00" severity="Notice" pid="2656" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2656) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:52:46.000-08:00" severity="Notice" pid="2606" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2606) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:52:30.000-08:00" severity="Notice" pid="2554" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2554) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:52:15.000-08:00" severity="Notice" pid="2498" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2498) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:51:59.000-08:00" severity="Notice" pid="2448" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2448) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:51:44.000-08:00" severity="Notice" pid="2386" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2386) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:51:28.000-08:00" severity="Notice" pid="2338" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2338) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:51:12.000-08:00" severity="Notice" pid="2292" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2292) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:50:57.000-08:00" severity="Notice" pid="2230" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2230) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:50:41.000-08:00" severity="Notice" pid="2180" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2180) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:50:26.000-08:00" severity="Notice" pid="2126" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2126) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:50:10.000-08:00" severity="Notice" pid="2072" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2072) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:49:54.000-08:00" severity="Notice" pid="2018" pname="stunnel">CLIENT: /usr/local/bin/stunnel(2018) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:49:39.000-08:00" severity="Notice" pid="1964" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1964) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:49:23.000-08:00" severity="Notice" pid="1916" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1916) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:49:08.000-08:00" severity="Notice" pid="1860" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1860) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:48:52.000-08:00" severity="Notice" pid="1808" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1808) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:48:37.000-08:00" severity="Notice" pid="1756" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1756) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:48:21.000-08:00" severity="Notice" pid="1696" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1696) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:48:15.000-08:00" severity="Notice" pid="1682" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1682) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:48:06.000-08:00" severity="Notice" pid="1646" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1646) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:47:50.000-08:00" severity="Notice" pid="1590" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1590) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:47:34.000-08:00" severity="Notice" pid="1538" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1538) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:47:19.000-08:00" severity="Notice" pid="1486" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1486) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:47:03.000-08:00" severity="Notice" pid="1434" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1434) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:46:48.000-08:00" severity="Notice" pid="1382" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1382) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:46:47.000-08:00" severity="Notice" pid="617" pname="dhcpcd">DHCP: Lease renewal successfully.</LogMessage><LogMessage dateTime="2017-02-14T19:46:44.000-08:00" severity="Notice" pid="1370" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1370) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:46:32.000-08:00" severity="Notice" pid="1322" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1322) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:46:17.000-08:00" severity="Notice" pid="1274" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1274) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:46:01.000-08:00" severity="Notice" pid="1218" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1218) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:45:45.000-08:00" severity="Notice" pid="1142" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1142) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:45:30.000-08:00" severity="Notice" pid="1096" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1096) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:45:14.000-08:00" severity="Notice" pid="1043" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1043) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:45:14.000-08:00" severity="Notice" pid="1042" pname="stunnel">CLIENT: /usr/local/bin/stunnel(1042) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:44:58.000-08:00" severity="Notice" pid="984" pname="stunnel">CLIENT: /usr/local/bin/stunnel(984) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:44:43.000-08:00" severity="Notice" pid="932" pname="stunnel">CLIENT: /usr/local/bin/stunnel(932) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:44:28.000-08:00" severity="Notice" pid="880" pname="stunnel">CLIENT: /usr/local/bin/stunnel(880) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:44:12.000-08:00" severity="Notice" pid="828" pname="stunnel">CLIENT: /usr/local/bin/stunnel(828) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:43:56.000-08:00" severity="Notice" pid="772" pname="stunnel">CLIENT: /usr/local/bin/stunnel(772) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:43:41.000-08:00" severity="Notice" pid="723" pname="stunnel">CLIENT: /usr/local/bin/stunnel(723) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:43:26.000-08:00" severity="Notice" pid="658" pname="stunnel">CLIENT: /usr/local/bin/stunnel(658) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:43:10.000-08:00" severity="Notice" pid="600" pname="stunnel">CLIENT: /usr/local/bin/stunnel(600) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:42:55.000-08:00" severity="Notice" pid="548" pname="stunnel">CLIENT: /usr/local/bin/stunnel(548) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:42:39.000-08:00" severity="Notice" pid="483" pname="stunnel">CLIENT: /usr/local/bin/stunnel(483) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:42:24.000-08:00" severity="Notice" pid="426" pname="stunnel">CLIENT: /usr/local/bin/stunnel(426) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:42:08.000-08:00" severity="Notice" pid="357" pname="stunnel">CLIENT: /usr/local/bin/stunnel(357) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:41:53.000-08:00" severity="Notice" pid="309" pname="stunnel">CLIENT: /usr/local/bin/stunnel(309) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:41:37.000-08:00" severity="Notice" pid="32719" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32719) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:41:22.000-08:00" severity="Notice" pid="32667" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32667) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:41:06.000-08:00" severity="Notice" pid="32616" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32616) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:40:50.000-08:00" severity="Notice" pid="32559" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32559) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:40:35.000-08:00" severity="Notice" pid="32507" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32507) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:40:19.000-08:00" severity="Notice" pid="32455" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32455) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:40:04.000-08:00" severity="Notice" pid="32401" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32401) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:39:48.000-08:00" severity="Notice" pid="32349" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32349) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:39:33.000-08:00" severity="Notice" pid="32295" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32295) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:39:17.000-08:00" severity="Notice" pid="32245" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32245) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:39:01.000-08:00" severity="Notice" pid="32183" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32183) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:38:46.000-08:00" severity="Notice" pid="32137" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32137) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:38:30.000-08:00" severity="Notice" pid="32087" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32087) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:38:14.000-08:00" severity="Notice" pid="32025" pname="stunnel">CLIENT: /usr/local/bin/stunnel(32025) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:37:59.000-08:00" severity="Notice" pid="31975" pname="stunnel">CLIENT: /usr/local/bin/stunnel(31975) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:37:43.000-08:00" severity="Notice" pid="31921" pname="stunnel">CLIENT: /usr/local/bin/stunnel(31921) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:37:28.000-08:00" severity="Notice" pid="31867" pname="stunnel">CLIENT: /usr/local/bin/stunnel(31867) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:37:12.000-08:00" severity="Notice" pid="31817" pname="stunnel">CLIENT: /usr/local/bin/stunnel(31817) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:36:56.000-08:00" severity="Notice" pid="31761" pname="stunnel">CLIENT: /usr/local/bin/stunnel(31761) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:36:41.000-08:00" severity="Notice" pid="31711" pname="stunnel">CLIENT: /usr/local/bin/stunnel(31711) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:36:25.000-08:00" severity="Notice" pid="31655" pname="stunnel">CLIENT: /usr/local/bin/stunnel(31655) start to connect to server stunnel.</LogMessage><LogMessage dateTime="2017-02-14T19:36:10.000-08:00" severity="Notice" pid="31603" pname="stunnel">CLIENT: /usr/local/bin/stunnel(31603) start to connect to server stunnel.</LogMessage></LogData>[root@splunkmsologs beta_cameras]#
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Casting Call: Compete in Cyber Games

Lights, Camera, SecOps: Apply to Compete in Cyber Games     Think you have what it takes to beat the clock? ...

Data Management Digest – June 2026

Welcome to the June 2026 edition of Data Management Digest! This month’s update is short and sweet, with a ...

Think Like an Architect: Introducing the Splunk Certified Cybersecurity Defense ...

In cybersecurity, defenders respond to threats. Architects design the systems that stop them.    As ...