The number of files in my file target location keeps expanding very rapidly. Sometimes they are only ~10kb before the writing to a file stops and another file is created.
CREATE EVENT SESSION [mycool1] ON DATABASE
ADD EVENT sqlserver.begin_tran_completed(
ACTION( mdmtargetpkg.mdmget_TimeStampUTC,package0.event_sequence,sqlserver.client_app_name,sqlserver.client_hostname,sqlserver.client_pid,sqlserver.database_id,sqlserver.database_name,sqlserver.query_hash,sqlserver.session_id,sqlserver.sql_text,sqlserver.transaction_id)),
ADD EVENT sqlserver.begin_tran_starting(
ACTION( mdmtargetpkg.mdmget_TimeStampUTC,package0.event_sequence,sqlserver.client_app_name,sqlserver.client_hostname,sqlserver.client_pid,sqlserver.database_id,sqlserver.database_name,sqlserver.query_hash,sqlserver.session_id,sqlserver.sql_text,sqlserver.transaction_id)),
ADD EVENT sqlserver.error_reported(
ACTION( mdmtargetpkg.mdmget_TimeStampUTC,package0.event_sequence,sqlserver.client_app_name,sqlserver.client_hostname,sqlserver.client_pid,sqlserver.database_id,sqlserver.database_name,sqlserver.query_hash,sqlserver.session_id,sqlserver.sql_text,sqlserver.transaction_id)
WHERE ([package0].greater_than_uint64 AND [package0].equal_boolean)),
ADD EVENT sqlserver.login(
ACTION( mdmtargetpkg.mdmget_TimeStampUTC,package0.event_sequence,sqlserver.client_app_name,sqlserver.client_hostname,sqlserver.client_pid,sqlserver.database_id,sqlserver.database_name,sqlserver.query_hash,sqlserver.session_id,sqlserver.sql_text,sqlserver.transaction_id)),
ADD EVENT sqlserver.rpc_completed(
ACTION( mdmtargetpkg.mdmget_TimeStampUTC,package0.event_sequence,sqlserver.client_app_name,sqlserver.client_hostname,sqlserver.client_pid,sqlserver.database_id,sqlserver.database_name,sqlserver.query_hash,sqlserver.session_id,sqlserver.sql_text,sqlserver.transaction_id)
WHERE ([package0].greater_than_uint64 AND [package0].equal_boolean)),
ADD EVENT sqlserver.sql_batch_completed(
ACTION( mdmtargetpkg.mdmget_TimeStampUTC,package0.event_sequence,sqlserver.client_app_name,sqlserver.client_hostname,sqlserver.client_pid,sqlserver.database_id,sqlserver.database_name,sqlserver.query_hash,sqlserver.session_id,sqlserver.sql_text,sqlserver.transaction_id)
WHERE ([package0].greater_than_uint64 AND [package0].equal_boolean))
ADD TARGET package0.event_file(SET filename=N'https://mystorage1.blob.core.windows.net/xevents/myfile.xel')
WITH (MAX_MEMORY=102400 KB,EVENT_RETENTION_MODE=ALLOW_SINGLE_EVENT_LOSS,MAX_DISPATCH_LATENCY=3 SECONDS,MAX_EVENT_SIZE=0 KB,MEMORY_PARTITION_MODE=NONE,TRACK_CAUSALITY=OFF,STARTUP_STATE=OFF)
GO
After creating this, and interacting with SQL, I notice that my xevents files roll over extremely quickly without a reasonable explanation. Sometimes they grow to several MB and other times they are only a few KB.
I am not stopping and starting the session, it is running continuously.
Any pointers would be appreciated. I haven't noticed a pattern that explains when or why new files are created for xevent output.