In 8.5, we are releasing the auto-instrumentation capability, which allows the .NET APM agent to automatically instrument .NET Framework, .NET Core, and .NET applications without requiring code changes or recompilation.

blog-thumb-release-observability.png

Announcing general availability of Elastic APM .NET agent profiler auto-instrumentation

Announcing the beta release of the Elastic APM .NET agent, which includes distributed tracing, sampling of transaction subsets, and a variety of metrics.

We are proud to announce the <a href="https://www.nuget.org/packages?q=Elastic.Apm">beta release</a> of the Elastic APM .NET agent! The version number of this release is <code>1.0.0-beta1</code>.
Before you get too excited, a quick reminder that you should not run the beta in production. The agent is now ready for more serious testing, so you should definitely consider giving it a try in your test, pre-prod, and dev environments. If you do so, we'd be thrilled to get some feedback in the <a href="https://discuss.elastic.co/c/apm">discussion forum</a>.
Back in February we announced the <a href="/blog/elastic-apm-dot-net-agent-preview-released">alpha release</a> of the .NET APM agent. We received very positive feedback from the community, and we managed to attract lots of users already in this very early stage. Our <a href="https://www.nuget.org/packages/Elastic.Apm">base NuGet package</a> reached around 20,000 downloads.
In this post I'll summarize what happened since the alpha release, and I'll also give a short summary about what we plan to do in the coming months.
<h2>Distributed tracing support</h2>An important new feature of the agent in the beta release is distributed tracing. If you have multiple services that communicate over HTTP with the <code>HttpClient</code> class, the agent will automatically connect these services into a single trace.
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blta2c27a798968828f/5d1a5ee48c85764d8812127a/DotNetDistributedTracingSample.jpg" data-sys-asset-uid="blta2c27a798968828f" alt="Dot Net Distributed Tracing Sample" style="display: block; margin: auto;">
The agent implements the <a href="https://www.w3.org/TR/trace-context/">W3C Trace Context</a> specification. One small caveat to this is that the Trace Context spec is not yet an official standard (although it’s already very close to it — at this moment it's a "Candidate Recommendation"), therefore, in order to avoid breaking tracing in case the W3C Trace Context proposal changes before its finalization, similarly to other Elastic APM agents, we also prefix the added HTTP header with <code>elastic-apm</code>. Everything else is implemented according to the specification, and once the W3C Trace Context specification becomes a standard, we will also rename our HTTP header to completely follow the specification.
In case of HTTP calls, with the <code>HttpClient</code> class you don’t need to do anything; distributed tracing is automatically enabled.
We have also added the ability to serialize and deserialize the trace-parent value manually with the Public Agent API. If your application communicates over a non-HTTP protocol (e.g. gRPC or a direct TCP connection) by using the Public Agent API, you can manually “continue” a distributed trace on the incoming side.
Here is how to serialize the trace parent header:
<pre class="prettyprint">string outgoingDistributedTracingData = Agent.Tracer.CurrentTransaction
 .OutgoingDistributedTracingData.SerializeToString();
</pre>The <code>outgoingDistributedTracingData</code> variable contains the string representation of the distributed tracing data.
When you call another service, you can transfer this string to the callee service and continue the trace with the following method call:
<pre class="prettyprint">var transaction2 = Agent.Tracer.StartTransaction("Transaction2", "TestTransaction", DistributedTracingData.TryDeserializeFromString(serializedDistributedTracingData));
</pre>where <code>serializedDistributedTracingData</code> is the string value that you serialized in the caller side.
The result is that when you look at transactions from these two services in Kibana they will be connected as a single trace.
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blte33649aae8811419/5d1a5f1d3819dc4d83e0c455/DotNetDistributedTracingWithAgentApi.jpg" data-sys-asset-uid="blte33649aae8811419" alt="Dot Net Distributed Tracing With Agent API" style="display: block; margin: auto;">
Of course we plan to continuously add support for more and more libraries using non-HTTP protocols out of the box.
<h2>Sampling</h2>The alpha releases of the agent recorded every single transaction, which in a production system isn’t necessarily ideal. In production, you usually want to capture only a subset of your transactions.
Therefore we also added sampling to the agent. It works the same as in other Elastic APM agents: With the <a href="/guide/en/apm/agent/dotnet/current/config-core.html#config-transaction-sample-rate">TransactionSampleRate config</a> you can tell the agent to only record a certain percentage of the transactions. The expected value is between 0 and 1, where 0.4 means 40% of the transactions will be recorded.
Errors and exceptions are always captured no matter whether the corresponding transaction is sampled or not.
<h2>Metrics</h2>The beta version out of the box reports the following metrics:
<ul>
	<li>System free and total memory (Windows and Linux only)</li>
	<li>Process CPU usage (every platform where .NET Core is supported)</li>
	<li>System CPU usage (Windows and Linux only)</li>
	<li>Process working set and private bytes (every platform where .NET Core is supported)</li>
</ul>With this, the first iteration of the metrics work landed in the 1.0.0-beta1 version of the APM .NET agent.
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltabfbf8ca9a88f939/5d1a5f445d8a9a536d15e978/DotNetMetrics.jpg" data-sys-asset-uid="bltabfbf8ca9a88f939" alt="Dot Net Metrics" style="display: block; margin: auto;">
But we won’t stop here: We plan to add <a href="https://github.com/elastic/apm-agent-dotnet/issues/321">runtime-specific metrics</a> (e.g. GC metrics and more), and we're also considering <a href="https://github.com/elastic/apm-agent-dotnet/issues/322">an API or an integration with an existing metrics library</a> to also send custom metrics to Elastic APM. In case you have any input, <a href="https://discuss.elastic.co/c/apm">feel free to contact us</a>.
One interesting side note: While building this feature we found <a href="https://github.com/dotnet/corefx/issues/37614">a small glitch in the CoreFX API</a>: The <code>Process.TotalProcessorTime</code> method reported inaccurate values on macOS. We implemented a fix for this, which we <a href="https://github.com/dotnet/corefx/pull/37637">contributed back to the CoreFX codebase</a>.
<h2>Additional improvements based on your feedback</h2>The following are a few of the refinements we've made based on your feedback.
<h3>ASP.NET Core transaction names based on routing information</h3>We changed how the agent generates transaction names in the case of ASP.NET Core <a href="https://github.com/elastic/apm-agent-dotnet/issues/166">based on your feedback</a>. The new way of generating transaction names is based on routing information, which is also in-sync with other Elastic APM agents.
In the case of ASP.NET Core MVC, the transaction name will contain the name of the Controller class and the name of the action method. Additionally, in case the action method has parameters, those will be shown as a placeholder string.
Let's take an example: We have an MVC controller called <code>User</code> with an action method called <code>Profile</code> that has an integer parameter, which is a user id:
<pre class="prettyprint">public class UserController : Controller
{
 public IActionResult Profile(int id)
 //... more code
}
</pre>In this case all calls that are routed to the <code>Profile</code> method will be mapped to the same transaction name, which is <code>GET User/Profile {id}</code> — regardless of the user id. So every transaction to the same action method will be grouped to the same transaction group.
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt2fad8c1668442e33/5d1a5f715f304656c2ba82eb/AspNetCoreApmTransactionName.jpg" data-sys-asset-uid="blt2fad8c1668442e33" alt="ASP Net Core APM Transaction Name" style="display: block; margin: auto;">
This works similarly with Razor Pages.
<h3>Docker container ID</h3>If your .NET Core application runs in a Linux container, the agent also reports the container id, following the <a href="https://github.com/elastic/ecs">Elastic Common Schema</a>. With this feature you can jump from APM data directly to container metrics, logs, and more.
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt7aadf0d9f7940c74/5d1a5f8ec4753d564581e5a6/ApmDotNetContainerId.jpg" data-sys-asset-uid="blt7aadf0d9f7940c74" alt="APM Dot Net Container Id" style="display: block; margin: auto;">
This feature is currently Linux only, so we only capture the container id for Linux containers. Of course we plan to have this feature also <a href="https://github.com/elastic/apm-agent-dotnet/issues/272">for Windows containers</a>.
<h3>Public Agent API: evolved</h3>The API surface of our Public Agent API has grown significantly. We know that there are lots of libraries out there that we don’t yet cover with auto instrumentation, but we definitely don’t want you to lose visibility because of this.
Therefore, with the <a href="/guide/en/apm/agent/dotnet/current/public-api.html">Public Agent API</a> you can trace certain activities in your code.
The alpha release already allowed the capturing of spans and transactions, and we now have additional context information that you can attach to your spans and transactions.
For example, if you use a database library that we don’t support with automatic instrumentation, here is how you send database tracing information manually to Elastic APM with the Public Agent API:
<pre class="prettyprint">Agent.Tracer.CurrentTransaction.CaptureSpan("MyCustomDbWrite", ApiConstants.TypeDb, (span) =&gt;
{
 span.Context.Db = new Database 
 { Statement = dbStatement, Type = dbType, Instance = dbInstance };
 //..code executing the database operation
});
</pre>where the string variables <code>dbStatement</code>, <code>dbType</code>, and <code>dbInstance</code> can hold any string value that you would like to capture for your database statements.
You can also manually capture a transaction with incoming HTTP information, in case you’d like to trace a web framework that we don’t support currently out of the box:
<pre class="prettyprint">Agent.Tracer.CaptureTransaction("MyCustomTransaction",ApiConstants.TypeRequest, (transaction) =&gt;
{
 transaction.Context.Request = new Request(myRequestMethod, myRequestUri);
 //code executing the request
 transaction.Context.Response =
 new Response { StatusCode = myStatusCode, Finished = wasFinished };
});
</pre>If you don't want to or aren't able to wrap your code with lambda expressions, you can use the non-lambda pattern of <code>Agent.Tracer.StartTransaction(...)</code> / <code>transaction.StartSpan(...)</code> and <code>transaction.End()</code> / <code>span.End()</code> method pairs.
<h2>.NET flavor support, and Elastic APM Server and NuGet packages</h2>The supported .NET flavors and versions haven't changed. What we announced <a href="/blog/elastic-apm-dot-net-agent-preview-released">in the previous blog post</a> under "Supported frameworks" still holds: The agent works on every .NET flavor and version that supports .NET Standard 2.0. This means .NET Core 2.0 and newer and .NET Framework 4.6.1. For ASP.NET Core we have automatic instrumentation, and you can use the Public Agent API on every .NET Standard 2.0 compatible .NET version.
The NuGet packages haven't changed either (except the fact that we added new versions). We still have four packages — the <a href="https://www.nuget.org/packages/Elastic.Apm.All">Elastic.Apm.All</a> is the default package that references our three other packages. By adding this to an ASP.NET Core application, you are ready to go. Otherwise you can also reference the library specific packages. The <a href="https://www.nuget.org/packages/Elastic.Apm/">Elastic.Apm</a> package contains the base of the agent with the Public Agent API.
The beta agents works with Elastic APM Server version 6.5 and newer. You can keep track of this in the <a href="/guide/en/apm/get-started/current/agent-server-compatibility.html#dotnet-compatibility">agent/server compatibility page</a>.
<h2>What’s next?</h2>Of course our biggest priority for the .NET APM is to reach GA. This will happen based on your feedback — if you have any for us please let us know. If you have a general question, just hop on our <a href="https://discuss.elastic.co/c/apm">Discuss forum</a>. If you have more-detailed feedback where you want to also reference source code, or have a more-detailed feature request, feel free to open an issue in our <a href="https://github.com/elastic/apm-agent-dotnet/issues/new/choose">GitHub repository</a>.
In addition to making existing features production ready, we're also working hard on adding auto instrumentation for <a href="https://github.com/elastic/apm-agent-dotnet/issues/83">ASP.NET on top of .NET Framework</a>.
And of course we're continuing work on closing the gap between the .NET agent and other Elastic APMs.
<h2>Thank you!</h2>And finally, I'd like to take this opportunity to say a huge "thank YOU" to all the amazing community members who are already involved in the development of the .NET agent. Thanks for everyone who tried out the agent, and special thanks for community members who opened issues and also implemented features and actively contributed to the agent:
<ul>
	<li><a href="https://github.com/elastic/apm-agent-dotnet/pull/33">#33</a></li>
	<li><a href="https://github.com/elastic/apm-agent-dotnet/pull/148">#148</a></li>
	<li><a href="https://github.com/elastic/apm-agent-dotnet/pull/259">#259</a></li>
	<li><a href="https://github.com/elastic/apm-agent-dotnet/pull/120">#120</a></li>
	<li><a href="https://github.com/elastic/apm-agent-dotnet/pull/240">#240</a></li>
	<li><a href="https://github.com/elastic/apm-agent-dotnet/pull/289">#289</a></li>
</ul>Try out the .NET APM agent beta with your non-production workloads and let us know what you think! You can get started with Elastic APM with a free trial on the <a href="/cloud/">Elasticsearch Service</a>, or by downloading the <a href="/downloads/apm">default distribution</a>.

APM_BlogHeader.png

APM_BlogThumbnail.png

Elastic APM .NET agent beta released

We are proud to announce the preview release of the Elastic APM .NET Agent! This blog post shows you how you can monitor .NET applications with Elastic APM.

We are proud to announce the preview release of the Elastic APM .NET agent! To make sure everyone is on the same page I’d like to start by defining what we exactly mean by “Preview Release”:&nbsp;this release is the first properly packaged version of the .NET APM agent. The main goal is to collect feedback and to share our progress with the community. If you are interested in this work, please try the agent in your test environment and let us know how it works for you and what features you miss! The best way to give feedback and ask questions is in our <a href="https://discuss.elastic.co/c/apm">discussion forum</a> or if you find an issue or you would like to submit a pull request, jump to our <a href="https://github.com/elastic/apm-agent-dotnet">GitHub repository</a>. The .NET agent is Apache licensed and we are more than happy to receive contributions from the community!
<a href="/solutions/apm">Elastic APM</a> is an Application Performance Monitoring solution from Elastic and alongside the .NET agent, there are official agents available for <a href="https://github.com/elastic/apm-agent-java">Java</a>,<a href="https://github.com/elastic/apm-agent-nodejs"> Node.js</a>,<a href="https://github.com/elastic/apm-agent-python"> Python</a>,<a href="https://github.com/elastic/apm-agent-ruby"> Ruby</a>,<a href="https://github.com/elastic/apm-agent-js-base"> JavaScript/RUM</a>, and<a href="https://github.com/elastic/apm-agent-go"> Go</a>. Elastic APM helps you to gain insight into the performance of your application, track errors, and gauge the end-user experience in the browser.
I will dive into this new APM .NET agent below, but if you'd prefer to watch a preview rather than read about it, check out this video:
<div class="video embed-container" style="height: 319.725px;">
	<img style="width: 100%; margin: auto; display: block;" class="vidyard-player-embed" src="https://play.vidyard.com/Ph4RhJVDrQMQfpJQ3cEov5.jpg" data-uuid="Ph4RhJVDrQMQfpJQ3cEov5" data-v="4" data-type="inline">
</div>If you would like to know more details, please take a look at the <a href="/guide/en/apm/agent/dotnet/current/index.html">Elastic APM .NET agent documentation</a>.
<h2>Supported frameworks</h2>We started the the design of the agent <a href="https://goo.gl/forms/FHHbhptcDx8eDNx92">by asking</a> our potential user base about what frameworks and .NET flavors they use for their .NET applications.
Based on that feedback the preview release has auto instrumentation features for the following libraries:
<ul>
	<li>ASP.NET Core 2.x </li>
	<li>Entity Framework Core 2.x</li>
	<li>Outgoing web requests with the <a href="https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclient?view=netstandard-2.0">HttpClient</a> class on .NET Core</li>
</ul>Additionally, the APM .NET agent offers a <a href="/guide/en/apm/agent/dotnet/current/public-api.html">Public Agent API</a> that enables you to manually instrument your application for other frameworks, or for custom tagging.
This API is shipped as a <a href="https://docs.microsoft.com/en-us/dotnet/standard/net-standard">.NET Standard</a> 2.0 library, which means you can use it on every .NET flavour that supports .NET Standard 2.0. In the case of .NET Full Framework this is version 4.6.1 or newer, and in case of .NET Core this is version 2.0 or newer. The is no restriction in terms of operating systems, the agent packages should work on any operating system that is supported by the .NET Framework you use.
<h2>Downloading the agent</h2>The agent ships as a set of NuGet packages via <a href="http://nuget.org/">nuget.org</a>.
The following packages are available:
<ul>
	<li><a href="https://www.nuget.org/packages/Elastic.Apm.All/">Elastic.Apm.All</a>: This is a meta package that references every other Elastic APM .NET agent package. If you plan to monitor a typical ASP.NET Core application that depends on the <a href="https://www.nuget.org/packages/Microsoft.AspNetCore.All">Microsoft.AspNetCore.All package</a> and uses Entity Framework Core then you should reference this package. In order to avoid adding unnecessary dependencies in applications that aren’t depending on the <a href="https://www.nuget.org/packages/Microsoft.AspNetCore.All">Microsoft.AspNetCore.All package</a> we also shipped some other packages - those are all referenced by the Elastic.Apm.All package.</li>
</ul><ul>
	<li><a href="https://www.nuget.org/packages/Elastic.Apm">Elastic.Apm</a>: This is the core of the agent, which we didn’t name “Core”, because someone already took that name :) This package also contains the Public Agent API and it is a .NET Standard 2.0 package. We also ship every tracing component that traces classes that are part of .NET Standard 2.0 in this package, which includes the monitoring part for HttpClient. Every other Elastic APM package references this package.</li>
	<li><a href="https://www.nuget.org/packages/Elastic.Apm.AspNetCore">Elastic.Apm.AspNetCore</a>: This package contains ASP.NET Core monitoring related code. The main difference between this package and the Elastic.Apm.All package is that this package does not reference the Elastic.Apm.EntityFrameworkCore package, so if you have an ASP.NET Core application that does not use EF Core and you want to avoid adding additional unused references, you should use this package.</li>
	<li><a href="https://www.nuget.org/packages/Elastic.Apm.EntityFrameworkCore">Elastic.Apm.EntityFrameworkCore</a>: This package contains EF Core monitoring related code.</li>
</ul><h2>ASP.NET Core + Elastic APM</h2>The focus of this release is clearly ASP.NET Core monitoring. The first step to enable the agent is to add the Elastic.Apm.All package to your application:
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltbcf49c92cabf3c82/5c98d659470da9484d06fb57/apm-demo-asp-net.jpg" data-sys-asset-uid="bltbcf49c92cabf3c82" alt="Elastic APM Demo in ASP.NET" "="">
The next step is to call the <code>UseElasticApm</code> method in the <code>Configure</code> method within the <code>Startup.cs</code> file:
<pre class="prettyprint">public class Startup
{
 public void Configure(IApplicationBuilder app, IHostingEnvironment env)
 {
 app.UseElasticApm(Configuration);
 //…rest of the method
 }
 //…rest of the class
}
</pre>And that’s it! With this the agent will automatically capture incoming requests, outgoing database and HTTP calls and it will also monitor unhandled exceptions. You can also configure the agent with environment variables or by using the <a href="https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-2.2">IConfiguration</a> interface. For configuration options please see <a href="/guide/en/apm/agent/dotnet/current/configuration.html">the Elastic APM .NET agent documentation</a>.
<h2>What about non-web .NET applications? Public Agent API</h2>As already hinted, even if you don’t use ASP.NET Core, you can still monitor your application with the public Agent API. For this, all you need to do is to reference the <a href="https://www.nuget.org/packages/Elastic.Apm">Elastic.Apm package</a>. Once you did that you will have access to the public Agent API. The entry point of the API is the Agent.Tracer property.
For more details about the public Agent API please refer to the <a href="/guide/en/apm/agent/dotnet/current/public-api.html">documentation</a>.
This small sample shows how to monitor an application that listens to incoming HTTP requests with the <code>HttpListener</code> class:
<pre class="prettyprint">using System;
using System;
using System.Net;
using System.Net.Http;
using System.Threading.Tasks;
using Elastic.Apm;
using Elastic.Apm.Api;
using Elastic.Apm.DiagnosticSource;
using Newtonsoft.Json.Linq;
namespace HttpListenerSample
{
 class Program
 {
 static async Task Main(string[] args)
 {
 //We enable outgoing HTTP request capturing:
 Agent.Subscribe(new HttpDiagnosticsSubscriber());
 // Create a listener.
 var listener = new HttpListener();
 // Add the prefix
 listener.Prefixes.Add("http://localhost:8080/");
 listener.Start();
 Console.WriteLine("Listening...");
 while (true)
 {
 // Note: The GetContext method blocks while waiting for a request.
 var context = listener.GetContext();
 // Capture the incoming request as a 
 //transaction with the Elastic APM .NET Agent
 await Agent.Tracer.CaptureTransaction("Request", 
 ApiConstants.TypeRequest, async () =&gt;
 {
 var request = context.Request;
 // Obtain a response object.
 var response = context.Response;
 // Construct a response.
 var responseString = $"&lt;HTML&gt;&lt;BODY&gt; &lt;p&gt; Hello world! Random number:"
 + $" &lt; {await GenerateRandomNumber()} &lt;/p&gt;"
 + $" &lt;p&gt; Number of stargazers on &lt;a" 
 + $" href=\"https://github.com/elastic/apm-agent-dotnet\"&gt;"
 + $" GitHub for the APM .NET Agent &lt;/a&gt;:"
 + $" {await GetNumberOfStars()} &lt;/p&gt;"
 + $" &lt;/BODY&gt;&lt;/HTML&gt;";
 var buffer = System.Text.Encoding.UTF8.GetBytes(responseString);
 // Get a response stream and write the response to it.
 response.ContentLength64 = buffer.Length;
 var output = response.OutputStream;
 output.Write(buffer, 0, buffer.Length);
 // You must close the output stream.
 output.Close();
 });
 }
 listener.Stop();
 }
 static readonly Random Random = new Random();
 private static async Task&lt;int&gt; GenerateRandomNumber()
 {
 // Get the current transaction and then capture 
 // this method as a span on the current transaction
 return await Agent.Tracer.CurrentTransaction
 .CaptureSpan("RandomGenerator", "Random",
 async () =&gt;
 {
 // Simulate some work
 await Task.Delay(5);
 return Random.Next();
 });
 }
 private static async Task&lt;int&gt; GetNumberOfStars()
 {
 var httpClient = new HttpClient();
 httpClient.DefaultRequestHeaders.Add("User-Agent", "APM-Sample-App");
 //This HTTP request is automatically captured by the Elastic APM .NET Agent:
 var responseMsg = await httpClient
 .GetAsync("https://api.github.com/repos/elastic/apm-agent-dotnet");
 var responseStr = await responseMsg.Content.ReadAsStringAsync();
 return int.TryParse(JObject.Parse(responseStr)["stargazers_count"]
 .ToString(), out var retVal) ? retVal : 0;
 }
 }
}
</pre>One thing I’d like to point out is that in case of an ASP.NET Core application by executing the <code>UseElasticApm()</code> method the agent automatically starts capturing database and outgoing HTTP calls. This is not the case in non-ASP.NET Core applications therefore you have to subscribe to those events, which can be done with the <code>Agent.Subscribe</code> method.
This is how you can subscribe to capture outgoing HTTP calls:
<pre class="prettyprint">Agent.Subscribe(new HttpDiagnosticsSubscriber());
</pre>And this is how you can subscribe to capture Entity Framework Core calls (for this&nbsp;the <a href="https://www.nuget.org/packages/Elastic.Apm.EntityFrameworkCore">Elastic.Apm.EntityFrameworkCore package</a> must be referenced):
<pre class="prettyprint">Agent.Subscribe(new EfCoreDiagnosticsSubscriber());
</pre>More complex configuration can be done through <code>Agent.Setup()</code> if so desired.
<h2>Summary and future</h2>We would be thrilled to get feedback in our <a href="https://discuss.elastic.co/c/apm">discussion forum</a> or in <a href="https://github.com/elastic/apm-agent-dotnet">our GitHub repository</a>. Please keep in mind that the current release is a preview and we may introduce breaking changes based on feedback or in case we find some issue with the current release.Of course we are just in the beginning of this journey with .NET within the Elastic APM solution. We have lots of exciting things we are currently working on. Some examples are distributed tracing support, support for ASP.NET Classic, and many other things.
Additionally, we are also always open for contributions, so feel free to check out the source code over at GitHub and to open a pull request.

Elastic APM .NET Agent Preview Released

Start free trial

Blog Footer CTA

Sign up for Elastic Cloud free trial

gergely-kalapos.jpg

Greg Kalapos

By submitting you acknowledge that you've read and agree to our <a href="/legal/elastic-cloud-account-terms" target="_self">Terms of Service</a>, and you agree to receive the <a href="/legal/privacy-statement#how-we-use-the-information" target="_self">selected communications</a> at the contact details you provided above. See <a href="/legal/privacy-statement/" target="_self">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Communication Preferences - ONLY for /communication-preferences

提交即表示您确认您已阅读并同意我们的<a href="/cn/legal/elastic-cloud-account-terms" target="_self">服务条款</a>，并且您同意通过您提供的上述联系方式接收<a href="/cn/legal/privacy-statement#how-we-use-the-information" target="_self">所选的通信</a>。如需了解更多信息，或想随时取消订阅，请参阅 <a href="/cn/legal/privacy-statement/" target="_self">Elastic 的隐私声明</a>。

By submitting you acknowledge that you've read and agree to our <a href="/legal/serverless-preview-terms" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Serverless GDPR Text

提交即表示您确认您已阅读并同意我们的<a href="/cn/legal/serverless-preview-terms" target="_self">服务条款</a>，并且 Elastic 可以使用您提供的上述详细信息与您联系，以向您介绍我们相关的<a href="/cn/legal/privacy-statement#how-we-use-the-information" target="_self">产品和服务</a>。如需了解更多信息，或想随时取消订阅，请参阅 <a href="/cn/legal/privacy-statement/" target="_self">Elastic 的隐私声明</a>。

By submitting you agree to <a href="/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud Terms of Service</a>. Your personal data will be processed in accordance with <a href="/legal/privacy-statement">Elastic's Privacy Statement</a>.

Cloud Trial GDPR Text

提交即表示您同意 <a href="/cn/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud 服务条款</a>。我们将会按照 <a href="/cn/legal/privacy-statement">Elastic 的隐私声明</a>处理您的个人数据。

By submitting you acknowledge that you've read and agree to our <a href="/legal/terms-of-use" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Newsletter GDPR Text

提交即表示您确认您已阅读并同意我们的<a href="/cn/legal/terms-of-use" target="_self">服务条款</a>，并且 Elastic 可以使用您提供的上述详细信息与您联系，以向您介绍我们相关的<a href="/cn/legal/privacy-statement#how-we-use-the-information" target="_self">产品和服务</a>。如需了解更多信息，或想随时取消订阅，请参阅 <a href="/cn/legal/privacy-statement/" target="_self">Elastic 的隐私声明</a>。

Explore similar demos

Overview

Speakers

Close

See more insights

The content on this page is not available in the selected language. As Elastic grows globally, we continue to support content in multiple languages.

The content on this page is not available in the selected language.

本页内容尚不支持所选语言。Elastic 正在不断努力，以实现对多种语言内容的支持。感谢您在此期间给予的耐心与陪伴！

Author

Articles by

Learn more

Watch now (no PT)

Watch now

See all top stories

All (no PT translation)

Contact information

Press Release

Share on Reddit

Share this story

Share by Email

Thank you for your interest!

Contact Info

Follow us on Youtube

Load More

Share on LinkedIn

Follow us on LinkedIn

Search Integrations

All Solutions

Video for

Follow us on Twitter

See when this webinar starts in my time zone

查看本次网络研讨会在我的时区的开始时间

Register to Watch

Register now

See All Posts

Can't make it? Register and we'll send you the recording. You'll also receive an email with related content

无法实时参加？注册后我们会给您发送录像。您还将收到相关内容的电子邮件。

Author

Articles by Greg Kalapos

Announcing general availability of Elastic APM .NET agent profiler auto-instrumentation

Elastic APM .NET agent beta released

Elastic APM .NET Agent Preview Released

Sign up for Elastic Cloud free trial