chore(hybridcloud) Reduce logging level in pagerduty alert rule action
diff --git a/src/sentry/integrations/pagerduty/actions/notification.py b/src/sentry/integrations/pagerduty/actions/notification.py
index 35184e617ebae..a0d84782e880d 100644
--- a/src/sentry/integrations/pagerduty/actions/notification.py
+++ b/src/sentry/integrations/pagerduty/actions/notification.py
@@ -41,14 +41,19 @@ def _get_service(self):
 
     def after(self, event, state, notification_uuid: Optional[str] = None):
         integration = self.get_integration()
+        log_context = {
+            "organization_id": self.project.organization_id,
+            "integration_id": self.get_option("account"),
+            "service": self.get_option("service"),
+        }
         if not integration:
             # integration removed but rule still exists
-            logger.error("Integration removed, however, the rule still refers to it.")
+            logger.info("pagerduty.org_integration_missing", extra=log_context)
             return
 
         service = self._get_service()
         if not service:
-            logger.error("The PagerDuty service does not exist anymore while integration does.")
+            logger.info("pagerduty.service_missing", extra=log_context)
             return
 
         def send_notification(event, futures):

Previously alert rules that were missing an integration would log at ERROR. However, there isn't anything we can do about these most of the time because the source of the problem is customers removing integrations. Reducing the logging level to info will give us enough context to figure out why an alert isn't triggering should a customer ask.

Fixes SENTRY-19CK