<?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: lifecycle of a oneview alert in HPE Synergy</title>
    <link>https://community.hpe.com/t5/hpe-synergy/lifecycle-of-a-oneview-alert/m-p/7103964#M392</link>
    <description>&lt;P&gt;The state of the alert does not change the URI of the alert.&amp;nbsp; If there is an external source that is indicating the change of state, a new alert would be generated to indicate the status of that external resource has changed, and the correlated alert is cleared.&amp;nbsp; This is mostly when there is a physical problem with a server.&lt;/P&gt;</description>
    <pubDate>Tue, 06 Oct 2020 14:20:25 GMT</pubDate>
    <dc:creator>ChrisLynch</dc:creator>
    <dc:date>2020-10-06T14:20:25Z</dc:date>
    <item>
      <title>lifecycle of a oneview alert</title>
      <link>https://community.hpe.com/t5/hpe-synergy/lifecycle-of-a-oneview-alert/m-p/7103855#M389</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;from curiosity Im asking my self if teh alert is generated with an uri ex. /rest/alerts/2 and its in state Active or Locked. Once the condition that generated alert will be resolved the alert goes to state Cleared and the uri remains the same /rest/alerts/2 ?&lt;/P&gt;&lt;P&gt;The idea is to get alerts that are active or locked - after a while get alerts that have been cleared - and pair this information. Or the uri is always the same and there is another way how to identify eg. pair the cleared alert with the active/locked alert.&lt;/P&gt;&lt;P&gt;Reading from docu alertState - The system will automatically set the state of an alert to Cleared if the severity of alert is OK.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://techlibrary.hpe.com/docs/enterprise/servers/oneview5.0/cicf-api/en/index.html#rest/alerts" target="_blank" rel="noopener"&gt;https://techlibrary.hpe.com/docs/enterprise/servers/oneview5.0/cicf-api/en/index.html#rest/alerts&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks a lot for hints&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Oct 2020 19:36:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/lifecycle-of-a-oneview-alert/m-p/7103855#M389</guid>
      <dc:creator>placka</dc:creator>
      <dc:date>2020-10-05T19:36:22Z</dc:date>
    </item>
    <item>
      <title>Re: lifecycle of a oneview alert</title>
      <link>https://community.hpe.com/t5/hpe-synergy/lifecycle-of-a-oneview-alert/m-p/7103862#M390</link>
      <description>&lt;P&gt;Essentially, the URI of an alert will perpetually be the URI.&amp;nbsp; While the unique ID is a numerical value, it would end at&amp;nbsp;9223372036854775807, and then roll over back to 1.&amp;nbsp; So needless to say, no one should ever get close to that number.&lt;/P&gt;&lt;P&gt;Slight edit here:&amp;nbsp; I should say that the alert URI should always be the assigned URI, unless the alert can be deleted.&amp;nbsp; Not all alerts can be deleted.&amp;nbsp; But if it does, the numerical value isn't assigned again until roll over.&amp;nbsp; Which I have already established should never happen.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Oct 2020 22:12:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/lifecycle-of-a-oneview-alert/m-p/7103862#M390</guid>
      <dc:creator>ChrisLynch</dc:creator>
      <dc:date>2020-10-05T22:12:46Z</dc:date>
    </item>
    <item>
      <title>Re: lifecycle of a oneview alert</title>
      <link>https://community.hpe.com/t5/hpe-synergy/lifecycle-of-a-oneview-alert/m-p/7103885#M391</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;thanks for insight.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;S its my understanding that:&lt;/P&gt;&lt;P&gt;1. some alert will be generated ( shortened and simlified )&lt;/P&gt;&lt;P&gt;with:&lt;/P&gt;&lt;P&gt;some problem AAA&lt;/P&gt;&lt;P&gt;uri /rest/alerts/2&lt;/P&gt;&lt;P&gt;alertstate: active&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. situation that generated the alert will pass - will the uri remain the same ? ( in between there was another alert generated with /rest/alert/3 some problem BBB )&lt;/P&gt;&lt;P&gt;some problem AAA&lt;/P&gt;&lt;P&gt;uri /rest/alert/2&lt;/P&gt;&lt;P&gt;alertstate cleared&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;or it will be&lt;/P&gt;&lt;P&gt;some problem AAA&lt;/P&gt;&lt;P&gt;uri /rest/alert/4&lt;/P&gt;&lt;P&gt;alertstate cleared&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2020 10:46:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/lifecycle-of-a-oneview-alert/m-p/7103885#M391</guid>
      <dc:creator>placka</dc:creator>
      <dc:date>2020-10-06T10:46:23Z</dc:date>
    </item>
    <item>
      <title>Re: lifecycle of a oneview alert</title>
      <link>https://community.hpe.com/t5/hpe-synergy/lifecycle-of-a-oneview-alert/m-p/7103964#M392</link>
      <description>&lt;P&gt;The state of the alert does not change the URI of the alert.&amp;nbsp; If there is an external source that is indicating the change of state, a new alert would be generated to indicate the status of that external resource has changed, and the correlated alert is cleared.&amp;nbsp; This is mostly when there is a physical problem with a server.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2020 14:20:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/lifecycle-of-a-oneview-alert/m-p/7103964#M392</guid>
      <dc:creator>ChrisLynch</dc:creator>
      <dc:date>2020-10-06T14:20:25Z</dc:date>
    </item>
  </channel>
</rss>

