F5OS logging config

[MVogel91]

Is your feature request related to a problem? Please describe.

F5OS Ansible modules currently don't support configuration of logging settings for the F5OS system.

Describe the solution you'd like

There should be a module to update log settings via Ansible.

Describe alternatives you've considered

Drop out of Ansible and configure through API, CLI or GUI.

Additional context

My customer operates a large landscape of iSeries to be swapped by rSeries. A unified onboarding through Ansible would heavily reduce the efforts

[pgouband]

Hi,

Thanks for reporting. Added to the backlog and internal tracking ID for this request is: INFRAANO-1592 for syslog.

[RemcoAA]

V1.11.0 has a f5os.logging module and I can add remote servers but remote forwarding configurations does not work even not with the example.

• name: Configure Remote Forwarding
  f5os_logging:
  remote_forwarding:
  enabled: true
  logs:
  - facility: local0
  severity: informational
  - facility: authpriv
  severity: notice
  - facility: auth
  severity: emergency
  files:
  - name: ansible.log
  - name: audit/
  - name: boot.log

"msg": "{'ietf-restconf:errors': {'error': [{'error-type': 'application', 'error-tag': 'malformed-message', 'error-path': '/openconfig-system:system/logging/f5-openconfig-system-logging:host-logs/config', 'error-message': 'invalid value for: facility in /system/logging/f5-logging:host-logs/f5-logging:config/f5-logging:selectors/f5-logging:selector/f5-logging:facility'}]}}"

[MVogel91]

@RemcoAA

Could you provide details about your F5OS software version?

Some features will only be available starting in certain versions.
Apart from "include_hostname" (1.8+), the options should execute fine with F5OS 1.7.

If you're running a lower version, you may need to verify the options available.

[RemcoAA]

I am running 1.7.0-8741

[MVogel91]

@RemcoAA
There appears to be a bug in the module.

Since this issue (enhancement) was about the feature missing in total, may I ask you to raise another independent issue and properly tag it as a bug?