Client-side Container Images
Use this page when you need a client image for log shipping or PushProx. The table below records the image versions and digests currently listed in this Help repository. Confirm the approved version and current scan or licensing status with the Sauron team before a new production deployment; this page is updated manually and does not report live registry state.
Which image should I use?
| Client image | Use it for | Start here |
|---|---|---|
| FluentBit | Send logs to Sauron OpenSearch. | Sending Logs |
| Prometheus PushProx Client | Register scrape targets when Sauron Prometheus cannot directly reach your metrics endpoint. | Sending Metrics - PushProx |
For authentication choices, see User Access. For PushProx setup and checks, see Sending Metrics.
Before production
Confirm the Third Party Licensed Technology approval covers your team's use, not only Sauron's own use.
Before using a client image in production:
- Confirm the required Third Party Licensed Technology approval is complete.
- Confirm the approved version and digest with the Sauron team, then pull it.
- Confirm the client authentication method in User Access.
- Run the first log or PushProx validation flow before relying on production traffic.
- Keep the image name, tag, digest, command, and client logs for troubleshooting.
Available Images
FluentBit
| Versions | Images |
|---|---|
| 4.2.2 | docker pull container-registry.oracle.com/olcne/fluent-bit-base:v4.2.2@sha256:cfdfb194c66e729db1e8438976a238ad7718d25875d7fec357b5bb6eda65b670 |
Prometheus PushProx Client
| Versions | Images |
|---|---|
| 0.2.0-105 | docker pull phx.ocir.io/odx-sre/sauron/pushprox-mirror:0.2.0-105@sha256:fc37c0ba876d9aa722be858f4369fdcf34b5c34c0b49e500e6adc2be0fe07973 |
Tips and checks
- Tips: Use an approved image version and digest. Keep credentials outside the image.
- Check: Confirm the image matches your platform and the container starts. Read its client logs for connection errors and check its arguments against the relevant setup guide.