Revive the logstash container for testing

[AlanCoding]

SUMMARY

Fast demo:

$ docker exec -i -t $(docker ps -aqf "name=tools_logstash_1") tail -n 2 /logstash.log
{"headers":{"remote_user":"awx_logger","http_accept":"*/*","content_type":"application/json; charset=utf-8","request_path":"/","http_version":"HTTP/1.1","http_authorization":"Basic YXd4X2xvZ2dlcjp3b3JrZmxvd3M=","request_method":"POST","http_host":"logstash:8085","request_uri":"/","content_length":"360"},"@timestamp":"2024-11-21T19:13:14.561Z","level":"WARNING","cluster_host_id":"awx-1","@version":"1","host":"awx-1","stack_info":null,"guid":"7ff29201","logger_name":"awx.api.generics","message":"status 404 received by user alan attempting to access /api/v2/workflow_jobs/4/workflow_nodes/ from 172.18.0.1","tower_uuid":"00000000-0000-0000-0000-000000000000"}
{"headers":{"remote_user":"awx_logger","http_accept":"*/*","content_type":"application/json; charset=utf-8","request_path":"/","http_version":"HTTP/1.1","http_authorization":"Basic YXd4X2xvZ2dlcjp3b3JrZmxvd3M=","request_method":"POST","http_host":"logstash:8085","request_uri":"/","content_length":"360"},"@timestamp":"2024-11-21T19:13:21.941Z","level":"WARNING","cluster_host_id":"awx-1","@version":"1","host":"awx-1","stack_info":null,"guid":"5492b3be","logger_name":"awx.api.generics","message":"status 404 received by user alan attempting to access /api/v2/workflow_jobs/4/workflow_nodes/ from 172.18.0.1","tower_uuid":"00000000-0000-0000-0000-000000000000"}

This already existed, but it wasn't working by the prior instructions. Needed container name & network. Logstash container predated other changes that made these necessary.

I also wanted to demonstrate our future direction, with the files broken out better. You could hypothetically run this completely on its own. If we could keep each compose file a full independent package, then that should be easier in the long run.

Also, the Makefile is nearing the point of maintenance failure, so I'm trying to dodge around changes to that. The ELK stack sure doesn't work.

ISSUE TYPE

• Bug, Docs Fix or other nominal change

COMPONENT NAME

• API

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud