Hi Community,
I have FeatureWriters creating log text files for me depending on various conditions.
If the conditions are not fulfilled the files are still generated but empty and emailer still sends those empty files as attachment.
How can i stop this from happening, so that only the log files with any values are sent as attachments with email.
Thank you
Solved
How to make Emailer to stop sending empty files
+2- Contributor
Best answer by nielsgerrits
We use different variants, but collect logmessages and write to logfile and the emailers is mostly the same in most workspaces.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+62
How I configured this:
- AttributeCreators creating log messages.
- Aggregator to concatenate these log messages into one text attribute.
- FeatureWriter to write temp logfile.
- AttributeRenamer to rename _dataset attribute to LogFilePath.
- Aggregator to merge logfile FeatureWriter with data FeatureWriter output.
- Tester to test if a logfile was written (LogFilePath has a value).
- 2 Emailer transformers, one with attachment, one without.
+2- Contributor
How I configured this:
- AttributeCreators creating log messages.
- Aggregator to concatenate these log messages into one text attribute.
- FeatureWriter to write temp logfile.
- AttributeRenamer to rename _dataset attribute to LogFilePath.
- Aggregator to merge logfile FeatureWriter with data FeatureWriter output.
- Tester to test if a logfile was written (LogFilePath has a value).
- 2 Emailer transformers, one with attachment, one without.
Hi Nielsgerrits,
Is it possible for you to share the setup screenshot?
What i am doing is entering data straight to the Featurewriter, which creates the file with filename+timestamp. (Timestamp uses a user parameter of python code).
A file name extractor extracts that name and the attachment filepath URL is updated accodingly.
+62- Best Answer
We use different variants, but collect logmessages and write to logfile and the emailers is mostly the same in most workspaces.
Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...
+2- Contributor
We use different variants, but collect logmessages and write to logfile and the emailers is mostly the same in most workspaces.
Thank you so much Nielsgerrits, its clear now what you were explaining earlier. Hopefully I can adapt it to my usecase.
+62
Thank you so much Nielsgerrits, its clear now what you were explaining earlier. Hopefully I can adapt it to my usecase.
Cheers :)
+2- Contributor
Another solution I found is to use the community made transformer caller filePropertyExtractor which gives various details about the file.
I check the file size and run through the tester, as I know that my empty files are less than 5 bytes(~1KB), anything bigger than that is sent to emailer and rest are not.
Just another way of doing the same thing :), for anyone looking this up in future!