Add better screenshot examples

kubeshop · May 15, 2024 · 6a991ce · 6a991ce
1 parent 63f37b9
commit 6a991ce
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 0 deletions.
diff --git a/docs/installation/pagerduty/assets/pager_duty_app_alert_and_changes.png b/docs/installation/pagerduty/assets/pager_duty_app_alert_and_changes.png
diff --git a/docs/installation/pagerduty/assets/pager_duty_app_changes.png b/docs/installation/pagerduty/assets/pager_duty_app_changes.png
diff --git a/docs/installation/pagerduty/index.md b/docs/installation/pagerduty/index.md
@@ -80,6 +80,8 @@ Go back to the Botkube Cloud instance creation.
 
 From now on, all events emitted by enabled sources are routed directly to created PagerDuty service using the [Events API v2](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTgw-events-api-v2-overview). Botkube follows the best practices by recognizing different event types and sending them to PagerDuty accordingly.
 
+![pager_duty_app_alert_and_changes.png](assets/pager_duty_app_alert_and_changes.png)
+
 ### Alerts
 
 An [alert](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTgx-send-an-alert-event) indicates a problem within a monitored system. Botkube forwards the following types of alerts to PagerDuty: