When will the 'ci.change.unplanned' event will be triggered?

Swathi14
Tera Contributor

Hi Team,

 

I have a requirement to send notification whenever a unscheduled change happens on CI.

 

Below is the scenario : whenever I am change a CPU count(field on server) on a CI and it is outside the change window, this should trigger a notification. So to achieve this we have enabled the unauthorized change property and upon enabling events are getting generated and emergency change are getting created, which is OOB. For my senario I want to understand when and how is this event getting generated from, so that I can create a notification when there is change in CPU count.

 

Thanks in advance.

4 REPLIES 4

Community Alums
Not applicable

Hi @Swathi14 ,

An unauthorized change request is created when an unplanned CI change activity occurs, and the system triggers the following checks:
  • The system checks to see if the CI is part of the allowed CI classes. If it is allowed, then the system checks to see if this specific CI has been flagged previously. If it was flagged and the previously created unauthorized change was within the notification ignore period, then no further action is taken. If not, then further checks are made to see whether this CI is associated to a change request that matches the condition stated in the properties. If not, then the change to the CI that was detected is flagged as unauthorized and a ci.change.unplanned event is raised.
  • On receipt of the ci.change.unplanned event, the script checks to see if the Enable event processing field is true. If it is true, then an unauthorized change request is created. By default, this property is false.

The ci.change.unplanned event that is generated automatically triggers the creation of an Emergency type change request.

With the help of the following details that are pre-populated on the form, you can identify and review the unauthorized change:
  • The Unauthorized option is selected. This option indicates that the change is an unauthorized change.
  • The Assignment group field is populated with Change Management.
  • The Configuration item field is populated with the item that the unauthorized change was made for.
  • The Description field is populated with the information on the changed fields of the change request.

 

Hi Sandeep, 

 

Thanks for the quick and detailed response, now I understood what happens when event is triggered. I want to know from where and how these events are getting generated from? 

I would like to know this trigger as well for testing purposes. 

Hi Swathi,

 

Were you able to get the table name for generated events or from where and how these events are getting generated from? I have implemented same unauthorized change request but looking further in deep to implement notification and some other details so can control and decide where to raise change or not.

 

Thanks,

Ashroba