Exception within .NET processes with MongoDB after OneAgent Upgrade to 1.307

We have identified the cause of the issue and we are actively working on a resolution.

There are currently 2 workarounds available:
* The .NET MongoDB OneAgent feature can be disabled (enabled off, instrumentation off, then restart the process)
* Downgrade to OA version 1.305.

If you are experiencing issues and need assistance with implementing the workaround, please open a support case.

We are actively working on a permanent fix and will communicate its availability as soon as it becomes available.

The following workarounds are still available. If you need assistance with performing these workarounds, please reach out to Dynatrace Product Support.
* The .NET MongoDB OneAgent feature can be disabled (enabled off, instrumentation off, then restart the process)
* Downgrade to OA version 1.305.

We have released the fix for the issue in OneAgent 1.307.59.
The previously suggested workarounds are not required anymore and should be reversed after the OneAgent Update. If you require further assistance, please reach out to Dynatrace Product Support. Thank you for your patience while we worked on resolving the issue and sorry for the inconvenience this may have caused.