Grafana vs. JMP

Just about any organization with more than one server and more than one cluster as it scales very well. Configuration of the application takes time and finesse to fine tune to where the balance of load time and getting data quickly meets. The plugins add load time but fine tuning for the application to meet demand needs nailed down at implementation

Incentivized

Many organizations have seen their analytical capabilities, and the results from them, plateau. Of these, we've observed, that most of them didn't appreciate that they could do (even) better. These companies should definitely consider JMP. Any company that is research-based can benefit from accelerating their research, learning more in less time, effort and cost, with JMP's tools. Basically, any organization that is hungry enough for improvement to seek out better ways is suitable for JMP. Those who are happy with their current performance are not likely to consider the changes, though they were not major impediments by our clients, required.

• Alerting through many different medium as Slack, Email, Webhook etc
• Beautiful and unlimited number of dashboards to view your metrics and tweak them as you please
• Log aggregation and powerful Logql to filter and view your logs
• Microservices monitoring
• Large number of plugins and data sources to collect your metrics from almost anywhere

Incentivized

• Graphs are more detail-oriented and contain statistical inferences.
• Everything is drag and drop. Pretty much easy to use and handle and also to learn.
• Importing and exporting the results are easy and they can be attached with any other tool for processing.

Incentivized

• Documentation needs to be more clarified since it can be confusing for beginners
• Notification alert message templates need to be simplified

Incentivized

• Loading a large amount of data is very tedious as it takes a lot of time and it crashes very frequently.
• I dislike the limited options they have in terms of statistical models or analysis tools.
• Variable value designation is a big problem in JMP, the software fails to recognize the type of data when it comes to the numeric value.

Incentivized

I've mentioned this earlier, but the licensing agreements are very prohibitive. I work with a company where my role has become less and less doing my own analytics and more and more trying to help other people in that role. As we are bringing more people "up to speed" it's hard to justify licenses for 2-3 people when they aren't full time, Six Sigma black belts just looking at stats all day. A floating license option would make this a no-brainer, since these people could continue their other work and add JMP usage as they grow their skills, but this is not something JMP/SAS has offered.

Great usage in terms of monitoring of any application from backend to frontend and even any AWS resource via cloud watch and other connectors. Easy to use and configure personalised dash boarding and alerting features. Cost efficient and easy to setup and run, no mazor scaling challenges in terms of managing and maintaining the stack, easy to configure via Prometheus, influx and other connectors

Incentivized

The GUI interface makes it easier to generate plots and find statistics without having to write code. The JSL scripting is a bit of a steep learning curve but does give you more ability to customize your analysis. Overall, I would recommend JMP as a good product for overall usability.

Incentivized

The helpful tips are great for new users. I am always able to find solutions to a tool I am working with through the hep section. And my area has a users group that meets each quarter to share ideas and view upcoming JMP revisions.

Incentivized

I have not used your online training. I use JMP manuals and SAS direct help.

Grafana is more flexible, readily adopts other tools frameworks instead of forcing you to use their agent, doesn't force you into Vendor lock-in, and embraces open source, self-hosted, and Enterprise. Similar companies would like you to use their specific tooling and don't offer nearly as much flexibility. The other thing I like about Grafana is their storage usage is much lower compared to similar tools and competitors

Incentivized

We actually use both JMP and IBM SPSS, but I think JMP's complexity lends itself to more in-depth statistical analyses. SPSS is designed for that as well, but we tend to use it more for quicker analyses, and we have found that JMP is far more powerful.

• It has kicked out some of our paid monitoring and visualization tools.
• Now Monitoring, Visualization and Alerting is being done in a single platform.
• It made monitoring and visualization very easy for us.

• JMP has resulted in literally millions of dollars in ROI due to identification of correctable errors.
• Use of JMP control charts JMP has greatly simplified and improved interpretation of Lean, FMEA, and PDSA type analyses.
• Use of JMP has enable the testing and subsequent selection of 'best practices' saving uncounted hours in false starts based on 'collective experience'.
• The down side is that JMP is not a 'magic box', one still has to take care in applying the tools properly. Moreover, time-consuming approaches using JMP may still be the 'order of the day', because the service (even power user) is unaware of significant shortcuts available for free on the JMP community website.

Incentivized