<?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: Field extraction from regex issues in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654005#M226004</link>
    <description>&lt;P&gt;I always tell people do not treat structured data as text. &amp;nbsp;You'll regret later. &amp;nbsp;Use spath to unpack JSON; use mvexpand to flatten JSON array.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "^[^{]+ (?&amp;lt;data&amp;gt;{.+})"
| spath input=data path=records{}
| mvexpand records{}
| spath input=records{}
| spath input=records{} path=value.successfulSetoflog{}
| mvexpand value.successfulSetoflog{}
| spath input=value.successfulSetoflog{}
| fields - data records{} value.successfulSetoflog{}.* value.successfulSetoflog{}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The sample data will give you&lt;/P&gt;&lt;TABLE width="3425px"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;awsAccountId&lt;/TD&gt;&lt;TD&gt;event.arn&lt;/TD&gt;&lt;TD&gt;event.endTime&lt;/TD&gt;&lt;TD&gt;event.eventStatusCode&lt;/TD&gt;&lt;TD&gt;event.eventTypeCategory&lt;/TD&gt;&lt;TD&gt;event.lastUpdatedTime&lt;/TD&gt;&lt;TD&gt;event.region&lt;/TD&gt;&lt;TD&gt;event.startTime&lt;/TD&gt;&lt;TD&gt;event.statusCode&lt;/TD&gt;&lt;TD&gt;eventDescription.latestDescription&lt;/TD&gt;&lt;TD&gt;eventTypeCode&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPHeaders.content-length&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPHeaders.context-type&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPHeaders.date&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPHeaders.x-amzn-requestid&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPStatusCode&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.RequestId&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.RetryAttempts&lt;/TD&gt;&lt;TD&gt;value.detail-type&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="126.203125px"&gt;123456789123&lt;/TD&gt;&lt;TD width="1207.5px"&gt;arn:aws:health:us-east-1::event/RDS/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED_SOFTWARE_BACKUP_SCHEDULED&lt;/TD&gt;&lt;TD width="125.921875px"&gt;2020-01-22 04:33:00+00:00&lt;/TD&gt;&lt;TD width="152.65625px"&gt;NUMBER_SPECIFIC&lt;/TD&gt;&lt;TD width="140.96875px"&gt;scheduledChange&lt;/TD&gt;&lt;TD width="186.625px"&gt;2020-02-22 02:05:17.689000+00:00&lt;/TD&gt;&lt;TD width="47.453125px"&gt;us-east-2&lt;/TD&gt;&lt;TD width="125.921875px"&gt;2020-01-20 04:33:00+00:00&lt;/TD&gt;&lt;TD width="64.296875px"&gt;current&lt;/TD&gt;&lt;TD width="245.8125px"&gt;We are contacting you to inform you that one or more of your Amazon authena instances listed in the 'Affected resources' tab are scheduled to receive maintenance on the mentioned hardware between 2020-03-10 04:33 UTC (thursday) and2020-03-10 07:33UTC (thursday). The exact time of the maintenance will be determined by the DB instance if you have any questions or concerns, contact AWS Premium Support. &lt;A href="http://aws.amazon.com/support" target="_blank" rel="noopener"&gt;http://aws.amazon.com/support&lt;/A&gt;&lt;/TD&gt;&lt;TD width="382.359375px"&gt;AWS_DATABASE_SOFTWARE_UPDATE_AVAILABLE&lt;/TD&gt;&lt;TD width="49.40625px"&gt;4000&lt;/TD&gt;&lt;TD width="112.171875px"&gt;application/x-dvz-json-2.1&lt;/TD&gt;&lt;TD width="78.296875px"&gt;Tue, 10 Jan 2020 11:11:11 GMT&lt;/TD&gt;&lt;TD width="121.96875px"&gt;105ab4c6-ccc3-999b-9c84-999320628f00&lt;/TD&gt;&lt;TD width="40px"&gt;500&lt;/TD&gt;&lt;TD width="116.46875px"&gt;yz0c12d7-s44d-8b65-k883-f233rb4cb70c&lt;/TD&gt;&lt;TD width="40px"&gt;0&lt;/TD&gt;&lt;TD width="61.84375px"&gt;AWS API Health Event&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
    <pubDate>Fri, 11 Aug 2023 03:51:24 GMT</pubDate>
    <dc:creator>yuanliu</dc:creator>
    <dc:date>2023-08-11T03:51:24Z</dc:date>
    <item>
      <title>How to do Field extraction from regex issues?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654000#M226003</link>
      <description>&lt;P&gt;Hello Splunk Community,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm trying to extract fields from the cloudwatch events like 1)region 2)arn 3) startTime 4) endTime 5)eventTypeCode 6)latestDescription from an event. The regex works fine in regex101 however it's not extracting all field values in Splunk&lt;/P&gt;
&lt;P&gt;For ex:&amp;nbsp;| rex field=_raw "region":\s(?P&amp;lt;_region&amp;gt;"\w+-\w+-\d)"&lt;/P&gt;
&lt;P&gt;the above rex is only extracting us-east-1 region only where I have multiple regions in the data. Please help to extract the field I mentioned/highlighted.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;sample event:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;2020-02-10T17:42:41.088Z 775ab4c6-ccc3-600b-9c84-124320628f00&lt;/SPAN&gt;&lt;SPAN&gt; {"&lt;/SPAN&gt;&lt;SPAN&gt;records&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;:&lt;/SPAN&gt;&lt;SPAN&gt; [{"&lt;/SPAN&gt;&lt;SPAN&gt;value&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;:&lt;/SPAN&gt;&lt;SPAN&gt; {"&lt;/SPAN&gt;&lt;SPAN&gt;successfulSetoflog&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;:&lt;/SPAN&gt;&lt;SPAN&gt; [{"&lt;/SPAN&gt;&lt;SPAN&gt;awsAccountId&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;:&lt;/SPAN&gt;&lt;SPAN&gt; "&lt;/SPAN&gt;&lt;SPAN&gt;123456789123&lt;/SPAN&gt;&lt;SPAN&gt;", "&lt;/SPAN&gt;&lt;SPAN&gt;event&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;:&lt;/SPAN&gt;&lt;SPAN&gt; {"&lt;/SPAN&gt;&lt;STRONG&gt;arn&lt;/STRONG&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;:&lt;/SPAN&gt;&lt;SPAN&gt; "&lt;/SPAN&gt;&lt;SPAN&gt;arn:aws:health:us-east-........................................................&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 16:59:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654000#M226003</guid>
      <dc:creator>iamsplunker</dc:creator>
      <dc:date>2023-08-14T16:59:01Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction from regex issues</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654005#M226004</link>
      <description>&lt;P&gt;I always tell people do not treat structured data as text. &amp;nbsp;You'll regret later. &amp;nbsp;Use spath to unpack JSON; use mvexpand to flatten JSON array.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "^[^{]+ (?&amp;lt;data&amp;gt;{.+})"
| spath input=data path=records{}
| mvexpand records{}
| spath input=records{}
| spath input=records{} path=value.successfulSetoflog{}
| mvexpand value.successfulSetoflog{}
| spath input=value.successfulSetoflog{}
| fields - data records{} value.successfulSetoflog{}.* value.successfulSetoflog{}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The sample data will give you&lt;/P&gt;&lt;TABLE width="3425px"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;awsAccountId&lt;/TD&gt;&lt;TD&gt;event.arn&lt;/TD&gt;&lt;TD&gt;event.endTime&lt;/TD&gt;&lt;TD&gt;event.eventStatusCode&lt;/TD&gt;&lt;TD&gt;event.eventTypeCategory&lt;/TD&gt;&lt;TD&gt;event.lastUpdatedTime&lt;/TD&gt;&lt;TD&gt;event.region&lt;/TD&gt;&lt;TD&gt;event.startTime&lt;/TD&gt;&lt;TD&gt;event.statusCode&lt;/TD&gt;&lt;TD&gt;eventDescription.latestDescription&lt;/TD&gt;&lt;TD&gt;eventTypeCode&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPHeaders.content-length&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPHeaders.context-type&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPHeaders.date&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPHeaders.x-amzn-requestid&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.HTTPStatusCode&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.RequestId&lt;/TD&gt;&lt;TD&gt;value.ResponseMetatype.RetryAttempts&lt;/TD&gt;&lt;TD&gt;value.detail-type&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="126.203125px"&gt;123456789123&lt;/TD&gt;&lt;TD width="1207.5px"&gt;arn:aws:health:us-east-1::event/RDS/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED_SOFTWARE_BACKUP_SCHEDULED&lt;/TD&gt;&lt;TD width="125.921875px"&gt;2020-01-22 04:33:00+00:00&lt;/TD&gt;&lt;TD width="152.65625px"&gt;NUMBER_SPECIFIC&lt;/TD&gt;&lt;TD width="140.96875px"&gt;scheduledChange&lt;/TD&gt;&lt;TD width="186.625px"&gt;2020-02-22 02:05:17.689000+00:00&lt;/TD&gt;&lt;TD width="47.453125px"&gt;us-east-2&lt;/TD&gt;&lt;TD width="125.921875px"&gt;2020-01-20 04:33:00+00:00&lt;/TD&gt;&lt;TD width="64.296875px"&gt;current&lt;/TD&gt;&lt;TD width="245.8125px"&gt;We are contacting you to inform you that one or more of your Amazon authena instances listed in the 'Affected resources' tab are scheduled to receive maintenance on the mentioned hardware between 2020-03-10 04:33 UTC (thursday) and2020-03-10 07:33UTC (thursday). The exact time of the maintenance will be determined by the DB instance if you have any questions or concerns, contact AWS Premium Support. &lt;A href="http://aws.amazon.com/support" target="_blank" rel="noopener"&gt;http://aws.amazon.com/support&lt;/A&gt;&lt;/TD&gt;&lt;TD width="382.359375px"&gt;AWS_DATABASE_SOFTWARE_UPDATE_AVAILABLE&lt;/TD&gt;&lt;TD width="49.40625px"&gt;4000&lt;/TD&gt;&lt;TD width="112.171875px"&gt;application/x-dvz-json-2.1&lt;/TD&gt;&lt;TD width="78.296875px"&gt;Tue, 10 Jan 2020 11:11:11 GMT&lt;/TD&gt;&lt;TD width="121.96875px"&gt;105ab4c6-ccc3-999b-9c84-999320628f00&lt;/TD&gt;&lt;TD width="40px"&gt;500&lt;/TD&gt;&lt;TD width="116.46875px"&gt;yz0c12d7-s44d-8b65-k883-f233rb4cb70c&lt;/TD&gt;&lt;TD width="40px"&gt;0&lt;/TD&gt;&lt;TD width="61.84375px"&gt;AWS API Health Event&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Fri, 11 Aug 2023 03:51:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654005#M226004</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2023-08-11T03:51:24Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction from regex issues</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654083#M226017</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/33901"&gt;@yuanliu&lt;/a&gt;&amp;nbsp;Thanks for your response, the query you've provided is the example?&lt;BR /&gt;Would you mind to share the example query to unpack the fields I've highlighted in my question.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2023 13:51:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654083#M226017</guid>
      <dc:creator>iamsplunker</dc:creator>
      <dc:date>2023-08-11T13:51:24Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction from regex issues</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654135#M226028</link>
      <description>&lt;P&gt;If you scroll to the right, you will notice that "&lt;STRONG&gt;arn&lt;/STRONG&gt;" is a subnode event.&lt;STRONG&gt;arn&lt;/STRONG&gt;, "&lt;STRONG&gt;region&lt;/STRONG&gt;" is subnode event.&lt;STRONG&gt;region&lt;/STRONG&gt;, and so on; "&lt;STRONG&gt;&lt;SPAN class=""&gt;eventTypeCode&lt;/SPAN&gt;&lt;/STRONG&gt;" is just node &lt;STRONG&gt;&lt;SPAN class=""&gt;eventTypeCode&lt;/SPAN&gt;&lt;/STRONG&gt;, and "&lt;STRONG&gt;latestDescription&lt;/STRONG&gt;" is subnode eventDescription.&lt;STRONG&gt;latestDescription&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;If you only want to see these, you can use fields or table command to list them, e.g.,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "^[^{]+ (?&amp;lt;data&amp;gt;{.+})"
| spath input=data path=records{}
| mvexpand records{}
| spath input=records{}
| spath input=records{} path=value.successfulSetoflog{}
| mvexpand value.successfulSetoflog{}
| spath input=value.successfulSetoflog{}
| fields - data records{} value.successfulSetoflog{}.* value.successfulSetoflog{} _time
| fields event.arn event.region event.startTime event.endTime eventTypeCode eventDescription.latestDescription&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Your sample data will give you listing (again, scroll to the right to see all fields)&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;event.arn&lt;/TD&gt;&lt;TD&gt;event.region&lt;/TD&gt;&lt;TD&gt;event.startTime&lt;/TD&gt;&lt;TD&gt;event.endTime&lt;/TD&gt;&lt;TD&gt;eventTypeCode&lt;/TD&gt;&lt;TD&gt;eventDescription.latestDescription&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;arn:aws:health:us-east-1::event/RDS/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED_SOFTWARE_BACKUP_SCHEDULED&lt;/TD&gt;&lt;TD&gt;us-east-2&lt;/TD&gt;&lt;TD&gt;2020-01-20 04:33:00+00:00&lt;/TD&gt;&lt;TD&gt;2020-01-22 04:33:00+00:00&lt;/TD&gt;&lt;TD&gt;AWS_DATABASE_SOFTWARE_UPDATE_AVAILABLE&lt;/TD&gt;&lt;TD&gt;We are contacting you to inform you that one or more of your Amazon authena instances listed in the 'Affected resources' tab are scheduled to receive maintenance on the mentioned hardware between 2020-03-10 04:33 UTC (thursday) and2020-03-10 07:33UTC (thursday). The exact time of the maintenance will be determined by the DB instance if you have any questions or concerns, contact AWS Premium Support. &lt;A href="http://aws.amazon.com/support" target="_blank" rel="noopener"&gt;http://aws.amazon.com/support&lt;/A&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;This is an emulation for you to play with and compare with real data&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| makeresults
| eval _raw = "2020-02-10T17:42:41.088Z 775ab4c6-ccc3-600b-9c84-124320628f00 {\"records\": [{\"value\": {\"successfulSetoflog\": [{\"awsAccountId\": \"123456789123\", \"event\": {\"arn\": \"arn:aws:health:us-east-1::event/RDS/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED_SOFTWARE_BACKUP_SCHEDULED\", \"eventTypeCategory\": \"scheduledChange\", \"region\": \"us-east-2\", \"startTime\": \"2020-01-20 04:33:00+00:00\", \"endTime\": \"2020-01-22 04:33:00+00:00\", \"lastUpdatedTime\": \"2020-02-22 02:05:17.689000+00:00\", \"statusCode\": \"current\", \"eventStatusCode\": \"NUMBER_SPECIFIC\"}, \"eventTypeCode\": \"AWS_DATABASE_SOFTWARE_UPDATE_AVAILABLE\", \"eventDescription\": {\"latestDescription\": \"We are contacting you to inform you that one or more of your Amazon authena instances listed in the 'Affected resources' tab are scheduled to receive maintenance on the mentioned hardware between 2020-03-10 04:33 UTC (thursday) and2020-03-10 07:33UTC (thursday). The exact time of the maintenance will be determined by the DB instance if you have any questions or concerns, contact AWS Premium Support. \\n\\nhttp://aws.amazon.com/support\"}}], \"failedSet\": [], \"ResponseMetatype\": {\"RequestId\": \"yz0c12d7-s44d-8b65-k883-f233rb4cb70c\", \"HTTPStatusCode\": 500, \"HTTPHeaders\": {\"x-amzn-requestid\": \"105ab4c6-ccc3-999b-9c84-999320628f00 \", \"context-type\": \"application/x-dvz-json-2.1\", \"content-length\": \"4000\", \"date\": \"Tue, 10 Jan 2020 11:11:11 GMT\"}, \"RetryAttempts\": 0}, \"detail-type\": \"AWS API Health Event\"}}]}"
``` data emulation above ```&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 12 Aug 2023 00:03:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654135#M226028</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2023-08-12T00:03:19Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction from regex issues</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654150#M226039</link>
      <description>&lt;P&gt;For this type of data, you can use the &lt;STRONG&gt;extract&lt;/STRONG&gt; command.&amp;nbsp; To make it work, we need to remove the part before the first &lt;STRONG&gt;{&lt;/STRONG&gt;.&amp;nbsp; (It can be saved to a field if needed)&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| makeresults
| eval _raw="2020-02-10T17:42:41.088Z 775ab4c6-ccc3-600b-9c84-124320628f00 {\"records\": [{\"value\": {\"successfulSetoflog\": [{\"awsAccountId\": \"123456789123\", \"event\": {\"arn\": \"arn:aws:health:us-east-1::event/RDS/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED/AWS_RDS_AURORA_SOFTWARE_BACKUP_SCHEDULED_SOFTWARE_BACKUP_SCHEDULED\", \"eventTypeCategory\": \"scheduledChange\", \"region\": \"us-east-2\", \"startTime\": \"2020-01-20 04:33:00+00:00\", \"endTime\": \"2020-01-22 04:33:00+00:00\", \"lastUpdatedTime\": \"2020-02-22 02:05:17.689000+00:00\", \"statusCode\": \"current\", \"eventStatusCode\": \"NUMBER_SPECIFIC\"}, \"eventTypeCode\": \"AWS_DATABASE_SOFTWARE_UPDATE_AVAILABLE\", \"eventDescription\": {\"latestDescription\": \"We are contacting you to inform you that one or more of your Amazon authena instances listed in the 'Affected resources' tab are scheduled to receive maintenance on the mentioned hardware between 2020-03-10 04:33 UTC (thursday) and2020-03-10 07:33UTC (thursday). The exact time of the maintenance will be determined by the DB instance if you have any questions or concerns, contact AWS Premium Support. \n\nhttp://aws.amazon.com/support\"}}], \"failedSet\": [], \"ResponseMetatype\": {\"RequestId\": \"yz0c12d7-s44d-8b65-k883-f233rb4cb70c\", \"HTTPStatusCode\": 500, \"HTTPHeaders\": {\"x-amzn-requestid\": \"105ab4c6-ccc3-999b-9c84-999320628f00 \", \"context-type\": \"application/x-dvz-json-2.1\", \"content-length\": \"4000\", \"date\": \"Tue, 10 Jan 2020 11:11:11 GMT\"}, \"RetryAttempts\": 0}, \"detail-type\": \"AWS API Health Event\"}}]}"
| rex mode=sed "s/^[^{]+//"
| extract&lt;/LI-CODE&gt;</description>
      <pubDate>Sat, 12 Aug 2023 07:39:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-do-Field-extraction-from-regex-issues/m-p/654150#M226039</guid>
      <dc:creator>jotne</dc:creator>
      <dc:date>2023-08-12T07:39:31Z</dc:date>
    </item>
  </channel>
</rss>

