the last one looks OK. (You can think of it as patterns for searching files on disk.) Have you created an ingest rule to ingest this custom log source?
just to be clear, is “xxx” in your paths a replacement for something sensitive, or a part that might have multiple values (like a wildcard)? If taken literally, please note that you log ingest rule covers the second of custom log sources in the first post, and the rest are not matched (Merchants vs xxx).
Can you say what is the exact full path to the log file you try to ingest? Knowing that I could match it with the rules.
It looks to me that the custom log source rule is perfectly OK. Please remember that custom log source name (not the file name) is your “log.source” attribute, which you can choose in your ingest rules.
Just for your information - you should also have a built-in rule (disabled on default) which ingests all custom log sources - you can just enable it if you find it suitable.