Share your experience using Trellix Enterprise Security Manager - Enterprise Log Manager [EOL]

We use the solution as a login platform. We have a lot of microservices, and we get log records from there, which we host on Amazon OpenSearch.

There are a couple of cool features. The service provides vacuum storage for cold or ultra-warm data. We retrieve historical data with just a click of a button to move it from cold to hot or warm because it's already stored in the backend storage, S3.

Some configurations or settings are not accessible to end users, as OpenSearch Service is a managed service. It would be beneficial to have some level of customization available in the managed service, tailored to the specific use cases of the end users. Currently, there are strict controls. For instance, if you wish to adjust cluster settings or other parameters, it's challenging for AWS to modify them.

The real-time analytics provided by Amazon OpenSearch Service can significantly improve your decision-making processes. Initially, we struggled to determine the correct cluster size and monitor various metrics. You can easily observe metrics like JVM and CPU usage on the monitoring dashboard. This information helps choose the appropriate tool and understand its support and extension capabilities. It would be even better if the service included built-in alerting based on these metrics. If an issue arises, you must manually check the cluster's status. Implementing preconfigured alerts for critical metrics like JVM and CPU usage would significantly enhance the service's usability.

I have been using Amazon OpenSearch Service for 2 years.

The product is stable.

The solution's scalability is excellent. You can scale up with Ruby on Rails deployment. It's pretty effective. If you wish to upgrade anything, it's super efficient. For example, you can trigger a global deployment test, and you'll experience no downtime.

We receive good support from Amazon OpenSearch Service. You encounter difficulties resolving issues. They are satisfactory in terms of communication and response time.

Neutral

We couldn't find a suitable solution for authentication. Among the various options considered, the primary reason for choosing Amazon OpenSearch Service was our familiarity with AWS, as we already host our applications on this platform. Another significant factor was the high licensing costs. Upgrading to Elasticsearch's latest version incurs high licensing expenses. Also, the cost of using Splunk was high. Amazon OpenSearch Service was the most suitable option considering both the ecosystem and cost factors. Additionally, since Elasticsearch and OpenSearch are similar, transitioning to OpenSearch from Elasticsearch was relatively easy. This transition allows us to maintain a consistent user experience while remaining within the AWS ecosystem without incurring excessive costs.

Creating a cluster is hard, but sometimes, when you want to make a VPC web cluster, it is difficult to expose the dashboards. You can see the proxy settings if you want to integrate with Okta. We had a real challenge with setting up the integration with Okta. The cluster creation was not complex, whereas the integration took us months to resolve. Deployment took two to three months to complete.

The cluster setup is not complicated, especially if you want it taken care of with Okta and the dashboard exposed via proxy.

A managed service is more costly than a self-managed one. The cost isn't about monitoring; it also involves human resources and labor cost savings. For instance, if you previously used self-managed Elasticsearch, you need to handle all upgrade strategies and cluster management yourself. This incurred a significant cost, which makes tools like OpenSearch valuable. OpenSearch is designed to save your developers or users to manage the infrastructure.

It should be easier to integrate with other AWS services.

I recommend the solution, but it depends on your specific use case. For example, if you plan to use it for logging or centralized login setup. Thus, I suggest assessing your needs based on data characteristics. For example, if your data exhibits fluctuating volumes or varying patterns per day. Managing OpenSearch entails addressing various aspects, including site templates and lifecycle policies. Therefore, ensuring all necessary components are in place is crucial.

It's easy for a person to learn to use Amazon OpenSearch Service for the first time. There would be a learning curve, and it might take some time in terms of managing the internals of the OpenSearch cluster, but if you just want to use it as an end user, it's pretty intuitive. You can navigate around to see the options quickly.

Overall, I rate the solution a seven out of ten.

I use it for developing scripts - UI scripts and API tests. 

We use it for both API testing and UI testing. It's been okay. Apica claims to have expertise similar to LoadRunner, and we were interested in trying it. 

Overall, it's functional, and we get good support from the Apica team since it's a newer product. 

I like the transcript download feature. And with UI scripting, it's helpful that Apica handles a lot of the backend work automatically. I don't have to tag everything manually, though I can tag elements later if needed. It's really good at recording the steps.

Moreover, it is easy to set up and configure tests in Apica.  I really like how it presents the results in a sheet format. That's very helpful.

It's not very user-friendly.

There are more areas of improvement as well. We could use more detailed information in the request and response sections. 

Also, with correlation, there are times we can't correlate values in the header, and that would be a helpful improvement.

I have been using it for more than one and a half year. 

It doesn't crash. So, for me, the stability is good. 

Scalability is not bad. We have more than 20 end users using it in my company. 

I would rate the scalability an eight out of ten. 

The customer service and support are really helpful. 

Positive

I used LoadRunner and JMeter. 

The initial setup is easy. 

It is not a famous product, and it still needs to be worked on. JMeter is the best tool in this space. Like for API testing. 

Overall, I would rate Apica a seven out of ten.