Anomalies in Microservice Architecture (train-ticket) based on version configurations

The work contains ten datasets containing monitoring data (logs, Jaeger Traces and Prometheus KPI data). The datasets contain monitoring data from train-ticket, a benchmark system for microservices. The dataset includes a short description with explanations of identified anomalies. The structure of the folder is as follows: <strong>&lt;changed-microservice&gt;_&lt;third-party-library&gt;_&lt;version&gt;_&lt;date-when-data-was-collected&gt;</strong> Each folder stores the respective data: Logs: original log file: LOGS_&lt;change-microservice&gt;_&lt;third-party-library&gt;_&lt;Version&gt;.txt parsed log files required for Loglizer (anomaly detection technique): LOGS_&lt;change-microservice&gt;_&lt;third-party-library&gt;_&lt;Version&gt;.txt_structured.csv LOGS_&lt;change-microservice&gt;_&lt;third-party-library&gt;_&lt;Version&gt;.txt_templates.csv KPI Data: Monitoring_&lt;change-microservice&gt;_&lt;third-party-library&gt;_&lt;Version&gt; Traces: Traces_&lt;change-microservice&gt;_&lt;third-party-library&gt;_&lt;Version&gt;