⚙️ GermainUX Code Profiler
GermainUX Code Profiler provides code-level observability for supported application runtimes.
It helps identify slow methods, performance bottlenecks, errors, inefficient dependencies, and code paths affecting users or business transactions.
For front-end JavaScript profiling, use GermainUX JS Profiler.
👀 Overview
Profiler data can be correlated with:
|
Item |
|---|
|
User sessions |
|
Business workflows |
|
Application performance |
|
Databases |
|
APIs and services |
|
Infrastructure |
|
Errors |
|
Other GermainUX telemetry |
The available profiling depth depends on the monitored language and runtime.
❓ When to Use Code Profiler
Use GermainUX Code Profiler when you need to determine:
|
Question |
|---|
|
Which code caused a slow transaction |
|
Which methods consume the most execution time |
|
Where an exception occurred |
|
Which dependency introduced a delay |
|
Which database or service call affected a transaction |
|
Which code path caused a failed business operation |
⚡ Capabilities
Depending on the runtime, GermainUX can capture:
|
Capability |
|---|
|
Method and function execution |
|
Transaction duration |
|
Call hierarchy |
|
Exclusive execution time |
|
Cumulative execution time |
|
Performance hotspots |
|
Errors and exceptions |
|
Stack traces |
|
Database calls |
|
External API and service calls |
|
CPU and memory activity |
|
Garbage collection |
|
Application throughput |
|
Dependencies |
⏳ Exclusive and Cumulative Time
|
Measure |
Meaning |
|---|---|
|
Exclusive Time |
Time spent executing the method itself |
|
Cumulative Time |
Total time spent in the method and operations it invokes |
📦 Supported Technologies
Supported profiling technologies include:
|
Technology |
Documentation |
|---|---|
|
.NET |
|
|
Go |
|
|
Go deployment |
|
|
Java |
|
|
Node.js |
|
|
Node.js deployment |
|
|
Any other Windows-based Technology |
please contact us if needed |
Exact deployment and available telemetry depend on the runtime.
🏗️ Architecture
Application Runtime → GermainUX Code Profiler → GermainUX Enterprise
Code Profiler can be combined with other GermainUX components to correlate code activity with user experience and infrastructure.
🚀 Deployment Overview
Code Profiler deployment is runtime-specific.
Use the applicable technology guide rather than maintaining duplicate runtime installation procedures here.
⚙️ Configuration
Configure only the level of detail required for the monitoring or investigation.
Depending on the runtime, scope can include:
|
Scope |
|---|
|
Applications |
|
Transactions |
|
Packages |
|
Classes |
|
Methods |
|
Functions |
|
Dependencies |
Start with focused profiling and expand only after validating data volume and overhead.
🔒 Security and Data Privacy
Review whether profiling can capture:
|
Item |
|---|
|
Method arguments |
|
Error details |
|
Stack traces |
|
URLs |
|
Database statements |
|
External-service information |
|
User or business identifiers |
Exclude or protect sensitive values where required.
✅ Validate
Confirm:
|
Check |
|---|
|
The application starts normally. |
|
The profiler connects to GermainUX. |
|
Code telemetry appears. |
|
Methods and transactions are identified correctly. |
|
Errors and dependencies appear. |
|
Profiling overhead is acceptable. |
|
Sensitive information is handled correctly. |
|
Data correlates with the correct application and transaction. |
📚 Related Documentation
📞 Support
For assistance installing, configuring, or troubleshooting GermainUX-Agent, contact GermainUX Support.
Component: Agent, Code Profiler, JS Profiler, RUM Windows
Feature Availability: 2014.1