Expose livestatus socket to the network
Bug #1916530 reported by
Tiago Pasqualini da Silva
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Nagios Charm |
Fix Released
|
Undecided
|
Tiago Pasqualini da Silva | ||
Bug Description
Currently, the charm can enable the livestatus socket on nagios. Nagios currently allows it to be accessed through the network by exposing it with xinetd. The charm could take advantage of this by offering a config option to enable it.
With this socket exposed to the network, admins could take advantage of this by querying nagios from whatever machine is allowed to query it, instead of needing to ssh into the nagios unit and querying the livestatus unix socket.
Related branches
~tiago.pasqualini/charm-nagios:livestatus
- James Troup (community): Approve
- Tom Haddon: Abstain
- BootStack Reviewers: Pending requested
- Xav Paice: Pending requested
- Drew Freiberger: Pending requested
-
Diff: 150 lines (+89/-0)4 files modifiedconfig.yaml (+19/-0)
hooks/templates/livestatus.tmpl (+19/-0)
hooks/upgrade_charm.py (+33/-0)
tests/functional/test_config.py (+18/-0)
~tiago.pasqualini/charm-nagios:livestatus
- James Troup (community): Needs Fixing
- Drew Freiberger (community): Approve
- Xav Paice (community): Needs Information
-
Diff: 150 lines (+89/-0)4 files modifiedconfig.yaml (+19/-0)
hooks/templates/livestatus.tmpl (+19/-0)
hooks/upgrade_charm.py (+33/-0)
tests/functional/test_config.py (+18/-0)
Revision history for this message
| Tiago Pasqualini da Silva (tiago.pasqualini) wrote | #1 |
| Changed in charm-nagios: | |
| assignee: | nobody → Tiago Pasqualini da Silva (tiago.pasqualini) |
| status: | New → In Progress |
| description: | updated |
| Changed in charm-nagios: | |
| status: | In Progress → Fix Released |
| milestone: | none → 21.07 |
To post a comment you must log in.
Fix: https:/