It appears that the error message is that the VizAlerts can't find the .config\vizalerts.yaml file. When you edited the vizalerts.yaml file as described in the installation guide did you change the filename or extension at all?
Also, a couple of forums notes:
1) Please don't make multiple posts with the same question, that can result of overlap and confusion.
2) Most everyone who answers questions on the forums is a volunteer so we are answering questions when we can. The forums are not a tech support line with guaranteed response times.
3) #2 especially applies to VizAlerts which is a community-developed piece of software. If you are in need of specific support beyond what you can get here on the forums you could potentially arrange with my company (DataBlick) or with Tableau professional services (I'm naming two organizations that I know have done paid support for VizAlerts).
Also, questions asked here are expected to be answered here, not off-site privately through email or phone. This allows others who may have the same issue to follow along and possibly fix it. It allows input from other people, too, so asking others to contact you outside of the forums really doesn't help, so I would recommend removing your phone number...plus by posting it you allow spammers another way to contact you and that's never fun
Because VizAlerts is not supported there isn't the option to contact Tableau Support. Reading the documentation and asking questions here is your best free method of getting help.
Prashanth Badugu wrote:
MainThread - 2017-03-23 04:38:02 - [INFO] - LoggerQuickSetup - Logging initializ
ed, writing to .\logs\vizalerts.log_2017-03-23.log
MainThread - 2017-03-23 04:38:02 - [INFO] - main - VizAlerts v2.0.1 is starting
An exception was raised loading the config file .\config\vizalerts.yaml: (<type
'exceptions.IOError'>, IOError(2, 'No such file or directory'), <traceback objec
t at 0x02C53BC0>) Stacktrace: <traceback object at 0x02C53BC0>
MainThread - 2017-03-23 04:38:02 - [ERROR] - validate_conf - An exception was ra
ised loading the config file .\config\vizalerts.yaml: (<type 'exceptions.IOError
'>, IOError(2, 'No such file or directory'), <traceback object at 0x02C53BC0>) S
tacktrace: <traceback object at 0x02C53BC0>...
I'm guessing from the error message that the configuration file cannot be found. Does your VizAlerts 2.0 file structure look like this?
Thanks for the screenshot. I can tell from the screenshot that you've got file extensions turned off, can you use the View menu and make sure that you've got file extensions displayed (as in the screenshot below) and verify that vizalerts.yaml actually has just that as a file name and not something tacked on the end?
thanks for you response ..
i did check on the folder and had updated the folder options as mentioned above ..
below is the YAML file ..
# Local paths settings
log.dir: ".\\logs\\" # folder write dump log files to. Will be created if it does not exist.
log.dir.file_retention_seconds: 432000 # retain log files for default of 5 days
log.level: DEBUG # level of log verbosity
schedule.state.dir: ".\\ops\\" # file written to keep the last run state for schedules
temp.dir: ".\\temp\\" # folder to write temporary files to (csv, png for viz exports). Will be created if it does not exist.
temp.dir.file_retention_seconds: 86400 # retain temp files for default of 24 hours, mostly for debugging
# Email settings
smtp.serv: temailhost.tycoelectronics.net # name of the smtp mail server (change for production use; default is only set to "localhost" for ease of testing with PaperCut: https://papercut.codeplex.com/)
smtp.port: 25 # port to user for SMTP server (default is 25)
smtp.address.from: Tabserver-Dev-VizAlerts_DoNotReply@xx.com # default sender for all alerts mail
smtp.address.to: firstname.lastname@example.org # email address of admin to send failures to
smtp.subject: 'ALERT: VizAlerts failed to execute properly' # subject line in exception emails sent to admin
smtp.ssl: false # use encryption when connecting to SMTP server
smtp.user: null # username for account used to connect to SMTP server (null for no authentication)
smtp.password: null # password for account used to connect to SMTP server (null for no authentication)
# This can either be a plaintext password enclosed in single quotes, e.g. 'myp@ssw0rd'
# OR it can be a valid path to a .txt file containing the password, e.g. 'c:\users\mcoles\password.txt'
# Tableau Server settings
server: insights-dev.connect.xx.com # the Tableau Server instance your alerts will reside on. Recommend using the fully-qualified name, e.g. 'myserver.mydomain.com'
server.version: 10 # the major version of Tableau Server that this is running against (just ensures correct URLs in email footers)
server.user: xxx1S0156 # this is ANY user licensed in Tableau Server--it does not need to be an Admin. It must have access to download summary data from vizalerts.source.viz
server.user.domain: xxxxxxxx # the domain for the server.user account.
# Leave as null (no quotes) if Tableau Server uses local authentication
# Set to the domain if using AD authentication, e.g. 'mycompany.com'
vizalerts.source.viz: 'VizAlertsConfig/ScheduledTriggerViews' # Viz to pull list of alerts from. Must be of the form 'WorkbookURL/ViewUrl'
vizalerts.source.site: 'VizAlerts' # Site that the vizalerts.source.viz exists within. Leave as 'Default' if using the default site.
# Security settings
server.ssl: true # use HTTPS for Server connections (recommended, but left off by default for testing)
server.certcheck: true # if using HTTPS, validate the certificate (recommended, but left off by default for testing)
# If you turn this on you MUST specify a certificate bundle in server.certfile
server.certfile: E:\\Tableau\\Tableau Server\\SSL\\insights-dev_ssl.pem # Full path to the set of trusted CA certificates to verify your SSL certificate on Tableau Server in .pem format
# example: 'c:\\certificates\\cacert.pem'
trusted.useclientip: false # use clientip for trusted tickets verification
# This is optional. Please see http://onlinehelp.tableausoftware.com/current/server/en-us/trusted_auth_optional.htm
trusted.clientip: null # IP address of THIS host. Only needed if trusted.useclientip is set to true. Otherwise, just leave it null.
# SMS Settings
smsaction.enable: false # use these settings to enable SMS messages. If false, we won't even check them, and all SMS attempts will fail
smsaction.provider: twilio # the only allowed provider currently is twilio
smsaction.account_id: '' # account ID, for Twilio this is the account SID from http://twilio.com/user/account
smsaction.auth_token: '' # auth token, for Twilio http://twilio.com/user/account
# This can either be a plaintext password enclosed in quotes, e.g. 'eyJ0eXAiOiJKV1QiLCJhbGciO...'
# OR it can be a valid path to a .txt file containing the auth token, e.g. 'c:\users\mcoles\authtoken.txt'
# Processing settings
threads: 2 # Number of threads VizAlerts will use to process alerts
# Higher = More alerts process at once, increased server load
# Lower = Fewer alerts processed at once, decreased server load
# Content references within a single alert are processed serially
data.coldelimiter: ',' # Character used to separate field values in CSV files exported from Tableau Server
# Some regions use semicolons for this, in which case switch it to ';'
Thanks for sharing our community etiquette, Jonathan and Toby!
Prashanth Badugu, you will need to run VizAlerts in the context of the directory your .py script is in:
E:\VizAlerts> python .\vizalerts.py
The reason it is failing is because it is looking for the config file in .\config\vizalerts.yaml, one level under the path you are running it from, not the path that vizalerts.py lives in. So just change where you run it from and it should fix it.
The issues isn't fixed yet .. we are getting an error with -1
the error msg :Error
msg: MainThread - 2017-04-04 00:47:22 - [ERROR] - get_trusted_ticket -
UserWarning generating trusted ticket: Error generating trusted ticket
not sure why
We should be able to pass only the xx1S0156 but in our case we are
am I missing something in the config ??