Multiprofiling: Running SeaLights side-by-side with other profilers

Multiprofiling lets you run SeaLights alongside other profilers—APM, security, or performance tools—so you don’t have to choose between coverage analytics and existing monitoring like Datadog or the VS Profiler. There are three main approaches:

• first, Microsoft’s CLR Instrumentation Engine which can host multiple profilers;

• second, vendor-specific chaining such as Contrast Security’s mechanism;

• and third, the SeaLights Multiprofiler, a lightweight proxy that loads several profilers in a defined order.

Typical use case: keep your APM traces while adding SeaLights coverage for test optimization and governance.

Compatibility largely depends on third-party profiler implementations; SeaLights supports multiprofiling via CLRIE and the SeaLights Multiprofiler.

Because vendor support for multiprofiling differs, the table below outlines current compatibility among the most common profilers.

Profiler	SeaLights Multiprofiler	Microsoft CLRIE
Sealights	COMPATIBLE	COMPATIBLE
Dynatrace	NOT COMPATIBLE	NOT COMPATIBLE
DataDog	COMPATIBLE	NOT COMPATIBLE
OpenCover	COMPATIBLE	NOT COMPATIBLE
AppDynamics	NOT TESTED	NOT TESTED
NewRelic	NOT TESTED	NOT TESTED
Contrast Security	NOT TESTED	NOT TESTED

• For CLRIE, the other profiler must fully support the CLRIE interface to work with SeaLights.

• Dynatrace does not support/allow Multiprofiling.

• Contrast uses its own chaining; follow Contrast’s docs when combining with SeaLights.

• For Azure web app, Datadog overrides environment variables, and the current MP solution is then not suitable.