Post reply

XE Module start histogram not show all

  • June 14, 2023 at 12:24 pm

    #4211032

    Hi,

    module_start doesn't find some events in non-filtered session, and finds them when filtering for database name.

    I exec manually from ssms procedure and it count in filtered XE but wasn't in non filtered XE.

    tried also NO_EVENT_LOSS option but still same.

    I found the same problem in other SQL instances.

    This can be problem with some buffer limitation ? But weird is that there is problem with still same procedure.

     

     

    Here is code.

    CREATE EVENT SESSION [ModuleStart_Histogram] ON SERVER 
    ADD EVENT sqlserver.module_start
    ADD TARGET package0.histogram(SET filtering_event_name=N'sqlserver.module_start',slots=(16384),source=N'object_name',source_type=(0))
    WITH (MAX_MEMORY=4096 KB,EVENT_RETENTION_MODE=NO_EVENT_LOSS,MAX_DISPATCH_LATENCY=30 SECONDS,MAX_EVENT_SIZE=4096 KB,MEMORY_PARTITION_MODE=NONE,TRACK_CAUSALITY=OFF,STARTUP_STATE=ON)
    GO


    CREATE EVENT SESSION [ModuleStart_Histogram_test] ON SERVER 
    ADD EVENT sqlserver.module_start(
    WHERE ([sqlserver].[database_name]='DBName'))
    ADD TARGET package0.histogram(SET filtering_event_name=N'sqlserver.module_start',slots=(16384),source=N'object_name',source_type=(0))
    WITH (MAX_MEMORY=4096 KB,EVENT_RETENTION_MODE=ALLOW_SINGLE_EVENT_LOSS,MAX_DISPATCH_LATENCY=30 SECONDS,MAX_EVENT_SIZE=4096 KB,MEMORY_PARTITION_MODE=NONE,TRACK_CAUSALITY=OFF,STARTUP_STATE=ON)
    GO

    Thanks for ideas

    • This topic was modified 1 year, 5 months ago by  tony28.

  • June 15, 2023 at 1:10 pm

    #4211939

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply