Re: Manually creating OEM Incident?

There is a way to manually create an incident based on an alert. But I’m not sure that would have triggered any notification or actions… will have to test that. https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.3.1/emadm/using-incident-management.html#GUID-F8CA7018-DEBB-4CBD-8F57-4E9A77E1729C <https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.3.1/emadm/using-incident-management.html#GUID-F8CA7018-DEBB-4CBD-8F57-4E9A77E1729C>

Creating an Incident Manually

If an event of interest occurs that is not covered by any rule and you want to convert that event to an incident, perform the following:

Using an available view, find the event of interest. Select the event in the table.
From the More... drop-down menu, choose Create Incident... Enter the incident details and click OK. Should you decide to work on the incident, set yourself as owner of the incident and update status to Work in Progress.

You can also create an event manually with EMCLI - meant for user reported, but this still wouldn’t trigger notifications/ticket creation unless that event type/target type is included in the rules... https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.3.1/emadm/using-incident-management.html#GUID-98AA06D1-C274-47C0-BB1B-B8EA18B08DB7 <https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.3.1/emadm/using-incident-management.html#GUID-98AA06D1-C274-47C0-BB1B-B8EA18B08DB7>

Really, you should have a rule that creates an incident and triggers notification of some sort for any critical alert (at least). The OOB ruleset has an example of this:

I also recommend using the Events without Incidents out of box View in Incident Manager, to track anything falling thru the cracks.

For testing, we do have a way to simulate alerts, but I don’t think that will actually create the ticket in CASD, it was meant as a way to test w/o actually triggering the actions but just to verify them. The best way to test is to actually change a threshold - I like archive dest personally, or table space. https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.3.1/emadm/using-incident-management.html#GUID-D28D8C54-46B9-4A54-8FD6-996965275522 <https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.3.1/emadm/using-incident-management.html#GUID-D28D8C54-46B9-4A54-8FD6-996965275522>

Hope this helps! I’ll try to play around w/ the create event when I get some time after OOW! ;)

> On Sep 6, 2019, at 12:51 PM, Herring, David <dmarc-noreply_at_freelists.org> wrote:
>
> Sure. Recently I found a non-clustered env had reached 98% full on DBDATA but we didn't get an alert. Turns out our Incident Rule for space alerts was set only for ASM Cluster vs. ASM Instance. It got overlooked because we only have a handful of non-clustered envs. I updated our ASM Instance Incident Rule to include space metrics but I would have loved at that point to quickly create an Incident concerning space to force that Incident Rule to trigger an alert and consequently a ticket being raised on CA Service Desk (CASD).
>
> Another example is with testing a bridge we have from CASD to a 3rd party company's ticketing system. I'd love to issue a command to have an Incident created to test the whole process at any time. I know the CASD Connector has the ability to run a test but that's a "getTicket" whereas I'd like the whole process tested. Currently I have a little script to push a mountpoint above the warning threshold, then drop the temp files. A real hack that is kind of risky.
>
> Regards,
>
> Dave
>
> <image001.png>
>
> Dave Herring
> DBA
> 103 JFK Parkway
> Short Hills, New Jersey 07078
> Mobile 630.441.4404
>
> dnb.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.dnb.com_&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=e2ySKFbZtsbLGCPPnk-bGxynIXvLeakw9ckTe3VmQgY&m=0nMHzgaGoFGrKSx4ePLsLMzSelF0xG9jul-NaG7jKvk&s=O1RdftKiAJ6fLdvgN43MOvfaJm3nZ-7UqrTJFr9YipQ&e=>
>
> <image002.png> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_DunBradstreet&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=e2ySKFbZtsbLGCPPnk-bGxynIXvLeakw9ckTe3VmQgY&m=0nMHzgaGoFGrKSx4ePLsLMzSelF0xG9jul-NaG7jKvk&s=gllaYYoff1Ae0i2IonQ_a8js6aLJlAsHE1adKhrqP1U&e=><image003.png> <https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_dnbus&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=e2ySKFbZtsbLGCPPnk-bGxynIXvLeakw9ckTe3VmQgY&m=0nMHzgaGoFGrKSx4ePLsLMzSelF0xG9jul-NaG7jKvk&s=O2BS17Cl0bFnp5xXLSzdE15Uj5XMvHDq4qDd1d2Gu6U&e=><image004.png> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_dun-2D-26-2Dbradstreet&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=e2ySKFbZtsbLGCPPnk-bGxynIXvLeakw9ckTe3VmQgY&m=0nMHzgaGoFGrKSx4ePLsLMzSelF0xG9jul-NaG7jKvk&s=7FW1vZolk5S-yf4a-scfmGWN_SyodTgtzVaKtUfJy88&e=><image005.png> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_user_DunandBrad&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=e2ySKFbZtsbLGCPPnk-bGxynIXvLeakw9ckTe3VmQgY&m=0nMHzgaGoFGrKSx4ePLsLMzSelF0xG9jul-NaG7jKvk&s=lbLRu8yEol2Hzr9HzcPNLJUB0xGo0S76LMUuekTSlHw&e=>
>
> From: oracle-l-bounce_at_freelists.org <mailto:oracle-l-bounce_at_freelists.org> <oracle-l-bounce_at_freelists.org <mailto:oracle-l-bounce_at_freelists.org>> On Behalf Of Courtney Llamas
> Sent: Friday, September 6, 2019 11:52 AM
> To: dmarc-noreply_at_freelists.org <mailto:dmarc-noreply_at_freelists.org>
> Cc: oracle-l_at_freelists.org <mailto:oracle-l_at_freelists.org>
> Subject: Re: Manually creating OEM Incident?
>
> CAUTION: This email originated from outside of D&B. Please do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> hmm… can you give me a little background on what you’re trying to do?
>
>
> On Sep 6, 2019, at 11:49 AM, Herring, David <dmarc-noreply_at_freelists.org <mailto:dmarc-noreply_at_freelists.org>> wrote:
>
> Folks, does anyone know if there's a way to manually / programmatically create an OEM Incident outside of the console? I was hoping that "emcli" would have something like that. It has " delete_incident_record" and "clear_problem" but nothing for creating / raising an Incident.
>
> This is for OEM 12.1.0.4 / 5.
>
> Thx.
>
> Dave

--
http://www.freelists.org/webpage/oracle-l