Reason for Moderation

2. Re: Setup SLO Objects (V12.1)

Are you having issues opening the object? It may be displaying in a different perspective (such as Administration) - once you have the object opened, setting up SLOs is fairly straightforward. You'll select whether to have the SLO active/monitored (and when to do so), along with time zones if applicable.

Once these have been configured, the next section (Service Selection) allows you to add objects/criterion to monitor. The section "FulFillment Criteria" directly underneath allows you to specify "Runs shorter than/longer than MRT," or the job ending in a specific status for actions. Actions can be set up to react on fulfillment or on violation, and respond in a particular method based on the requirements that are being monitored.

One thing to keep in mind is that, at this point, SLO objects are not able to effectively monitor tasks which cross midnight. For example:

*JOB_A starts at 11:30pm, and normally runs until 12:30am.

*There are two SLO Objects monitoring JOB_A - one for a late execution at 12:45am, and another for extreme delay notification at 1:00am.

*JOB_A ends at 12:47, which should trigger the first SLO (but not the second) for violation.

*Both SLO Objects violate.

This is noted on Community, and we have a request to vote for this functionality to be included in a future release (which may be accomplished via the link below):

Are you having issues opening the object? It may be displaying in a different perspective (such as Administration) - once you have the object opened, setting up SLOs is fairly straightforward. You'll select whether to have the SLO active/monitored (and when to do so), along with time zones if applicable.

Once these have been configured, the next section (Service Selection) allows you to add objects/criterion to monitor. The section "FulFillment Criteria" directly underneath allows you to specify "Runs shorter than/longer than MRT," or the job ending in a specific status for actions. Actions can be set up to react on fulfillment or on violation, and respond in a particular method based on the requirements that are being monitored.

One thing to keep in mind is that, at this point, SLO objects are not able to effectively monitor tasks which cross midnight. For example:

*JOB_A starts at 11:30pm, and normally runs until 12:30am.

*There are two SLO Objects monitoring JOB_A - one for a late execution at 12:45am, and another for extreme delay notification at 1:00am.

*JOB_A ends at 12:47, which should trigger the first SLO (but not the second) for violation.

*Both SLO Objects violate.

This is noted on Community, and we have a request to vote for this functionality to be included in a future release (which may be accomplished via the link below):

Are you having issues opening the object? It may be displaying in a different perspective (such as Administration) - once you have the object opened, setting up SLOs is fairly straightforward. You'll select whether to have the SLO active/monitored (and when to do so), along with time zones if applicable.

Once these have been configured, the next section (Service Selection) allows you to add objects/criterion to monitor. The section "FulFillment Criteria" directly underneath allows you to specify "Runs shorter than/longer than MRT," or the job ending in a specific status for actions. Actions can be set up to react on fulfillment or on violation, and respond in a particular method based on the requirements that are being monitored.

One thing to keep in mind is that, at this point, SLO objects are not able to effectively monitor tasks which cross midnight. For example:

*JOB_A starts at 11:30pm, and normally runs until 12:30am.

*There are two SLO Objects monitoring JOB_A - one for a late execution at 12:45am, and another for extreme delay notification at 1:00am.

*JOB_A ends at 12:47, which should trigger the first SLO (but not the second) for violation.

*Both SLO Objects violate.

This is noted on Community, and we have a request to vote for this functionality to be included in a future release (which may be accomplished via the link below):

Reason for Moderation

6. Re: Setup SLO Objects (V12.1)

Glad to help! To attach the SLO to an object for monitoring, that can be done in the Service Selection section (under the main Service Level Objective tab). Within, there should be the option labelled, 'Add Criterion.' Select this, and the option to choose the object name to monitor should appear, allowing for definition of the parameter.

9. Re: Setup SLO Objects (V12.1)

This sounds a bit more complex, and/or like a notification that you have had previously set up is not working as expected. In either case, it would likely be best to open a ticket with Support so that your needs and requirements are fully addressed. There are many reasons why this may not be working (from configuration to an actual issue, and anything between that), so I want to ensure you have all the tools you need to diagnose this effectively.

Reason for Moderation

Describe the reason this content should be moderated (required)

10. Re: Setup SLO Objects (V12.1)

Am I in the right direction? I mean like I setup the SLO Object and put the mail id to get notification from the SLO Object and I enabled that SLO Object and when the condition get violated, we get notification. So, that's how it works right ?