SLA Voilation Alert

Hi all,
I setup SLA and after creating activity I can see SLA & reminder timings, when it reached reminder time SLA icon turn in to yellow from green.
But I canu2019t get the Violation Alert u2013 alert profile is activated and also ran the program RPEIC_SLA_ALERTS and it got message on screen saying that 5 entries have been moved into THREIC_SLA_ALRT but when I checked in the table but no entries found
Personal reminder - I created personal reminder when it due to alert I am getting error msg in broadcasting area saying 'unable to deliver the msg'?
Did I miss something here? Any help?
thanks,
R

Hi Jarret,
As you requested here I am giving steps that I followed.
I followed below steps
1)     Defined alert profiles Alert ID HREIC_VOLATION
Class- CL_CRM_IC_ALERT_GENRIC
Navigation link u2013 ToActivityDetailsFromAlert
Description: violation
Message: Activity [param1] passed the due date [param2]
Tooltip: Go To Alert View
2)     Defined alert profiles Alert ID HREIC_REMINDER
Class- CL_CRM_IC_ALERT_GENRIC
Navigation link u2013 ToalertviewfromAlert
Description: reminder
Message: The due date [param1]for activity [parm2] approching
Tooltip: Go To Alert View
3)     Maintain constants(Table: v_hreic_constant) : ALRTREMIED - HREIC_REMINDER
                                                                           ALRTVIOLAT - HREIC_VOILATION
4)     The program RPEIC_SLA_ALERTS reads the activity table THREIC_ACTIVITY and records those activities that need to have alerts sent to them in the alert table THREIC_SLA_ALRTS (Activities Selected by SLA Alert Program). (for testing after creating activity (assume sla in place) then run the above program then only you can get alerts in production systems we will schedule it back ground on your requirement.
Hope this helps.
Ravi

Similar Messages

Need Help:Regarding Case when we should receive an email if we haven't receive feed within SLA.

Hello Cisco Team/Everyone,
We are facing one major hurdle we need to configure a case when a email should be sent to business if the feed is not received within SLA.
At present what we can configure is if feed is being received within SLA then an email will be sent informing about the timely delievery of feed and if we receive feed after SLA then also an email will be sent to business informing that feed received late but if we haven't received the feed within SLA then please let us know how to configure Email Action ? ( informing that we haven't received the feed within SLA )
Thanks.

You have muliple solutions so we probably need more details
At a mininum you would want 2 different email events with different triggers and 2 different email actions
You may or may not have 2 different jobs
How we decided to handle:
We decided to create and ALERT Job Group for our SLA notifications/alerts
   (you can make it its own parent or integreate with another Job Group depeending on what makes sense to you)
We organized the next level by time windows in military time
Alert\
\0000_0259 <-- alerts that trigger between midnight and 3am (they line up top to bottom that way and visually progress)
If this is a file based alert you create a dependecy on the file not existing
Next put a Time Window on it lets say start at 12:15am and end at 1:00 am
Here's the counter intuitive part:
You create an event to send an email to business on job completed normally that the SLA was breached
          if the file didn't exist by 1am then this executes and completes normally
          We use powershell to write-output of text we want to send for that particular business unit
          We use in email action
You create an event to skip the job if job not ready by the end of its time window
          if the file existed then the depdendcy is not statisfied and job essentailly is not ready by end of time window 1am
          Operations teams consider "skipped" a "OK" status since we do it on purpose
Other options
You could also use exit codes to do similar things, if your process that is evaluating the SLA is produce different exit codes, Then you can apply different events to the exit codes
Hope that helps!
Marc

Cisco Unified Operations Manager v Cisco Service Monitor

I am unfamiliar with both od these products. Both seem to overlap in that they seem to aim for end to end voice quality management, relying on the 1040 probe.
Am I off base here? Are they similar products, one or both maybe OEM'd???
Are they widely deployed?
Any thoughts welcome.
Regards

Hi Gordon,
They are very much complimentary. In fact, installing OM used to install SM by default on same box.
OM doesn't collect info from the 1040 probes. SM does this, and then alerts to OM if thresholds are breached.
OM will then display the alert.
Operations Manager is very much about actively monitoring the health of the UC environment. Here's a couple of practical examples of what it does:
- Maps out a logical view of the environment
- Performs scheduled tests - checks CM reg, dial tone, TFTP
- Simulates calls with both synthetic phones and even real phones
- Interactive tests - check phone features are working etc
- Performance management - view utilisation of GW's CM's etc.
- IP SLA - simulated calls, jitter testing across the network using routers / switches and IP SLA features
- Alert monitoring - dashboard view
Service Monitor is very focussed on measuring the actual user experience of calls.
- It can use CDR / CMR records (with no 1040 HW sensors deployed) to record, and monitor the quality of individual calls
- It can also use the 1040 HW sensors to collect more granular call quality details.. (it sends the details to SM via syslog constantly)
- Report and alert on call quality based on thresholds (Alerts are sent to OM and appear in your alerts window)
The only real overlap I would say is that OM does some quality tests with IP SLA, but it is based on synthetic calls rather than working with data about real calls.
There is also another module, Unified Service Statistics Monitor, I'd recommend looking at this too, it provides the historical component, and also a variety of different reporting - including service levels and executive style dashboards.
I've done a few deployments. Standard network management principles apply, and I think this is where a lot of them fall down. No product can manage your network for you automatically, the biggest part is people and process. Once you have this in place you can definitely use products like OM, SM to automate and simplify.
The larger and more complex your network, the more valuable and useful these products can become.
My recommendation is to get the eval copy, and try them out. You do need to think carefully about what you want to achieve though, without this step, an install of these products probably won't impress. The art is all about the setup.
Cheers,
Tim

Roaming Fraud in Telecoms and High-Usage Reporting standards

Hi,
I am sure that there are people out there performing software development on telecoms systems to process high usage reports in order to reduce roaming fraud. I am hoping that someone can point me at a forum they may use so that I may join them to exchange
information.
Can anyone help please?
Many thanks in advance.
Terry

Kai,
Thanks for the question (and input). As you probably know, we have several partners that provide WLP-ready monitoring solutions providing insight into the utilization, availability, and performance of portal components, including Acsera, Quest, Intersperse, and Wily. In general, these tools are sophisticated and powerful, providing features such as SLA management, alerting, and drill down capability to meet the needs of operational, support, and development personnel tasked with detecting, isolating, and diagnosing performance and availability related issues.
In addition, we recognize the need to provide business users with straightforward statistics on utilization and performance. While we do not plan on providing such capabilities out of the box for the 9.2 release, we are actively investigating the possibility of leveraging the Analytics component of ALUI to provide such reporting capabilities for Weblogic Portal in the future.
If you'd like to know more about ALUI Analytics, visit http://www.plumtree.com/products/analytics/default.htm
Ken

SLA Alerts in DB polling proxy

Hi
I have created a DBAdapter to poll a table in the database for any inserts/updates. Have adopted the Logical Delete processing.
Now I need to configure an SLA alert for the proxy service based on this DBAdapter.
The alert needs to be raised when no records have been updated/inserted for more than say 10 minutes.
The SLA Alert Rule I have defined is as follows:
Rule Name   TriggerAlert
Alert Destination   Poll_SLA/SLAQueue
Start Time (H:MM)   3:00 AM
End time (H:MM)   1:30 PM
Rule Expiration Date (M/D/YYYY)   12/31/2011
Rule Enabled   true
Alert Severity   Critical
Alert Frequency   Every Time
Stop Processing More Rules   true
Conditions
Condition Expression   Aggregation Interval 0 Hour(s) and 5 Minutes
Operation.receive.Message Count = 0
But somehow the SLA Alert is not raised even if there are no inserts or updates for 5 minutes. The proxy service is polling the records correctly as I can see the log actions being executed.
Could someone help me in pointing out the configuration that I have missed or have wrongly done asap.
Thanks & Regards
Kshama
Edited by: Kshama Tamhankar on Dec 20, 2011 9:30 PM

Hi,
I changed the Alert rule to Message Count=0 and the main setting that I had to change to raise the alert was in the Operational Settings tab of the Proxy service.
Monitoring: Enabled Pipeline Monitoring for Service Level and above. By default this is set as Pipeline Level.
Thanks & Regards
Kshama

IP SLA Alert

Hi,
I have configured IP SLA to monitor the remote peer ip address sucessfully with icmp. Below is the configuration :-
ip sla 1
icmp-echo 192.168.10.1 source-interface Loopback1
timeout 1000
threshold 2
frequency 3
ip sla schedule 1 life forever start-time now
track 101 ip sla 1 reachability
IP SLA works fine. Now i want configure IP SLA in such a way that the failover happens only if there are 5 to 10 timeouts on the link and in such case there should be an alert generated via logging or snmp. Can any one help on this?

Hi Maxson,
Yes, its possible to configure the failover in such a way that it will happen only if there are 5 to 10 min timeouts on the link.
For this you have to define the track command and also defined the delay up time and down time. This delay up and delay down is the settings that will wait upto specific time before making changeover happen that will provide stability to your track and it will save the failover from flapping too much if there are slightly one or 2 ip sla operations failed event will expected in network.
So for example under track 101 ip sla 1 reachability command --> you can define delay up 3 down 10
This wlll change the failover happen only when the operation keep up for 3 seconds and and also make the failover happen when the ip sla operation will remain down for 10 seconds.
For more information and options, here is the reference guide for the same :-
http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_eot.html#wp1055209
Now the next part is to get an alert for the failover happen, you can configure trap like this
ip sla reaction-configuration 1 react timeout threshold-type immediate action-type trapOnly
The above command will generate the trap the moment threshold had been exceeded. There had been lot more trap that you can configure as per the requirements, kindly have a look at this nice document here :-
Configuring Proactive Threshold Monitoring of IP SLAs Operations
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/sla_threshold_mon.html
Many Thanks,
Gaganjeet Singh

IP SLA and Tracking for alerting

Hi,
I configured IP SLAs for sites that connect to the Internet via a 2911 router
Config:
ip sla 199
icmp-echo 4.2.2.2 source-interface GigabitEthernet0/2
ip sla schedule 199 life forever start-time now
ip sla logging traps
track 199 ip sla 199
delay down 120 up 120
Works great - sends a syslog message to the Solarwinds box and message sets off an email alert.
We have a couple of smaller sites that connect to the Internet via a 5510. I'm trying to accomplish the same thing but, it doesn't seem to have the options to set a "delay down and delay up"
Below seems to be my only option:
"track 199 rtr 199 reachability"
Will this tracking-config log the ping fail and if so, is there a way to delay the logging for 120 secs - for Up and Down events?
Thanks, Pat

Hello Pat,
Have you tried entering the command "track 199 rtr 199 reachability"
The prompt should look like this after:
Router(config-track)#
Here you should be able to enter the command "delay down 120 up 120" to my recollection.

EEM- Email alert with IP SLA Based on Packet Loss

hi joseph,
i need your advise, i want to get alert email based on IP SLA Packet loss
the scenarion as below :
1. If the traffic hit threshold packet loss greater than 20% as long 15 minutes --> send email
2. If reset condition packet loss eq 0% as long 15 minutes --> send email again
I don't know how to configure it condition. could you help me to verify my configuration below?
ip sla logging traps
ip sla 1
icmp-jitter 10.216.0.105 source-ip 10.216.0.107 num-packets 100 interval 40
frequency 50
ip sla schedule 1 life forever start-time now
ip sla reaction-configuration 1 react Packetloss threshold-value 3 1 threshold-type immediate action-type trapOnly
ip sla enable reaction-alerts
event manager applet TEST
event syslog pattern "IP SLAs$1$: Threshold exceeded"
action 2.0 mail server "10.240.0.10" to "[email protected]" from "[email protected]" subject "Alert for Intermittent Link" body "link intermittent in x %"
thank you

What's you have could work with a few modifications. First, increase that threshold-value of 3 to 20. You can leave the falling threshold value of 1. You'll need to add another applet to match the falling threshold syslog message. Not sure exactly what that one will look like.
The first applet will look like this:
event manager environment q "
event manager applet ipsla-threshold-exceeded
event syslog pattern "IP SLAs$1$: Threshold exceeded"
action 001 cli command "enable"
action 002 cli command "config t"
action 003 cli command "no event manager applet ipsla-healthy"
action 004 cli command "event manager applet ipsla-unhealthy"
action 005 cli command "event timer countdown time 900"
action 006 cli command "action 1.0 mail server $q 10.240.0.10$q to $q [email protected]$q from $q [email protected]$q subject $q Alert for Intermittent Link$q body $q link intermittent in 20 %$q"
action 007 cli command "action 2.0 cli command enable"
action 008 cli command "action 3.0 cli command $q config t$q"
action 009 cli command "action 4.0 cli command $q no event manager applet ipsla-unhealthy$q"
action 010 cli command "action 5.0 cli command end"
action 011 cli command "end"
And the second applet (the one where you'll need to fill in the appropriate syslog pattern) will look like:
event manager applet ipsla-threshold-normal
event syslog pattern "FALLING THRESHOLD PATTERN HERE"
action 001 cli command "enable"
action 002 cli command "config t"
action 003 cli command "no event manager applet ipsla-unhealthy"
action 004 cli command "event manager applet ipsla-healthy"
action 005 cli command "event timer countdown time 900"
action 006 cli command "action 1.0 mail server $q 10.240.0.10$q to $q [email protected]$q from $q [email protected]$q subject $q Link is stable$q body $q Link has been stable for 15 minutes$q"
action 007 cli command "action 2.0 cli command enable"
action 008 cli command "action 3.0 cli command $q config t$q"
action 009 cli command "action 4.0 cli command $q no event manager applet ipsla-healthy$q"
action 010 cli command "action 5.0 cli command end"
action 011 cli command "end"

OSB: API to create SLA alert on proxy

Hi,
does anyone know how to set an SLA alert for a large number of proxy services automatically ? I went through http://docs.oracle.com/cd/E21764_01/apirefs.1111/e15033/toc.htm but haven't found anything useful.
There is close to a hundred of proxies in my configuration and I need to set two SLA rules for all of them. Obviously, I don't want to do that through /sbconsole one by one. Additionally, I want to have sort of after-deploy-script to make sure that all deployed proxies have those SLA alerts set without checking anything manually.
Any idea?

Was looking at this and just realised the exact issue that is reported in this thread.
It would be really useful to have a way of executing a config file via the API to setup these SLAs.
Is there a place where I can vote for enhancements or see the release roadmap for OSB?
Many thanks
Murph

OSB - SLA Alert Details

Is it possible to include dynamic messages in the SLA alerts you can configure for Proxy Services? I would like to include the final $body contents of the alerts that are generated, but do not see a way to do it.

I dont see a way for including the $body content in the alert.
But you may consider writing the $body through a business service to a file or jms queue before invoking the alert action.

SLA alert doesn't display in the OSB console's dashboard

Greetings,
I defined several SLA alerts for a proxy service and I'm using a client which creates on the purpose the required conditions to raise the alerts, but nothing displays in the Dashboard. I also enabled the monitoring checkbox but I don't know if the level has to be pipeline, service or action. Did I miss something ?
Many thanks in advance,
Nicolas

1° Monitoring is enabled at service level.
2° The aggregation interval for the condition is the same as the monitoring one.
There is no message in the Dashboard, neither SLA Alerts nore any other one. What is very strange is that the Service Health tab says that the avg. response time is 0 seconds while the proxy service reply takes 30 seconds. The proxy service is based on a JAX-RPC WSDL generated in Workshop. I also tried JAX-RPC with the same result? The client is an Axis one generated in Workshop (not a WebLogic clientgen one) and it calls the proxy service as follows:
//JAX-RPC
TestService service = new TestServiceProxy().getTestService();
// Service will reply in 30 seconds
service.delay30();
//JAX-WS
TestService service = new TestServiceLocator().getTestServiceSoapPort();
// Service will reply in 30 seconds
service.delay30();
Once called, the operation logs a message at its begin and at its end. The message shows that the processing takes 30 seconds. The SLA alert rule says that an alert has to be raised, having the console as the destination, whenever the processing time of this operaztion invocation takes more than 5 seconds. However, no message apears in the dashboard, no SLA alert and the service's avg processing time is displayed as being 0 seconds.
Many thanks in advance for any help.
Nicolas

OSB - Creating SLA Alerts using WLST

Hi,
I'd like to create SLA Alerts on proxy services using WLST rather than via the service bus console.
The MBean described at:
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/javadoc/com/bea/wli/sb/management/configuration/ProxyServiceConfigurationMBean.html
only seem to allow enabling or disabling SLA alerts not creating them.
Can anyone point me in the right direction?
Thanks
Nick

Please refer -
http://blogs.oracle.com/MarkSmith/entry/osb_alerts_purging_is_essentia
From the blog -
The components that make up WLDF will be targeted to a single managed server in a clustered environment or to the Admin server in a single server environment. To establish what managed server this is, check to see where the WLI Aggregator application is targeted to. The WLDF data will be stored under this single managed server in the following location: //domain_name/servers/server_name/data/store/diagnostics/Check that on which server WLI Aggregator application is targeted and connect to that server from your script.
Regards,
Anuj

Configuring and using SLA alerts and Monitoring in OSB.

Hi,
I am having a business service which logically represents composite endpoint URI. Now I want to enable Monitoring and generate an SLA alert if the composite URI that the business service is representing is DOWN for some reason and the proxy routing to the BS is not able to invoke it.
How do I do that? Pls suggest!

Hi Deb,
Please refer section "46.5 How to Generate Alerts Based on Endpoint URI Status" at below link -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/endpointurimgmt.htm#i1080465
Also refer -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/monitoring_ops.htm#i1108778
Please post OSB related questions in Oracle SOA Suite forum only -
SOA Suite
Regards,
Anuj

WLST Script for Disabling/Enabling Global SLA Alerting.

Hello,
I wanna find a way from the WLST to disable and enable the SLA Alerting which is under Operations-->Global Settings in the sbconsole. This is the global setting not per sercive!
I have found how to create a session and how to disable the alerts per service, but i cannot find which MBean is accessed when throught the sbconsole the global SLA alerting is disabled/enabled.
Can anybody point me to the right direction or help me to find how to do this from WLST.
Thanks.

Hi Ganesh,
I have finally created the script i was looking for.. I copy-paste it below as a sample... For sure you need all the lines of code until the comment i have put "#####you need this code above"
now the code you see below the comment is for disabling the global sla alerting... you have to write a bit to target a specific service that you want to disable.
Keep in mind that after you make your change you hava to include those lines in order to activate the changes and disconnect and exit..
sessionMBean.activateSession(sessionName, "enable SLA")
disconnect()
exit()
If you have access to oracle support search for wlst script for osb it has a lot and you can find how to target a specific service...
I hope that i help a little bit
import sys
import wlstModule
from com.bea.wli.sb.management.configuration import SessionManagementMBean
from com.bea.wli.sb.management.configuration import ALSBConfigurationMBean
#from com.bea.wli.sb.management.configuration import ProxyServiceConfigurationMBean
from com.bea.wli.sb.management.configuration.operations import OperationsConfigMBean
from com.bea.wli.config import Ref
from com.bea.wli.sb.util import Refs
# Connect (username, password, URL)
connect('weblogic', 'password', 't3://localhost:7001')
domainRuntime()
# Create a session name
sessionName =sessionName = String("SessionScript"+Long(System.currentTimeMillis()).toString())
print('... after session. Session is: ', sessionName)
# Get the session MBean and create a session
sessionMBean = findService(SessionManagementMBean.NAME,SessionManagementMBean.TYPE)
print('-debug-this is the sessionbean',sessionMBean)
print('SessionMBean is: ', sessionMBean)
sessionMBean.createSession(sessionName)
print(String('Session was created ... ').concat(sessionName))
#####you need this code above
domainCustom()
cd('com.bea')
#path='com.bea:Name=OperationsConfig.'+sessionName+',Location=AdminServer,Type=com.bea.wli.sb.management.configuration.operations.OperationsConfigMBean'
cd('com.bea:Name=OperationsConfig.'+str(sessionName)+',Location=AdminServer,Type=com.bea.wli.sb.management.configuration.operations.OperationsConfigMBean')
set('DomainSLAAlertingEnabled',java.lang.Boolean("true"))
# Now commit (activate) the changes
sessionMBean.activateSession(sessionName, "enable SLA")
disconnect()
exit()

EEM script to alert on IP SLA failures

I have the following IP SLA set up and would like to do the following. I would like to have a log entry if any of the below have a failure and then send an email alerting to that failure. Is there a way to do this with EEM?
ip sla 1010
udp-jitter 64.xxx.xxx.xxx 3456 num-packets 30 interval 25
history hours-of-statistics-kept 24
ip sla schedule 1010 life forever start-time now
ip sla 1011
tcp-connect 64.xxx.xxx.xxx 2000
history hours-of-statistics-kept 24
ip sla schedule 1011 life forever start-time now
ip sla 1012
icmp-echo 64.xxx.xxx.xxx
frequency 30
history hours-of-statistics-kept 24
history distributions-of-statistics-kept 10
ip sla schedule 1012 life forever start-time now
Thanks,
Mike

Thanks that is very helpful. Now what about something like this?
From below I would like to alert if there is a failure (see the bold)
IP_SLA_2821#show ip sla stat 1020
IPSLAs Latest Operation Statistics
IPSLA operation id: 1020
Type of operation: udp-jitter
Latest RTT: 23 milliseconds
Latest operation start time: 14:25:34.377 EDT Fri Aug 24 2012
Latest operation return code: OK
RTT Values:
Number Of RTT: 30 RTT Min/Avg/Max: 23/23/33 milliseconds
Latency one-way time:
Number of Latency one-way Samples: 30
Source to Destination Latency one way Min/Avg/Max: 9/10/16 milliseconds
Destination to Source Latency one way Min/Avg/Max: 13/13/23 milliseconds
Jitter Time:
Number of SD Jitter Samples: 29
Number of DS Jitter Samples: 29
Source to Destination Jitter Min/Avg/Max: 0/1/6 milliseconds
Destination to Source Jitter Min/Avg/Max: 0/1/10 milliseconds
Packet Loss Values:
Loss Source to Destination: 0 Loss Destination to Source: 0
Out Of Sequence: 0 Tail Drop: 0
Packet Late Arrival: 0 Packet Skipped: 0
Voice Score Values:
Calculated Planning Impairment Factor (ICPIF): 0
Mean Opinion Score (MOS): 0
Number of successes: 33
Number of failures: 0
Operation time to live: Forever

SLA Voilation Alert

Similar Messages

Maybe you are looking for