hsiegeln/camel-ops-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit: Architecture, UX Strategy, and Scaffolding

Browse Source
This commit is contained in:
OpenClaw Squad
2026-03-01 20:52:49 +00:00
commit e0a122f440
19 changed files with 715 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/EXTRACTION_PROMPT.md Normal file
View File

@@ -0,0 +1,9 @@
# Architecture Update: nJAMS-Style Data Extraction (Java Agent)
**Context from User (Hendrik):**
"The architect and developer should think about a javaagent to mimic the njams agent for mulesoft and tibco to extract data from not-instrumented apache camel applications. we should be as 'apache camel native' as possible and also keep the monitoring overhead to an absolute minimum."
**Directives for Architect & Developer:**
1. **Zero-Code Change:** Customers should not have to rewrite their Camel XML or Java DSL. We attach an agent, and it works.
2. **Camel Native:** Instead of blindly instrumenting JVM bytecode (which can break things and add overhead), the agent should ideally hook into Camel's native SPIs (`CamelContext`, `EventNotifier`, `InterceptStrategy`, `Tracer`).
3. **Minimum Overhead:** Capturing payloads at every step can cause OutOfMemory errors and CPU spikes. How do we extract data cheaply? (e.g., Ring buffers, sampling, payload truncation, extracting only on error, or dynamically toggling capture from the SaaS Control Plane).