> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GermainUX Code Profiler

> GermainUX Code Profiler provides code-level observability for supported application runtimes.

Components
[`Agent`](https://docs.germainux.com/main/germainux-agent)
[`Code Profiler`](https://docs.germainux.com/main/germain-ux-code-profiler)
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`RUM Windows`](https://docs.germainux.com/main/germainux-rum-windows)

Availability
2014.1

**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**.

> **[When to Use Code Profiler](#when-to-use-code-profiler)**
>
> Find slow code paths

> **[Supported Technologies](#supported-technologies)**
>
> Runtimes and profiling options

> **[Configuration](#configuration)**
>
> Scope profiling detail

> **[Support](#support)**
>
> Get installation help

## Overview

Profiler data can be correlated with:

* 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:

* 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:

* Method and function execution
* Transaction duration
* Call hierarchy
* Exclusive execution time
* Cumulative execution time
* Performance hotspots

> **Show all 14**
>
> * 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 | [.NET Application Monitoring and Session Replay](https://docs.germainux.com/main/net-monitoring.md) |
| Go | [Go Monitoring](https://docs.germainux.com/main/golang-monitoring.md) |
| Go deployment | [Deploy Code Profiling for Go](https://docs.germainux.com/main/deploy-code-profiling-usage-monitoring-for-golang.md) |
| Java | [Java Monitoring](https://docs.germainux.com/main/java-monitoring.md) |
| Node.js | [Node.js Monitoring](https://docs.germainux.com/main/node-js-monitoring.md) |
| Node.js deployment | [Deploy Node.js Monitoring](https://docs.germainux.com/main/node-js-monitoring-deployment.md) |
| Any other Windows-based Technology | please [contact us](https://docs.germainux.com/main/support.md) 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:

* 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:

* 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:

* 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

* [GermainUX Code Profiler](https://docs.germainux.com/main/germain-ux-code-profiler.md)
* [GermainUX JS Profiler](https://docs.germainux.com/main/germain-ux-js-profiler.md)
* [GermainUX Agent](https://docs.germainux.com/main/germainux-agent.md)
* [GermainUX RUM Windows](https://docs.germainux.com/main/germainux-rum-windows.md)

## Support

For assistance installing, configuring, or troubleshooting GermainUX-Agent, contact [GermainUX Support](https://docs.germainux.com/main/support.md).

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> The Germain Team can help you set this up.

> **Can't find what you need?**
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.