Catalog | invalid connection config: missing required peer IP or hostname

[VoliKoN]

When running the docker-compose file from the Catalog src directory, I'm supplying a password as described in the Readme and the MySQL container loads up fine.
I'm getting the following from the catalog container:

catalog-catalog-1     | 2023/02/23 14:50:40 Running database migration...
catalog-catalog-1     | 2023/02/23 14:50:40 Error: Failed to apply migration <nil>
catalog-catalog-1     | 2023/02/23 14:50:40 Connecting to catalog-db:3306/sampledb?timeout=5s
catalog-catalog-1     | 2023/02/23 14:50:40 invalid connection config: missing required peer IP or hostname

The container keeps running and is working, but the logging is misleading...

[niallthomson]

Hi @VoliKoN appreciate you bringing this up. I'd noticed the error but hadn't had time to find the cause. We'll get this on the list.

[niallthomson]

The error

invalid connection config: missing required peer IP or hostname

appears to be caused by the splunksqlx wrapper we use for OpenTelemetry instrumentation. Reverting to sqlx appears to fix the error. Might need to move to our own implementation of instrumenting the DB queries or find a more robust implementation.

[Ninja4Code]

As the author says, this is happening in func createConnection in mysql_repository.go. This is called in main.go, which seems to be the entrypoint of the container? This runs after the migration is completed. I'm able to connect to the database and it has data.

I'm not an expert on Go at all, but does this in any way create a pointer to the sqlx in the repository:
type mySQLRepository struct { db *sqlx.DB readerDb *sqlx.DB }
It seems all of the methods in that repository are using the db or readerDb variable.
Wouldn't the spunksplx be for connecting to Splunk data in MySQL?
Is it possible to do a PR for this and make the change to sqlx because it's still in the code in the lab?