Custom static values for Log aggregation in AWX

[Workasis]

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

Bug Summary

I have two AWX instances running in the same Kubernetes cluster. Both instances are configured to export logs to Logstash. However, I am facing an issue where all job events are sent to the Logstash server, but I cannot identify which logs come from which AWX instance. The cluster_host_id always reflects the running AWX web pod (e.g., awx_web_37...), and the tower_id is null.

I would like to know if it is possible to add custom static values in the log aggregator settings to set a static value, such as awx_name: awx1 or using existing varible tower_url_base. This would help in identifying logs from different AWX instances clearly. I have observed that each instance has a unique identifier, but this value is lost if I delete and recreate or migrate the AWX instance. I would like to avoid using this field to identify the instance.

AWX Operator version

2.3.0

AWX version

AWX 22.4.0

Kubernetes platform

kubernetes

Kubernetes/Platform version

v1.23.17

Modifications

yes

Steps to reproduce

1. Deploy two AWX instances in the same Kubernetes cluster
2. Configurer both instances to export logs to Logstash
3. Run AWX demo job
4. The cluster_host_id reflets the running AWX and tower_id is null

Expected results

• cluster_host_id returns a uniqe id in AWX instaces which is not static for long term configuration.
• tower_id is nul even i set a random number in AWX logging settings
• tower_url_base is not present in awx job_events

Actual results

• Th set a static varible in each AWX for log aggretor settings (ex: awx_name: awx1) to identify logs from different instances AWX.
• tower_id is null, providing no identification of instances even i set a ranndom number in AWX for tower_id

Additional information

No response

Operator Logs

No response