Jira Service Management vs. Opsview Monitor

It will be well suite for large Organization where many team members involved from various Geographical location's in a single project or program as that would help greatly with this Agile Project Management tool. And, its may not be the right option for small organizations and also less of the need for co-located teams as well.

Incentivized

If you know Nagios or Nagios-like monitoring systems, OpsView will be really easy for you to learn and manage. Migrations process will be relatively easy. You're getting great U/I that will speed up adding new objects to the system and present data in a clear, organized way. In addition it's easy to create dedicated dashboards for your clients.

Incentivized

• Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
• Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
• Allow multiple different entry points and work flows for as many different needs your teams / company have

• Easily extensible. We write many of our own monitoring plugins for Opsview and use open source Nagios community plugins as well
• Quick to deploy. Don't need to worry about all of the dependencies that you need to with something like Nagios
• It just works. Most of the housekeeping tasks are completely automated
• Nice visualizations and dashboards

Incentivized

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

Incentivized

• pricey
• build in cloud monitoring packs need to be improved
• smb version is missing some powerfull features

Incentivized

I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.

I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.

Incentivized

Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.

Incentivized

Nagios and Zabbix - Opsview is much easier to setup and operate than both of them. SolarWinds Orion - Opsview is much more economical

Incentivized

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized

• helps to discover and remediate infrastructure problems quickly
• helps to present SLA diagrams for clients
• speeds up deployment proces for new solutions

Incentivized