make port configurable and send port+protocol on the syslog relation

Bug #1486257 reported by Kevin W Monroe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postgresql (Juju Charms Collection)
Medium
Unassigned
rsyslog (Juju Charms Collection)
Undecided
Unassigned

Bug Description

It looks like rsyslog hard codes its port values to 514 and 2514:

http://bazaar.launchpad.net/~charmers/charms/trusty/rsyslog/trunk/view/head:/hooks/hooks.py#L29

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 :

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.

Changed in postgresql (Juju Charms Collection):
importance: Undecided → Medium
Revision history for this message
Stuart Bishop (stub) wrote :

This should be implemented in a syslog layer.

Changed in postgresql (Juju Charms Collection):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers