Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixes incorrect internal link #177256

Merged
merged 2 commits into from
Mar 19, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/management/connectors/action-types/pagerduty.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ The PagerDuty connector enables you to trigger, acknowledge, and resolve PagerDu
In particular, it uses the https://v2.developer.pagerduty.com/docs/events-api-v2[v2 Events API].

To create this connector, you must have a valid PagerDuty integration key.
For configuration tips, refer to <<configuring-opsgenie>>
For configuration tips, refer to <<configuring-pagerduty>>

[float]
[[define-pagerduty-ui]]
Expand Down Expand Up @@ -129,7 +129,7 @@ For more details on these properties, see https://v2.developer.pagerduty.com/v2/
Use the <<action-settings, Action configuration settings>> to customize connector networking configurations, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use `xpack.actions.customHostSettings` to set per-host configurations.

[float]
[[pagerduty-benefits]]
[[configuring-pagerduty]]
=== Configure PagerDuty

By integrating PagerDuty with rules, you can:
Expand Down