![]() I want aggregation on multiples, not one terameter. We have three buckets rolled by hundreds of people and I want to see use cases for an individual to determine where I need to customize and provide more room. ![]() I get my KPIs in a bucket usage for yesterday but I'd like to see them by a particular date and week. I'd also like an improved UI because it hasn't significantly improved in a few years and we want to see it at a more granular level. If you go a bit beyond AWS products even if they're hosted on AWS, CloudWatch doesn't work very well. That would allow us to build our own custom solution because that is the biggest limitation of CloudWatch. It would be beneficial for CloudWatch to provide an API interface and some kind of custom configuration because everybody uses APIs now. Suppose Snowflake says we'd get all the same things with MongoDB such as APIs, hookups, or even monitoring. It's challenging to use one monitoring tool for S3 and another monitoring tool for Snowflake. For these, CloudWatch is good but a little basic and additional monitoring tools are required. ![]() We have many databases such as MongoDB and SQL Server, RDS, and PostgreSQL. Snowflake is a SaaS product hosted on AWS, but using it with CloudWatch still doesn't give us the support we need so we rely on separate monitoring. Even though the product works well with most AWS, it is a nightmare to use with Snowflake.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |