erwin Data Modeler vs. Grafana

I have had a chance to use few other data modeling tools from Quest and Oracle, but I am most comfortable using erwin Data Modeler. They understand your data modeling needs and have designed the software to give you a feeling of completeness when you are designing a data model.

Incentivized

If I was starting over on an Observability platform, Grafana would be my number 1 choice due to the flexibility and ability to act as a single platform either on its own or combining multiple data sources. The trick however, is that it can be fairly complex to learn and setup, so time is needed to make it a successful implementation. There is a level of cognitive load required

Incentivized

• Reverse Engineering: I love the way we can import an SQL file containing schema meta data and generate ER diagram out of it. This is specifically useful if you are implementing erwin Data Modeler for an existing database.
• Forward Engineering: We use this feature very frequently. Where we do database changes in our physical and logical data models and then generate deployment scripts for the changes made.
• Physical vs Logical Models: I like to have my database model split into physical and logical models and at the same time still linked to each other. Any changes you make to logical model or physical model shows up in the other.

Incentivized

• 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

• Cost is the single largest barrier to entry with this tool.
• Would like to see a greater variety of export options available for use outside of the tool, for example as a vector graphic.
• Support has been uneven at times.

Incentivized

• There are some settings which we can't configure from UI (Web Console).
• We've open[ed] up configuration files in command line text editors and manually do the settings e.g. LDAP/SSO configuration.
• In terms of visualization, it's best, but it doesn't support log analysis otherwise it could destroy business of all other visualization tools.

I had a lot of experience using erwin Data Modeler for designing data models. I think it's pretty intuitive and easy to use. It has enough features to represent your database requirements in form of a model.

Incentivized

It is infinitely flexible. If you can imagine it, Grafana can almost certainly do it. Usability may be in the eye of the beholder however, as there is time needed to curate the experience and get the dashboards customized to how it makes sense to you. I know one thing they are working on are more templates, based on data sources

Incentivized

CA customer support and our account manager have been able to support us with any issues that we have had, from managing our serial keys to issues we logged tickets to resolve. There are aspects of key management that have made it difficult over the years but support usually has worked with us.

Incentivized

Not listed, but I've only used alternatives built into something like the Squirrel SQL editor. That one is semi-functional but lacking many features and, in some instances, just plain wrong. The only pro there is that it's freely available and works over ODBC. I've tried some of the other free ones like Creately but didn't have much success.

Incentivized

Grafana blows Nagios out of the water when it comes to customization. The ability to feed almost any data source makes it very versatile and the cost is great.

Incentivized

• It is difficult to assign a monetary value to it. The initial learning curve was fairly long.
• It allows us to have better support documentation.
• It allows ease of communications between functional units.

Incentivized

• Time-consuming reports reduced
• Spotting trends in services
• Preventive maintenance

Incentivized