Skip to content

[WCF Service] Verify behavior with ASP.NET/IIS #2683

@Kielek

Description

@Kielek

From @nrcventura on slack https://cloud-native.slack.com/archives/C01NR1YLSE7/p1687280347464339?thread_ts=1687153473.852209&cid=C01NR1YLSE7

  1. Aspnet compatibility enabled or not. When that's enabled there can be some odd behavior depending on how things are instrumented and "state" is maintained. For example, the New Relic instrumentation at one point needs to do some extra work to prevent the instrumentation from tracking what looks like 2 requests even though it's one request.
  2. Self-hosted or IIS hosted. This can affect the interaction with aspnet instrumentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions