Audit Log Proof of Concept for OpenTelemetry

This proof of concept is part of an effort to make OpenTelemetry fit for audit logging purposes. We are building an end-to-end scenario to refine the challenges and requirements for audit logging in OTel and to showcase potential solutions.

Read about the entire idea at open-telemetry/community#2409.

About This Project

This PoC scenario provides an easy setup of an OpenTelemetry Demo environment to test how log messages are delivered through multiple different systems.

Requirements and Setup

• git
• docker or podman
• task
• optional: k9s

Quick Start Linux

git clone https://github.com/apeirora/otel-audit-log-poc.git
cd otel-audit-log-poc
sudo snap install task --classic
task
# wait a couple of minutes until all images are downloaded and pods are running - feel free to check with k9s
task otel:port-forward

Quick Start on mac

brew install go-task/tap/go-task
git clone https://github.com/apeirora/otel-audit-log-poc.git
cd audit-logpoc-for-otel
task # run the app 
task otel:port-forward #check http://localhost:8080
#to stop port forwarding type ctrl + c in the terminal

In case you're facing any errors, you can easily check which other tasks are defined: task -a

For example if you want to use kind instead of k3d for your cluster setup, then you can do the following:

task kind:start otel:demo-install

Demo Endpoints

With the frontend-proxy port-forward set up, you can access:

Web store: http://localhost:8080/ Grafana: http://localhost:8080/grafana/ Load Generator UI: http://localhost:8080/loadgen/ Jaeger UI: http://localhost:8080/jaeger/ui/ Flagd configurator UI: http://localhost:8080/feature

Support, Feedback, Contributing

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.

Security / Disclosure

If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.

Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

Licensing

Copyright 2025 SAP SE or an SAP affiliate company and ApeiroRA contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.