I am exploring Sentry, New Relic, and Azure Monitor. The tools can be used to monitor our solutions. We want to improve the reliability of the applications.

Sentry is a service to which we send all the application alerts, which is like an alert management app.

I use Sentry for internal applications from our front end to our back end code and to capture past services, tracing, calls, and the time it takes to process requests and updates. We're integrating with Gib so from the code base side of things we can trace changes, bottlenecks, etc. I'm a senior software engineer.

Our primary use case for this solution is web application monitoring and providing developers access to live error logs, error tracing, and some metrics without providing them real-time production access. So it's a great visibility tool for the developer team.

I use Sentry to monitor application performance. 

My primary use case has been in front-end and in back-end applications. 

My main use case for Sentry is to catch front-end or back-end application errors and report them.

We use the solution for error tracking. We integrate it with applications to receive notifications for errors automatically.

We are in banking, so we need a lot of protected data. Sentry allows us to restrict users from accessing certain data.

It's deployed on-premises, and we have multiple servers. 

There are eight people in our team, and they all use Sentry. We have another team of six people who are also using it.

We have plans to increase usage in the future.

We deploy CyberArk for some companies and projects. So, for example, if a company wants to protect its data, the CyberArk PAM solution can be implemented. So, in that case, we take that project and implement it. So, we don't go with the old Sentry because we have implemented a new PAM solution. We deploy the solution both on-premises and in the cloud.

The solution has two primary use cases. First, there are two different certifications, Defender and Sentry, in CyberArk. Sentry is how to deploy the PAM solution into the existing environment. For example, for all the privileged accounts, there's an administrative account, administrative access to the AD accounts and domain accounts, dash share accounts, etcetera.

If someone needs to make changes in the admin server, they must request access, and the records will go to the server owner or domain control owner, who needs to approve that access. Additionally, there is threat analysis for the suspected activity that will be triggered to another system. So, the session, which got connected to the servers, will be terminated at that particular time. Once a suspect alert is generated, the session will be terminated and no longer be connected to the server and no longer have access to the server.

Our primary use case is for user access to a particular database of specific tables. We are using the Sentry privileges feature.