code: def backend_notification(self, event=None, parameters=None):
          
          # request_parameters = cherrypy.request.json
          # event = request_parameters.get('event', event)
          # parameters = request_parameters.get('parameters', parameters)
          if event is None:
              data = cherrypy.request.json
              event = data.get('event', None)
          if parameters is None:
              data = cherrypy.request.json
              parameters = data.get('parameters', None)
  
          logger.warning("I got a backend notification: %s / %s", event, parameters)
  
          # For a configuration reload event...
          if event in ['creation', 'deletion']:
              # If I'm the master, ignore the command and raise a log
              if not self.app.is_master:
                  message = u"I received a request to reload the monitored configuration. " \
                            u"I am not the Master arbiter, I ignore and continue to run."
                  logger.warning(message)
                  return {'_status': u'ERR', '_message': message}
  
              message = "I received a request to reload the monitored configuration."
              if self.app.loading_configuration:
                  message += "I am still reloading the monitored configuration ;)"
              logger.warning(message)
  
              self.app.need_config_reload = True
              return {'_status': u'OK', '_message': message}
  
          return {'_status': u'OK', '_message': u"No action to do"}
docs: The Alignak backend raises an event to the Alignak arbiter
          -----
          Possible events are:
          - creation, for a realm or an host creation
          - deletion, for a realm or an host deletion
  
          Calls the reload configuration function if event is creation or deletion
  
          Else, nothing for the moment!
  
          In case of any error, this function returns an object containing some properties:
          '_status': 'ERR' because of the error
          `_message`: some more explanations about the error
  
          The `_status` field is 'OK' with an according `_message` to explain what the Arbiter
          will do depending upon the notification.
  
          :return: dict