3 New Customization Options for .NET Apps in TraceView!

  With the latest update to our .NET instrumentation we’re expanding our commitment to our power users by offering additional customization options. Our TraceView instrumentation team works incredibly hard to make sure that the install experience for first and long-time users is quick and easy. While we strive to provide an excellent out-of-the-box experience we realize that our end users also want the flexibility that customization affords when it comes to monitoring. Check out some of the new .NET Framework options we’re rolling out below!

Segment User Traffic for Smarter Troubleshooting

TraceView provides numerous filtering options to help users drill into more detail by default, but a powerful feature now available for .NET is Traffic Partitioning. As a programmatic way of classifying traces users can create buckets for different types of request traffic. A common example is to identify the percentage of traffic that stems from authenticated and anonymous users. For apps like TraceView that utilize time period visualizations (e.g., TraceView’s hour, day, and 7 day views) developers and operations can identify the most popular setting or filter on a time period to troubleshoot latency issues. To find out how – check out the docs here.

Enhance… Enhance…

For drill-down issue identification our instrumentation will automatically divide code into layers that are logical components of your app like ‘IIS’, ‘WCF-Service’, ‘ADO-NET’ and others, but it can also be helpful to add new layers for calls to external processes or to a block of code that isn’t already instrumented. As with partitioning this division can allow for more advanced filtering and the ability to drill-down into potential latency causes that would otherwise be hidden within other layers.

Detail for Distributed Tracing

For apps that take advantage of microservices or .NET multi-threading the new updates will allow for better visualizations. For distributed systems users can connect processes and hosts by passing X-Trace IDs between services. Event reporting from background and child threads will provide better support for asynchronous operations. Additional details like backtraces, info events, or return values can also be added to custom layers for even greater granularity.

Try it out!

Need performance monitoring for your .NET app that’s powerful and flexible? Ask us for a demo, sign up for our free trial, or just visit the Install Agents page within TraceView to get started with the new updates to our .NET instrumentation!