Describe the bug
Using Rollbar within DotNet Core 3.1
services.AddHttpContextAccessor();
var config = new RollbarInfrastructureConfig("api-key-here", "Development");
var telemetryOptions = new RollbarTelemetryOptions(true, 20)
{
TelemetryAutoCollectionTypes = TelemetryType.Log | TelemetryType.Error | TelemetryType.Network
};
config.RollbarTelemetryOptions.Reconfigure(telemetryOptions);
var dataSecurityOptions = new RollbarDataSecurityOptions
{
ScrubFields = new string[]
{
nameof(Patient.mrn),
nameof(Patient.lastName),
nameof(Patient.dateOfBirth),
}
};
config.RollbarLoggerConfig.RollbarDataSecurityOptions.Reconfigure(dataSecurityOptions);
RollbarInfrastructure.Instance.Init(config);
<State of RollbarInfrastructure.Instance.TelemetryCollector is in screenshot below>
Later, when invoking WEB API action method, instance of RollbarInfrastructure.Instance.TelemetryCollector within that action method looks like this:
When error is thrown within the action method, error is correctly captured within Rollbar, but none of Telemetry is captured.
Further more, even if I try to manually push telemetry to TelemetryCollector, it is not captured either.
Another interesting point, is that configuration options that are sent to Rollbar completely missing Telemetry configuration:
Describe the bug Using Rollbar within DotNet Core 3.1
Later, when invoking WEB API action method, instance of![2022-03-25_09h06_37](https://user-images.githubusercontent.com/2006491/160136499-567224e5-361d-44fa-bef3-9c951b7102c0.png)
RollbarInfrastructure.Instance.TelemetryCollector
within that action method looks like this:When error is thrown within the action method, error is correctly captured within Rollbar, but none of Telemetry is captured. Further more, even if I try to manually push telemetry to TelemetryCollector, it is not captured either.
Another interesting point, is that configuration options that are sent to Rollbar completely missing Telemetry configuration:
Rollbar Client - Rollbar.NET Hosting Environment (please complete the following information):
Expected behavior Logging telemetry is captured with the exception.