Did you make any changes to the VizAlertsConfig/ScheduledTriggerViews workbook/sheet? Add any filters? That could account for it, if so.
I didn't change that workbook for the last months.
The only thing that has changed, that we updated our tableau user licences, but I don't know what is going on.
The "MarketngDaily" is a "test_alert" - but I don't get any notification on failure.
If I assign an existing subscription to the view - it works.
"test_alert" is broken for me
1 of 1 people found this helpful
Hey Taulant. Okay, so I think we're gonna need to look at the logs, since this problem refuses to have an easy answer. I'd shoot off one more "test_alert" run during a time when no other alerts are scheduled, then could you post a redacted / cleansed version here? My suspicion is that the alert is not being picked up at all, because if it is, we should certainly see an email of some kind if it's actually being triggered. If it is being picked up, the most likely reason you're not getting anything is that there's no data in the viz, or the Email Action value isn't 1 for the rows it contains. If it's not either of those, then something much weirder is happening. But we'll know once we see the logs.
Hey Matt, thanks for your answer! Unfortunately we had some time delays due to corona
I'm new pretty new in the Tableau enviroment - Where can i find the logs that affect Vizalert?
I'll try to search them and post a version here.
thanks for your help!!
No problem, and sorry to hear that! :/
The VizAlerts logs are separate from the Tableau logs. Whatever folder you run VizAlerts from, the logs will be in a \logs folder directly under that location.
Do you have any ideas on what is happening over here? You're actually my last hope
Is it a solution to delete and install vizalert again? (would hate to that)
Sorry, I had a reply half-typed, then lost track of this...
Are you running VizAlerts within five minutes of adding the test_alert comment? They expire after that and would not show in the list.
What I would suggest is this, in this order, done within thirty seconds of each other:
1. Add the test_alert comment to your viz
2. Manually export https://server/views/VizAlertsConfig/ScheduledTriggerViews?:format=csv
3. Run your VizAlerts.exe / .py process and see what the logs say
If (2) results in the subscription id being negative, it successfully picked up the test_alert and you should see it in (3). If, however, (3) tells you that there are 0 results again, we need to look more closely at the CSV results from (2) that might account for VizAlerts not picking it up. It's almost unheard of that there'd be an issue in the source itself that would cause this, so it's 99% certain to be a problem of weird data conditions or something like that.
first, thanks for your help! I'm not used to such a proactive community - great to see! Let me know if I can help somehow !
VizAlert runs every minute and I used viz' that are working if I schedule them with a "Vizalert-Deactived-Mail-Subscription-Schedule". But they don't give any response when I use "test_alert"
I followed your steps:
- ran the alert on 2 different viz'
- subscription id was negative
- logs tell me that there are 0 results
- --> lets look more closely at CSV (In the xls you'll find the test_alert response & the working vizalert-schedule response)
Thanks Taulant. I must confess that I find absolutely nothing wrong that could account for this behavior. In the logs when you processed these alerts, did it say "Processing a total of 0 alerts", as it did before? Or did it say "Nothing to do! No rows in trigger data from file"? The former means that we still have the baffling problem where the test_alerts are not being picked up at all, but the latter means they are being picked up, they just don't have any data exposed to do anything with.
Taulant, are you running VizAlerts via the exe binary, or the python script? If you are using Python, I have made some edits to the vizalerts.py file that will give us additional logging to try and track down where the problem is occurring. Just rename the original to "vizalerts.py.orig" or something, and copy this into your VizAlerts folder. If you're using the Windows executable, I unfortunately won't be able to make the same logging additions, as my current build environment is broken and I don't have time to fix it.
vizalerts.py.zip 5.3 KB
Thanks Taulant, that's really helpful. I think this is a locale issue. The problem seems to occur in line 321 in the version I sent you:
if line['is_test'].lower() == 'true': alert.is_test = True else: alert.is_test = False
What's happening is that this test never comes back as true in the evaluation. The text "TRUE" from the CSV file exported from the VizAlertsConfig workbook, when converted to lower case, does not become "true", but may be substituting other characters, so that the result is always that alert.is_test is always False.
We can test this by:
1. Checking the values for the is_test column in the raw CSV file from VizAlertsConfig, to first ensure that it's correctly set to the string "TRUE" for the two negative subscription_ids (I believe this is the case, but since you've sent me XLSX files rather than the text files, I can't be certain that some other conversion hasn't happened).
2. Running a quick test in Python: What does 'TRUE'.lower() evaluate to in your environment? And does 'TRUE'.lower() = 'true' evaluate to true?