Lacework

Discussion of Lacework across the recent multi-week window was almost entirely negative, with commenters raising no praise themes at all and concentrating heavily on technical frustrations. Bugs dominated the conversation, appearing across every sampled mention and covering a wide range of surfaces including Terraform provider crashes, deprecated argument warnings, cloud-init failures, and Helm chart template inconsistencies. The sheer uniformity of complaint across different integration contexts suggested to readers of these threads that quality-control issues were not isolated to one area but felt systemic.

Reliability and integration concerns formed the second tier of recurring criticism. Several mentions described failures when connecting to cloud infrastructure, with one commenter detailing an inability to read from a configured S3 CloudTrail bucket and noting difficulty even reaching support through the Fortinet portal. Integration-lacking sentiment appeared to reinforce the reliability complaints, as commenters seemed to encounter broken or outdated documentation alongside the technical errors, compounding frustration.

The score trajectory tells a story of brief, unstable recovery followed by a longer decline. Sentiment started low, edged upward through mid-summer to a notable peak in late July, then fell sharply by mid-August and continued deteriorating into early 2026. That late-July uptick stands out given the surrounding context of complaints, though the small mention counts at each point limit how much weight any single reading can carry. The overall direction since that peak has been clearly downward.

Opinion was less divided than simply uniform in its negativity. There was no visible camp defending the product or offering counterpoints in the sampled discussion. Where differences existed, they were in degree of frustration rather than in sentiment direction, with some commenters describing workarounds while others reported hard blockers like provider panics and deployment failures.