May we add fingerprint in file source context for log event?

[WENPIN1]

Dear Vector developer,

I'm seeking a unique identity for file source not changed until the content is truncated after application restart.

For example, an application keeps appending log events as a same file until this application has been restarted (e.g. java garbage collection log).
$./myApp > myapp.log &

If I am unable to set the output file name("myapp.log") into a unique name, it won't have a unique file name in the log event while using vector file source.
I think fingerprint is a good alternative for this point when the log file name is restricted.
https://vector.dev/docs/reference/configuration/sources/file/#fingerprint

It is suggested to have a fingerprint in the output log events for uniquely identifying the log file for subsequent use.
https://vector.dev/docs/reference/configuration/sources/file/#output-logs

Thank you!

-WENPIN