make port configurable and send port+protocol on the syslog relation
Bug #1486257 reported by
Kevin W Monroe
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| postgresql (Juju Charms Collection) |
Won't Fix
|
Medium
|
Unassigned | ||
| rsyslog (Juju Charms Collection) |
New
|
Undecided
|
Unassigned | ||
Bug Description
It looks like rsyslog hard codes its port values to 514 and 2514:
http://
I think this should be configurable. This seems like a fairly easy feature to add, but perhaps there's a good reason to not allow users to change this. I'm all ears.
If there are no objections to making this configurable, I'd like to see the port value and protocol sent on the syslog relation so connected units (like rsyslog-forwarder*) know to use the configured port/protocol values as well.
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in postgresql (Juju Charms Collection): | |
| importance: | Undecided → Medium |
Revision history for this message
| Stuart Bishop (stub) wrote | #2 |
| Changed in postgresql (Juju Charms Collection): | |
| status: | New → Won't Fix |
To post a comment you must log in.
If this goes ahead, the PostgreSQL charm will need an update to support non-default ports. Please set the postgres status to triaged if this goes ahead and the interface changed.