Zendesk resolved the Explore feature errors by implementing effective indexing strategies. This action restored the query performance to expected levels, resolving the errors customers were experiencing when creating new reports and datasets.
The issue stemmed from a performance degradation after a database infrastructure upgrade, which removed query caching. By analyzing the problematic queries and applying indexing strategies, Zendesk was able to fix the issue. Additionally, they plan to improve monitoring systems and investigate further optimizations to prevent similar issues in the future.
On August 8, 2024, Zendesk experienced a service incident affecting some customers on Pods 17, 18, 28, and 29. These customers encountered errors when trying to create new reports using the Explore feature, impacting their ability to generate…
The root cause of the Zendesk Explore feature incident on August 8, 2024, was a performance degradation following a database infrastructure upgrade. This upgrade removed query caching that the system previously relied upon, significantly slowing…
During the Zendesk Explore incident on August 8, 2024, a workaround was available for customers experiencing issues. Users could create a new report by cloning an existing report and editing it, although creating new datasets was still not…
To prevent future Explore feature incidents, Zendesk is taking several steps. They plan to improve their monitoring system with specific alerts centered around SQL query latencies to catch performance issues early. Additionally, Zendesk is…