diff --git a/docs/images/classic-pipeline.png b/docs/images/classic-pipeline.png new file mode 100644 index 000000000..3b18fa0fc Binary files /dev/null and b/docs/images/classic-pipeline.png differ diff --git a/docs/images/integrated-pipeline.png b/docs/images/integrated-pipeline.png new file mode 100644 index 000000000..22b280e92 Binary files /dev/null and b/docs/images/integrated-pipeline.png differ diff --git a/docs/troubleshooting.asciidoc b/docs/troubleshooting.asciidoc index 1cab69d2b..0bc726321 100644 --- a/docs/troubleshooting.asciidoc +++ b/docs/troubleshooting.asciidoc @@ -244,4 +244,22 @@ The most expensive operation in the agent is typically stack trace capturing. Th If this is too much in your environment, consider disabling stack trace capturing either partially or entirely: - To disable stack trace capturing for spans, but continue to capture stack traces for errors, set the <> to `-1` and leave the <> on its default. -- To disable stack trace capturing entirely –which in most applications reduces the agent overhead dramatically– set <> to `0`. \ No newline at end of file +- To disable stack trace capturing entirely –which in most applications reduces the agent overhead dramatically– set <> to `0`. + +[float] +[[iisexpress-classic-pipeline]] +=== The ElasticApmModule does not load or capture transactions and there are no agent logs generated on IISExpress + +When debugging applications using Visual Studio and IISExpress, the same requirement to use the `Integrated` managed +pipeline mode exists. Select your web application project in the solution explorer and press F4 to load the properties +window. If the managed pipeline mode is set to classic, the ElasticApmModule will not load. + +For example: + +image::./images/classic-pipeline.png[Classic Managed Pipeline Mode in Properties] + +Should be changed to: + +image::./images/integrated-pipeline.png[Integrated Managed Pipeline Mode in Properties] + +You may need to restart Visual Studio for these changes to fully apply. \ No newline at end of file