Niklas

But yeah, looking at [the code](https://github.com/augustd/owasp-security-logging/blob/ed214c9b91c699e6b6165f28900d47cb92d97362/owasp-security-logging-common/src/main/java/org/owasp/security/logging/util/DefaultIntervalLoggerController.java#L85-L99), your observation makes sense. It is busy-looping...

I am inclined to just remove the watchdog altogether. There are better means such as the `/metrics` and `/health` endpoints to monitor the system status now. Seems to be kind...

Converted to an enhancement request. You are totally right, it should be possible to use tags to select projects, rather than having to select projects manually.

Yeah, this is a general limitation and independent of which destination you configure.

> is it planned to be implemented? Yes, as evident by the `p2` and `size/S` labels.

No progress until now. If you're using the `cyclonedx-node-npm` module to generate your BOMs, it supports the `--short-PURLs` flag for exactly this purpose: https://github.com/CycloneDX/cyclonedx-node-npm#usage

> ``` > { > name : "ALPINE_DATABASE_URL", > value : "jdbc:postgresql://" > }, > { > name : "ALPINE_DATABASE_USERNAME", > value : "" > }, > { > name...

You could try reducing the connection pool size to increasingly smaller numbers until it works. I've not seen the startup being blocked by connection creation before, so not sure what...

Thanks for the PR @jameskim0987! Unfortunately it's the opposite of what needs to be done. The schema is defined by the CycloneDX specification: https://github.com/CycloneDX/specification/tree/master/schema But our Go code is not...

Looks like the requests meant for the REST API somehow end up at the frontend pod. I would recommend double-checking whether requesting `https://ci-dev-dt.cp.manh.cloud/api/version` *from outside the cluster* actually reaches the...