Suspicious Activity From Logs

Problem Statement

Suspicious Activity From Logs Problem Description Application logs record how users interact with a payment service, and they can be used to spot accounts that are unusually busy. You are given a log file as an array of strings. Each entry records one money transfer and is written as three whitespace-separated fields: "sender_user_id recipient_user_id amount" sender_user_id: the user who initiates the transfer. recipient_user_id: the user who receives the transfer. amount: the amount transferred. All three fields are strings of decimal digits. The log entries are given in no particular order. A user is involved in a log entry when that user is the sender of the entry or the recipient of the entry. A user is suspicious when the number of log entries that user is involved in is at least threshold. If the sender and the recipient of an entry are the same user, that entry counts once for that user, not twice. Report the ids of every suspicious user, in ascending numeric order. In