Nagios Charm

Merge ~aluria/charm-nagios:fix/pd-docs into charm-nagios:master

  1. Git
  2. lp:~aluria/charm-nagios
  3. fix/pd-docs
  4. Merge into master
Proposed by Alvaro Uria
Status: Merged
Approved by: James Troup
Approved revision: e3a52e8c34ecab9c6ae89f1378568ea2890e9b05
Merged at revision: aeea85062541b27ead8c7f1c3679677803b904a4
Proposed branch: ~aluria/charm-nagios:fix/pd-docs
Merge into: charm-nagios:master
Diff against target: 28 lines (+10/-1)
1 file modified
README.md (+10/-1)
Reviewer Review Type Date Requested Status
🤖 prod-jenkaas-bootstack (community) continuous-integration Approve
BootStack Reviewers Pending
BootStack Reviewers Pending
Review via email: mp+416949@code.launchpad.net

Commit message

Update Pagerduty configuration details in README

To post a comment you must log in.
Revision history for this message
Alvaro Uria (aluria) wrote :

This request comes from [1].

1. https://discourse.charmhub.io/t/solved-nagios-pagerduty-anyone/5865/7

Revision history for this message
🤖 Canonical IS Merge Bot (canonical-is-mergebot) wrote :

This merge proposal is being monitored by mergebot. Change the status to Approved to merge.

Revision history for this message
🤖 prod-jenkaas-bootstack (prod-jenkaas-bootstack) wrote :

A CI job is currently in progress. A follow up comment will be added when it completes.

Revision history for this message
🤖 prod-jenkaas-bootstack (prod-jenkaas-bootstack) wrote :

PASSED: Continuous integration, rev:e3a52e8c34ecab9c6ae89f1378568ea2890e9b05
https://jenkins.canonical.com/bootstack/job/lp-charm-nagios-ci/53/
Executed test runs:
    SUCCESS: https://jenkins.canonical.com/bootstack/job/lp-charm-test-functest/688/
    None: https://jenkins.canonical.com/bootstack/job/lp-update-mp/1154/

Click here to trigger a rebuild:
https://jenkins.canonical.com/bootstack/job/lp-charm-nagios-ci/53//rebuild

review: Approve (continuous-integration)
Revision history for this message
🤖 Canonical IS Merge Bot (canonical-is-mergebot) wrote :

Change successfully merged at revision aeea85062541b27ead8c7f1c3679677803b904a4

Revision history for this message
Alvaro Uria (aluria) wrote :

This is now published in edge and will be released in stable in the coming SRU (April).

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/README.md b/README.md
2index 80d6e58..339ef45 100644
3--- a/README.md
4+++ b/README.md
5@@ -38,7 +38,7 @@ Will get you the public IP of the web interface.
6
7 - `enable_pagerduty` - Config variable to enable pagerduty notifications or not.
8
9-- `pagerduty_key` - Pagerduty API key to use for notifications
10+- `pagerduty_key` - Pagerduty Integration key to use for notifications (configured within a PD service, as "Nagios integration")
11
12 - `pagerduty_path` - Path for Pagerduty notifications to be queued, default is /var/lib/nagios3/pagerduty.
13
14@@ -121,6 +121,15 @@ The monitors interface expects three fields:
15 - `target-id` - Assign any monitors to this target host definition.
16 - `target-address` - Optional, specifies the host of the target to monitor. This must be specified by at least one unit so that the intended target-id will be monitorable.
17
18+### Test alert notifications
19+
20+Checks in the web interface allow sending custom service notifications. However,
21+these type of alerts are logged as `CUSTOM (CRITICAL)` and don't send notifications
22+via third party plugins (e.g. Pagerduty).
23+
24+In order to test if notification plugins work as expected, it is recommended to
25+force an alert (e.g. stop a service).
26+
27
28 # Contact Information
29

Subscribers

People subscribed via source and target branches

to all changes: