RE: Manually creating OEM Incident?

  • From: "Herring, David" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "HerringD" for DMARC)
  • To: "COURTNEY.LLAMAS@xxxxxxxxxx" <COURTNEY.LLAMAS@xxxxxxxxxx>, "dmarc-noreply@xxxxxxxxxxxxx" <dmarc-noreply@xxxxxxxxxxxxx>
  • Date: Fri, 6 Sep 2019 21:53:13 +0000

Courtney,

I definitely appreciate all the info.

Incident creation off existing Event - Yup, I thought of this but what I was 
looking for is something a little less manual and not involved steps down 
through a GUI.  Plus I need an Event first.

Event publish via "emcli" -  I guess this could be used as part of a 2-step 
process in that I generate an Event using this method, then go into the GUI and 
create an Incident off it as a test.  I could use it as an emergency where I 
wanted to get a ticket generated off certain data or a situation and have the 
ticket creation process handled programmatically after I create the Incident 
off the Event I create.

The simulation of an Incident off existing rules has always been a nice feature 
but, as you pointed out, nothing gets created.  In one of the situations I 
mentioned, we should have had a critical alert raised on DBDATA being above 95% 
full, which would have eventually sent a ticket off to our out-sourced system 
DBA team.  Once I found that we had a hole in our Incident Rules I wanted to 
force a re-evaluation, then thought about forcing an Incident to be created, 
then just manually created a ticket in CASD due to the emergency.

Regards,

Dave

[cid:image001.png@01D05044.5C2AEE60]

Dave Herring
DBA
103 JFK Parkway
Short Hills, New Jersey  07078
Mobile 630.441.4404

dnb.com<http://www.dnb.com/>

[cid:image002.png@01D05044.5C2AEE60]<http://www.facebook.com/DunBradstreet>[cid:image003.png@01D05044.5C2AEE60]<http://twitter.com/dnbus>[cid:image004.png@01D05044.5C2AEE60]<http://www.linkedin.com/company/dun-&-bradstreet>[cid:image005.png@01D05044.5C2AEE60]<http://www.youtube.com/user/DunandBrad>

From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf 
Of Courtney Llamas
Sent: Friday, September 6, 2019 3:46 PM
To: dmarc-noreply@xxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
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.

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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.oracle.com%2Fen%2Fenterprise-manager%2Fcloud-control%2Fenterprise-manager-cloud-control%2F13.3.1%2Femadm%2Fusing-incident-management.html%23GUID-F8CA7018-DEBB-4CBD-8F57-4E9A77E1729C&data=02%7C01%7Cherringd%40dnb.com%7C8a3f2bdd422648ffdc9e08d7330b5d34%7C19e2b708bf12437597198dec42771b3e%7C0%7C0%7C637033996207211897&sdata=XUnVn8L2IZrhuYTQQ3A2dP2g%2BZbOpYyA%2BYxxoi3UO9E%3D&reserved=0>

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:

  1.  Using an available view, find the event of interest.

  1.  Select the event in the table.

  1.  From the More... drop-down menu, choose Create Incident...

  1.  Enter the incident details and click OK.

  1.  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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.oracle.com%2Fen%2Fenterprise-manager%2Fcloud-control%2Fenterprise-manager-cloud-control%2F13.3.1%2Femadm%2Fusing-incident-management.html%23GUID-98AA06D1-C274-47C0-BB1B-B8EA18B08DB7&data=02%7C01%7Cherringd%40dnb.com%7C8a3f2bdd422648ffdc9e08d7330b5d34%7C19e2b708bf12437597198dec42771b3e%7C0%7C0%7C637033996207221899&sdata=BmdZUFuBfnjHktzx0T6sJ20M%2B50ftgRN80lX9DyPN3M%3D&reserved=0>


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:
[cid:image006.png@01D564D1.C12BE700]

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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.oracle.com%2Fen%2Fenterprise-manager%2Fcloud-control%2Fenterprise-manager-cloud-control%2F13.3.1%2Femadm%2Fusing-incident-management.html%23GUID-D28D8C54-46B9-4A54-8FD6-996965275522&data=02%7C01%7Cherringd%40dnb.com%7C8a3f2bdd422648ffdc9e08d7330b5d34%7C19e2b708bf12437597198dec42771b3e%7C0%7C0%7C637033996207221899&sdata=x4QI0PDp3L%2BjffpAzSDVfs5kIDl2UvIsFnpavdBq9VI%3D&reserved=0>


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@xxxxxxxxxxxxx<mailto:dmarc-noreply@xxxxxxxxxxxxx>> 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://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dnb.com%2F&data=02%7C01%7Cherringd%40dnb.com%7C8a3f2bdd422648ffdc9e08d7330b5d34%7C19e2b708bf12437597198dec42771b3e%7C0%7C0%7C637033996207231893&sdata=vyEI7DU91jJ%2FUZHvk3vOvp8qiA6PrwHHEucfR705x%2Bw%3D&reserved=0>

<image002.png><https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.facebook.com%2FDunBradstreet&data=02%7C01%7Cherringd%40dnb.com%7C8a3f2bdd422648ffdc9e08d7330b5d34%7C19e2b708bf12437597198dec42771b3e%7C0%7C0%7C637033996207231893&sdata=dfnbDQSY0yrp3k7O%2FN04frNdIACoQ2FMu3vVCQO80iA%3D&reserved=0><image003.png><https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fdnbus&data=02%7C01%7Cherringd%40dnb.com%7C8a3f2bdd422648ffdc9e08d7330b5d34%7C19e2b708bf12437597198dec42771b3e%7C0%7C0%7C637033996207241884&sdata=i3hgCg5M6pLOGA%2FyHwC%2Bupv3jkvh%2BymutaIw9ALFpUU%3D&reserved=0><image004.png><https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fdun-%26-bradstreet&data=02%7C01%7Cherringd%40dnb.com%7C8a3f2bdd422648ffdc9e08d7330b5d34%7C19e2b708bf12437597198dec42771b3e%7C0%7C0%7C637033996207241884&sdata=1hiGouJITaPnxmBtb044Rm5AA1BcqqvBnYa5506kiDg%3D&reserved=0><image005.png><https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.youtube.com%2Fuser%2FDunandBrad&data=02%7C01%7Cherringd%40dnb.com%7C8a3f2bdd422648ffdc9e08d7330b5d34%7C19e2b708bf12437597198dec42771b3e%7C0%7C0%7C637033996207241884&sdata=qOMZPOVKUghkqu9QcN%2BcMYISUnMpQUlsOQ26dKwbf5g%3D&reserved=0>

From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx> 
<oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>> On Behalf 
Of Courtney Llamas
Sent: Friday, September 6, 2019 11:52 AM
To: dmarc-noreply@xxxxxxxxxxxxx<mailto:dmarc-noreply@xxxxxxxxxxxxx>
Cc: oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>
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@xxxxxxxxxxxxx<mailto:dmarc-noreply@xxxxxxxxxxxxx>> 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

PNG image

PNG image

PNG image

PNG image

PNG image

PNG image

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 09-2019