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
103 JFK Parkway
Short Hills, New Jersey 07078
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Courtney Llamas
Sent: Friday, September 6, 2019 11:52 AM
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
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
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 220.127.116.11 / 5.