Dataset Viewer
The dataset viewer is not available for this subset.
Cannot get the split names for the config 'default' of the dataset.
Exception:    SplitsNotFoundError
Message:      The split names could not be parsed from the dataset config.
Traceback:    Traceback (most recent call last):
                File "tsfile/tsfile_py_cpp.pyx", line 567, in tsfile.tsfile_py_cpp.tsfile_reader_new_c
              tsfile.exceptions.FileOpenError: 28: 
              
              The above exception was the direct cause of the following exception:
              
              Traceback (most recent call last):
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
                  for split_generator in builder._split_generators(
                                         ~~~~~~~~~~~~~~~~~~~~~~~~~^
                      StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                  )
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/tsfile/tsfile.py", line 271, in _split_generators
                  scan = self._scan_metadata(all_files)
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/tsfile/tsfile.py", line 318, in _scan_metadata
                  with self._open_reader(file) as reader:
                       ~~~~~~~~~~~~~~~~~^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/tsfile/tsfile.py", line 742, in _open_reader
                  return TsFileReader(file)
                File "tsfile/tsfile_reader.pyx", line 323, in tsfile.tsfile_reader.TsFileReaderPy.__init__
              SystemError: <class '_weakrefset.WeakSet'> returned a result with an exception set
              
              The above exception was the direct cause of the following exception:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 68, in compute_split_names_from_streaming_response
                  for split in get_dataset_split_names(
                               ~~~~~~~~~~~~~~~~~~~~~~~^
                      path=dataset,
                      ^^^^^^^^^^^^^
                      config_name=config,
                      ^^^^^^^^^^^^^^^^^^^
                      token=hf_token,
                      ^^^^^^^^^^^^^^^
                  )
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
                  info = get_dataset_config_info(
                      path,
                  ...<6 lines>...
                      **config_kwargs,
                  )
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
                  raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
              datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

Advanced SIEM Dataset (TsFile)

This dataset is a lossless conversion to the Apache TsFile format of the HuggingFace dataset darkknight25/Advanced_SIEM_Dataset: a synthetic SIEM (Security Information and Event Management) event log for cybersecurity ML/AI research.

Original dataset

  • Source dataset: darkknight25/Advanced_SIEM_Dataset
  • Author / contact: sunny thakur (sunny48445@gmail.com)
  • License: MIT
  • Content: 100,000 synthetic security events (JSON Lines) simulating SIEM logs across 8 event types — firewall, ids_alert, auth, endpoint, network, cloud, iot, ai — with MITRE ATT&CK techniques, threat-actor associations and unconventional IOCs. Intended for anomaly detection, threat classification, predictive analytics and UEBA.

Scale

  • 100,000 events, 43 columns after flattening (incl. Time)
  • 8 event types (rows): ai 12,667 · endpoint 12,589 · auth 12,516 · cloud 12,511 · ids_alert 12,500 · firewall 12,448 · iot 12,434 · network 12,335
  • Time range: 2020-07-12 → 2030-07-10 (ISO 8601, second precision in source)

TsFile storage mapping (table model)

Role Column(s) Type
TAG event_type STRING — 8 types, one type = one device
Time source timestamp INT64 (ms)
FIELD (DOUBLE) meta_risk_score, meta_confidence, behav_baseline_deviation, behav_entropy DOUBLE
FIELD (INT64) process_id, src_port, dst_port, bytes, duration INT64
FIELD (BOOLEAN) behav_frequency_anomaly, behav_sequence_anomaly BOOLEAN
FIELD (STRING) event_id, source, severity, description, raw_log, additional_info, action, user, and all per-event-type fields (src_ip, dst_ip, alert_type, signature_id, model_id, input_hash, device_id, cloud_service, method, mac_address, …) plus meta_geo_location, meta_device_hash, meta_user_agent, meta_session_id STRING

Conversion notes

  • Flattened to a single wide table. In the source JSONL the per-event-type fields are already flat at the top level of each record, so they are carried over as columns as-is (each is sparse — populated only for its event type). The two nested dicts are flattened: advanced_metadatameta_* (6 fields, 100% present) and behavioral_analyticsbehav_* (4 fields, ~10% present).
  • No columns dropped, no rows dropped: all 100,000 events (unique event_id) and all flattened fields are preserved. Sparse columns keep their nulls — TsFile simply does not write null cells.
  • Time: source timestamp (ISO 8601) → INT64 epoch milliseconds. Rows are sorted ascending by (event_type, Time).
  • Duplicate-timestamp handling (+1 ms): the source contains 35 (event_type, timestamp) collisions at second precision — different events that happen to share the same second (a property of the source data, not introduced here). TsFile requires strictly increasing time within a device, so within each event_type, any row whose time is ≤ the previous row's is bumped to prev + 1ms. Exactly 35 rows are nudged by one millisecond; all 100,000 events are kept.

Layout

data/
└── advanced_siem_dataset.tsfile

Usage

from tsfile import TsFileReader

reader = TsFileReader("data/advanced_siem_dataset.tsfile")
schemas = reader.get_all_table_schemas()
tname = next(iter(schemas))

cols = ["event_type", "severity", "meta_risk_score", "src_ip", "alert_type"]
with reader.query_table(tname, cols, batch_size=65536) as rs:
    while (batch := rs.read_arrow_batch()) is not None:
        df = batch.to_pandas()
        # ... process ...
reader.close()

Citation

@misc{advanced_siem_dataset,
  title  = {Advanced SIEM Dataset},
  author = {sunny thakur},
  url    = {https://huggingface.co/datasets/darkknight25/Advanced_SIEM_Dataset},
  note   = {Synthetic SIEM security-event dataset}
}

Original dataset licensed under MIT.

Downloads last month
42