How to read extended events through the .net code












0














I had this requirement to log and read the extended events , I did achieve this through the Xpath queries and it worked as expected . Sometime has passed and now the .xel file has grown in size and the Xpath query takes long time to give back the results . I have heard there is .net code which will help to read the .xel file with more efficiency . Please help me the source code for the same .










share|improve this question





























    0














    I had this requirement to log and read the extended events , I did achieve this through the Xpath queries and it worked as expected . Sometime has passed and now the .xel file has grown in size and the Xpath query takes long time to give back the results . I have heard there is .net code which will help to read the .xel file with more efficiency . Please help me the source code for the same .










    share|improve this question



























      0












      0








      0







      I had this requirement to log and read the extended events , I did achieve this through the Xpath queries and it worked as expected . Sometime has passed and now the .xel file has grown in size and the Xpath query takes long time to give back the results . I have heard there is .net code which will help to read the .xel file with more efficiency . Please help me the source code for the same .










      share|improve this question















      I had this requirement to log and read the extended events , I did achieve this through the Xpath queries and it worked as expected . Sometime has passed and now the .xel file has grown in size and the Xpath query takes long time to give back the results . I have heard there is .net code which will help to read the .xel file with more efficiency . Please help me the source code for the same .







      .net sql-server xpath extended-events






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 12 '18 at 16:12









      TrebuchetMS

      2,0601619




      2,0601619










      asked Nov 12 '18 at 11:57









      ManjunathManjunath

      32




      32
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Extended Events data can be read programmatically using QuerableXEventData from any .NET application, including PowerShell.



          Below is a C# console example that extracts XE data from a trace that includes the rpc_completed event. The constructor overload here specifies the file pattern of the XE files to process. The project includes assembly references to Microsoft.SqlServer.XE.Core and Microsoft.SqlServer.XEvent.Linq (located in C:Program FilesMicrosoft SQL Server140Shared on my system).



          using System;
          using Microsoft.SqlServer.XEvent.Linq;

          namespace ExtendedEventsExample
          {
          class Program
          {
          static void Main(string args)
          {
          var xeFilePathPattern = @"C:TraceFilesrpc_completed*.xel";
          using (var events = new QueryableXEventData(xeFilePathPattern))
          {
          foreach (var xe in events)
          {
          if (xe.Name == "rpc_completed")
          {
          var xeName = xe.Name;
          var xeTimestamp = xe.Timestamp;
          var xeStatementField = (String)xe.Fields["statement"].Value.ToString();
          var xeDurationField = (UInt64)xe.Fields["duration"].Value;
          var xeClientAppNameAction = (String)xe.Actions["client_app_name"].Value;
          Console.WriteLine(
          $"Name: {xeName}" +
          $", Timestamp: {xeTimestamp}" +
          $", Statement: {xeStatementField}" +
          $", Duration: {xeDurationField}" +
          $", ClientAppName: {xeClientAppNameAction}"
          );
          }
          }
          }
          }
          }
          }


          I've found this method to be reasonably fast even with large trace files. You might consider using rollover files to limit trace file size. Example here.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53261682%2fhow-to-read-extended-events-through-the-net-code%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Extended Events data can be read programmatically using QuerableXEventData from any .NET application, including PowerShell.



            Below is a C# console example that extracts XE data from a trace that includes the rpc_completed event. The constructor overload here specifies the file pattern of the XE files to process. The project includes assembly references to Microsoft.SqlServer.XE.Core and Microsoft.SqlServer.XEvent.Linq (located in C:Program FilesMicrosoft SQL Server140Shared on my system).



            using System;
            using Microsoft.SqlServer.XEvent.Linq;

            namespace ExtendedEventsExample
            {
            class Program
            {
            static void Main(string args)
            {
            var xeFilePathPattern = @"C:TraceFilesrpc_completed*.xel";
            using (var events = new QueryableXEventData(xeFilePathPattern))
            {
            foreach (var xe in events)
            {
            if (xe.Name == "rpc_completed")
            {
            var xeName = xe.Name;
            var xeTimestamp = xe.Timestamp;
            var xeStatementField = (String)xe.Fields["statement"].Value.ToString();
            var xeDurationField = (UInt64)xe.Fields["duration"].Value;
            var xeClientAppNameAction = (String)xe.Actions["client_app_name"].Value;
            Console.WriteLine(
            $"Name: {xeName}" +
            $", Timestamp: {xeTimestamp}" +
            $", Statement: {xeStatementField}" +
            $", Duration: {xeDurationField}" +
            $", ClientAppName: {xeClientAppNameAction}"
            );
            }
            }
            }
            }
            }
            }


            I've found this method to be reasonably fast even with large trace files. You might consider using rollover files to limit trace file size. Example here.






            share|improve this answer


























              0














              Extended Events data can be read programmatically using QuerableXEventData from any .NET application, including PowerShell.



              Below is a C# console example that extracts XE data from a trace that includes the rpc_completed event. The constructor overload here specifies the file pattern of the XE files to process. The project includes assembly references to Microsoft.SqlServer.XE.Core and Microsoft.SqlServer.XEvent.Linq (located in C:Program FilesMicrosoft SQL Server140Shared on my system).



              using System;
              using Microsoft.SqlServer.XEvent.Linq;

              namespace ExtendedEventsExample
              {
              class Program
              {
              static void Main(string args)
              {
              var xeFilePathPattern = @"C:TraceFilesrpc_completed*.xel";
              using (var events = new QueryableXEventData(xeFilePathPattern))
              {
              foreach (var xe in events)
              {
              if (xe.Name == "rpc_completed")
              {
              var xeName = xe.Name;
              var xeTimestamp = xe.Timestamp;
              var xeStatementField = (String)xe.Fields["statement"].Value.ToString();
              var xeDurationField = (UInt64)xe.Fields["duration"].Value;
              var xeClientAppNameAction = (String)xe.Actions["client_app_name"].Value;
              Console.WriteLine(
              $"Name: {xeName}" +
              $", Timestamp: {xeTimestamp}" +
              $", Statement: {xeStatementField}" +
              $", Duration: {xeDurationField}" +
              $", ClientAppName: {xeClientAppNameAction}"
              );
              }
              }
              }
              }
              }
              }


              I've found this method to be reasonably fast even with large trace files. You might consider using rollover files to limit trace file size. Example here.






              share|improve this answer
























                0












                0








                0






                Extended Events data can be read programmatically using QuerableXEventData from any .NET application, including PowerShell.



                Below is a C# console example that extracts XE data from a trace that includes the rpc_completed event. The constructor overload here specifies the file pattern of the XE files to process. The project includes assembly references to Microsoft.SqlServer.XE.Core and Microsoft.SqlServer.XEvent.Linq (located in C:Program FilesMicrosoft SQL Server140Shared on my system).



                using System;
                using Microsoft.SqlServer.XEvent.Linq;

                namespace ExtendedEventsExample
                {
                class Program
                {
                static void Main(string args)
                {
                var xeFilePathPattern = @"C:TraceFilesrpc_completed*.xel";
                using (var events = new QueryableXEventData(xeFilePathPattern))
                {
                foreach (var xe in events)
                {
                if (xe.Name == "rpc_completed")
                {
                var xeName = xe.Name;
                var xeTimestamp = xe.Timestamp;
                var xeStatementField = (String)xe.Fields["statement"].Value.ToString();
                var xeDurationField = (UInt64)xe.Fields["duration"].Value;
                var xeClientAppNameAction = (String)xe.Actions["client_app_name"].Value;
                Console.WriteLine(
                $"Name: {xeName}" +
                $", Timestamp: {xeTimestamp}" +
                $", Statement: {xeStatementField}" +
                $", Duration: {xeDurationField}" +
                $", ClientAppName: {xeClientAppNameAction}"
                );
                }
                }
                }
                }
                }
                }


                I've found this method to be reasonably fast even with large trace files. You might consider using rollover files to limit trace file size. Example here.






                share|improve this answer












                Extended Events data can be read programmatically using QuerableXEventData from any .NET application, including PowerShell.



                Below is a C# console example that extracts XE data from a trace that includes the rpc_completed event. The constructor overload here specifies the file pattern of the XE files to process. The project includes assembly references to Microsoft.SqlServer.XE.Core and Microsoft.SqlServer.XEvent.Linq (located in C:Program FilesMicrosoft SQL Server140Shared on my system).



                using System;
                using Microsoft.SqlServer.XEvent.Linq;

                namespace ExtendedEventsExample
                {
                class Program
                {
                static void Main(string args)
                {
                var xeFilePathPattern = @"C:TraceFilesrpc_completed*.xel";
                using (var events = new QueryableXEventData(xeFilePathPattern))
                {
                foreach (var xe in events)
                {
                if (xe.Name == "rpc_completed")
                {
                var xeName = xe.Name;
                var xeTimestamp = xe.Timestamp;
                var xeStatementField = (String)xe.Fields["statement"].Value.ToString();
                var xeDurationField = (UInt64)xe.Fields["duration"].Value;
                var xeClientAppNameAction = (String)xe.Actions["client_app_name"].Value;
                Console.WriteLine(
                $"Name: {xeName}" +
                $", Timestamp: {xeTimestamp}" +
                $", Statement: {xeStatementField}" +
                $", Duration: {xeDurationField}" +
                $", ClientAppName: {xeClientAppNameAction}"
                );
                }
                }
                }
                }
                }
                }


                I've found this method to be reasonably fast even with large trace files. You might consider using rollover files to limit trace file size. Example here.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 12 '18 at 12:55









                Dan GuzmanDan Guzman

                22.9k31640




                22.9k31640






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53261682%2fhow-to-read-extended-events-through-the-net-code%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Full-time equivalent

                    さくらももこ

                    13 indicted, 8 arrested in Calif. drug cartel investigation