<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to break event 1 and 2 further? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396798#M70711</link>
    <description>&lt;P&gt;It should work for that case.&lt;/P&gt;</description>
    <pubDate>Fri, 19 Jul 2019 01:43:12 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2019-07-19T01:43:12Z</dc:date>
    <item>
      <title>How to break event 1 and 2 further?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396793#M70706</link>
      <description>&lt;P&gt;Each Realm entry should be an event, JSON is the source.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Event1:&lt;/STRONG&gt; &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{"realm":"/humapp","transactionId":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2328639","component":"Authentication","eventName":"AM-LOGIN-MODULE-COMPLETED","result":"SUCCESSFUL","entries":[{"moduleId":"Application","info":{"authIndex":"module_instance","authControlFlag":"REQUIRED","moduleClass":"Application","ipAddress":"10.254.110.61","authLevel":"0"}}],"userId":"","principal":["HUMAppAgent"],"timestamp":"2019-07-15T11:29:36.221Z","trackingIds":["25ac5061b64b400902"],"_id":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2328643"}
{"realm":"/humapp","transactionId":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2328639","component":"Authentication","eventName":"AM-LOGIN-COMPLETED","result":"SUCCESSFUL","entries":[{"moduleId":"Application","info":{"authIndex":"module_instance","ipAddress":"10.254.110.61","authLevel":"0"}}],"userId":"id=HUMAppAgent,ou=agent,o=humapp,ou=services,dc=openam,dc=verizontelematics,dc=com","principal":["HUMAppAgent"],"timestamp":"2019-07-15T11:29:36.235Z","trackingIds":["25ac5061b64b400902"],"_id":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2328647"}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;Event2 :&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{"realm":"/healthcheck","transactionId":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2328622","component":"Authentication","eventName":"AM-LOGIN-MODULE-COMPLETED","result":"SUCCESSFUL","entries":[{"moduleId":"DataStore","info":{"authControlFlag":"REQUIRED","moduleClass":"DataStore","ipAddress":"10.254.110.18","authLevel":"0"}}],"userId":"id=healthcheck01,ou=user,o=healthcheck,ou=services,dc=openam,dc=verizontelematics,dc=com","principal":["healthcheck01"],"timestamp":"2019-07-15T11:29:27.274Z","trackingIds":["6cea414e7a464b4d02"],"_id":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2328624"}
{"realm":"/healthcheck","transactionId":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2328622","component":"Authentication","eventName":"AM-LOGIN-COMPLETED","result":"SUCCESSFUL","entries":[{"moduleId":"DataStore","info":{"ipAddress":"10.254.110.18","authLevel":"0"}}],"userId":"id=healthcheck01,ou=user,o=healthcheck,ou=services,dc=openam,dc=verizontelematics,dc=com","principal":["healthcheck01"],"timestamp":"2019-07-15T11:29:27.295Z","trackingIds":["6cea414e7a464b4d02"],"_id":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2328628"}
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 15 Jul 2019 11:43:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396793#M70706</guid>
      <dc:creator>Sujithkumarkb</dc:creator>
      <dc:date>2019-07-15T11:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to break event 1 and 2 further?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396794#M70707</link>
      <description>&lt;P&gt;I tried with should_line_merge=false and it works fine on local .But how can i map it to the index and sourcetype on production , as i am unable to find the sourcetype declared in production to update with new config&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 01:22:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396794#M70707</guid>
      <dc:creator>Sujithkumarkb</dc:creator>
      <dc:date>2020-09-30T01:22:37Z</dc:date>
    </item>
    <item>
      <title>Re: How to break event 1 and 2 further?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396795#M70708</link>
      <description>&lt;P&gt;You need something like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[&amp;lt;your sourcetype here&amp;gt;]
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)(?=$|{"realm)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;As far as &lt;CODE&gt;finding the sourcetype declaration&lt;/CODE&gt;, you do not need to do that.  Many people have an app called something like &lt;CODE&gt;global_props&lt;/CODE&gt; or whatever and deploy configurations there.  Splunk will merge them all together.  You can see this using &lt;CODE&gt;$SPLUNK_HOME/bin/splunk btool props list --debug&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jul 2019 14:39:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396795#M70708</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-07-15T14:39:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to break event 1 and 2 further?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396796#M70709</link>
      <description>&lt;P&gt;Hey Woodcock, &lt;BR /&gt;
Thanks for the response , this works fine unless the each realm event starts from a new line as shown above in the preview . does not work when a new realm event starts on the same line as end of previous realm event line.&lt;/P&gt;

&lt;P&gt;{"&lt;STRONG&gt;realm&lt;/STRONG&gt;":"/healthcheck","transactionId":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2328622","component":"Authentication","eventName":"AM-LOGIN-MODULE-COMPLETED","result":"SUCCESSFUL","entries":[{"moduleId":"DataStore","info":{"authControlFlag":"REQUIRED","moduleClass":"DataStore","ipAddress":"10.254.110.18","authLevel":"0"}}],"userId":"id=healthcheck01,ou=user,o=healthcheck,ou=services,dc=openam,dc=verizontelematics,dc=com","principal":["healthcheck01"],"timestamp":"2019-07-15T11:29:27.274Z","trackingIds":["6cea414e7a464b4d02"],"_id"}{"&lt;STRONG&gt;realm&lt;/STRONG&gt;":"/healthcheck","transactionId":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2019 06:46:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396796#M70709</guid>
      <dc:creator>Sujithkumarkb</dc:creator>
      <dc:date>2019-07-16T06:46:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to break event 1 and 2 further?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396797#M70710</link>
      <description>&lt;P&gt;This is how it is indexing now. The first one is fine ,but second event has second half of first event and the half of second event&lt;BR /&gt;
7/16/19&lt;BR /&gt;
2:50:39.000 AM&lt;BR /&gt;
{"&lt;STRONG&gt;realm&lt;/STRONG&gt;":"/healthcheck","transactionId":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2411601","component":"Authentication","eventName":"AM-LOGIN-COMPLETED","result":"SUCCESSFUL","entries":[{"moduleId":"DataStore","info":{"ipAddress":"10.254.110.18","authLevel":"0"}}],"userId":"id=healthcheck01,ou=user,o=healthcheck,ou=services,dc=openam,dc=verizontelematics,dc=com","principal":["healthcheck01"],"timestamp":"2019-07-16T06:50:38.672Z","trackingIds":["3278ae96d06b64c602"],"_id":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2411607"}&lt;/P&gt;

&lt;P&gt;7/16/19&lt;BR /&gt;
12:28:36.000 PM &lt;BR /&gt;
{"&lt;STRONG&gt;realm&lt;/STRONG&gt;":"/healthcheck","transactionId":"25c79b89-329b-462e-950b-0f75fd67a3ae-72771235","component":"Authentication","eventName":"AM-LOGIN-COMPLETED","result":"SUCCESSFUL","entries":[{"moduleId":"LDAP","info":{"ipAddress":"10.223.108.29","authLevel":"0"}}],"userId":"cn=healthcheck01,ou=Users,ou=HealthCheck,ou=external,dc=verizontelematics,dc=com","principal":["healthcheck01"],"timestamp":"2019-07-16T05:57:41.089Z","trackingIds":["bf6f5024a8b7f65f02"],"_id":"25c79b89-329b-462e-950b-0f75fd67a3ae-&lt;STRONG&gt;72771241"}{"&lt;/STRONG&gt;realm*&lt;EM&gt;":"/healthch&lt;/EM&gt;*eck","transactionId":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2411601","component":"Authentication","eventName":"AM-LOGIN-MODULE-COMPLETED","result":"SUCCESSFUL","entries":[{"moduleId":"DataStore","info":{"authControlFlag":"REQUIRED","moduleClass":"DataStore","ipAddress":"10.254.110.18","authLevel":"0"}}],"userId":"id=healthcheck01,ou=user,o=healthcheck,ou=services,dc=openam,dc=verizontelematics,dc=com","principal":["healthcheck01"],"timestamp":"2019-07-16T06:50:38.653Z","trackingIds":["3278ae96d06b64c602"],"_id":"d9d6ba4e-c3bb-416e-b81b-3eb3afb3737a-2411603"}&lt;BR /&gt;
host = VDI-W10-13270 source = C:\Users\Sujith.Kumarkb.HUGHESTELEMATIC\Desktop\Forgerock.txt sourcetype = forgerock_16july&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 01:23:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396797#M70710</guid>
      <dc:creator>Sujithkumarkb</dc:creator>
      <dc:date>2020-09-30T01:23:01Z</dc:date>
    </item>
    <item>
      <title>Re: How to break event 1 and 2 further?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396798#M70711</link>
      <description>&lt;P&gt;It should work for that case.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2019 01:43:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-break-event-1-and-2-further/m-p/396798#M70711</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-07-19T01:43:12Z</dc:date>
    </item>
  </channel>
</rss>

