Our primary use case is logging for everything within the company. We have a custom LogShipper, and for whatever deployments we have, we add the LogShipper into our containers, apply customer configurations to parse log files, and send desired fields to ChaosSearch. We then review logs on ChaosSearch.

During my time at the company, I didn't see any improvements from using ChaosSearch. We faced some struggles, and it's unclear whether the problem was with the search function itself or due to incorrect configuration by our team.

ChaosSearch is considered a cheaper alternative to Elastic. The decision to choose this vendor was likely influenced by its lower cost, especially as pricing was a major concern. It also provides the same tooling set as Elastic, including open-source Elasticsearch and Kibana query language.

The user interface could be more intuitive and requires improvement. The search function often feels wonky, making it difficult to find specific messages. There should be documentation or feature enhancements to aid in more accurate searches.

I have been using ChaosSearch for a little over a year.

ChaosSearch appears to be stable, as I have not experienced any crashes or downtimes.

Scalability-wise, I haven't seen any issues with ChaosSearch, although finding specific messages is challenging due to limitations with searching logs.

I haven't heard about any technical support being provided for ChaosSearch.

Neutral

Before ChaosSearch, some teams might have used OpenSearch. However, ChaosSearch has become standardized across the company.

The initial setup was handled by another team, and they provided the necessary installation packages and configurations, so I have no personal experience.

The setup and maintenance are managed internally by another team within the company.

ChaosSearch provides the functionality expected for logging. That said, it's challenging to find the specific messages needed.

Pricing was a significant factor in choosing ChaosSearch, especially as an alternative to more expensive solutions like Elastic.

The company might have considered Elastic and OpenSearch, and the primary reason for switching was cost.

I am not familiar enough with search solutions to compare ChaosSearch to others critically, but OpenSearch might be preferable due to its open-source nature and integration with AWS.

I'd rate the solution six out of ten.