At my company, we have implemented a CloudWatch dashboard to track errors that occurred in the last 24 hours. However, this includes all types of errors, such as no data caused by the filter date being set in the future.
We are more interested in errors related to development, such as errors in calculated fields due to columns that are no longer available in the dataset.
Is there a way we can filter these types of errors in CloudWatch?
Hi Duncan, thank you for your time! I’m reviewing your response, and I think it would be useful to first send QuickSight logs to CloudWatch. I found here that I can use EventBridge to send the events, but the supported events listed don’t include dashboard errors.
However, this gave me an idea: I should be able to replicate the VisualLoadErrorCount using the metric filter you mentioned, but I’m not sure how to get the error logs in CloudWatch to reproduce the metric.
I have never attempted to create something like this with CloudWatch but my assumption would be that you need something that will read the logs and search for keywords then pass that to CloudWatch.
I would suggest looking into using a Lambda function to pass the values to CloudWatch.
My main issue is figuring out how to locate those logs. If the only way to send logs from QuickSight to CloudWatch is through the events supported by EventBridge, I’m affraid that won’t be enough to capture the types of errors occurring when rendering visuals on my dashboards.
The CloudWatch metrics should obtain the QuickSight logs from somewhere, but I can’t find where…
Hi @duncan , that’s exactly the solution we implemented in my team. The issue is that VisualLoadErrorCount is not enough for us—we want to dive deeper and retrieve the error log itself, not just the error count.
Hi @albmargar,
It’s been awhile since last communication took place on this thread, were you able to find a work around for your case or did you have remaining questions?
If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.
Hi @albmargar,
Since we haven’t heard back, I’ll close out this topic. However, if you have any additional questions, feel free to create a new post in the community and link this discussion for relevant information if needed.