Josh Coleman

Results 18 issues of Josh Coleman

- Changes to port availability check: Query OS for port usage, exhaustively claim port IPv4/6/HTTP.sys, wait for OS to report port as available again (this is overkill, but I wanted...

We are experiencing errors for some integration tests after the organization disabled the TLS 1.0 and 1.1 protocols for the staging collector. This appears to vary between environments as the...

bug
chore

### Feature Description The .NET agent currently only supports instrumentation of async methods with a `Task` or `Task` return type. A recent customer escalation involved an attempt to use `Parallel.ForEachAsync(...)`...

feature request

Test fix for lambda issue creating spans

### Feature Description Multiple logging frameworks include the ability to supply an exception. This exception object is inspected and typically the message, stack trace, and any inner exceptions are reported...

feature request

**Description** When explain plans are enabled, the .NET agent currently requests up to 20 plans per transaction for any Datastore segments over the configured explain plan duration threshold. These explain...

bug
documentation

### Is your feature request related to a problem? Please describe. Agent logs from application startup are not captured/forwarding by the New Relic .NET Agent. I would like to see...

enhancement
feature request

### Feature Description There was one metric that was not implemented for the log4net forwarding EAP: `Logging/Forwarding/Dropped` This was not implemented since a simple strategy could not be identified to...

feature request

### Feature Description During a recent GTSE investigation, @nr-ahemsath noted that the profiler did not log the agent version number on startup as expected. The customer's environment was an Azure...

enhancement
GTSE
win != linux
technical debt

**Description** .NET Core applications with Send Data on Exit enabled, can cause applications to crash during shutdown. This has been observed when the collector returns a HTTP `409` response to...

bug