cf-toolsuite / cf-hoover-ui

A simple dashboard display for metrics gathered from a cf-hoover instance

VMware Tanzu Application Service > Hoover UI

• Background
• Prerequisites
• Tools
• How to
  • Clone
  • Build
  • Manage configuration
  • Run
  • Check code quality
  • Deploy to Tanzu Application Service
  • Consume endpoints
• Credits

cf-hoover-ui's Issues

Refine filters for date/time columns in detail views

While we can filter on all fields in detail views, we should take into account idiosyncrasies of date/time columns. It is arguably more desirable to set a range than a specific date/time.

Let's refactor the filter implementation in each of the application and service instance detail views to allow users to set a range. To be as flexible as possible when defining a range, I'm contemplating adding start and end DatePicker(s) to the header row for date/time columns.

Helpful links to inform implementation:

• https://vaadin.com/docs/v8/framework/datamodel/datamodel-providers.html
• https://vaadin.com/components/vaadin-date-picker/java-examples
• https://vaadin.com/forum/thread/16957339/vaadin-8-grid-and-dateprovider-filter-for-date-range

Large data affects few pages stop rendering

Cf-hoover-ui stop showing snapshot-detail-services, snapshot-detail-application, or snapshot-detail-users when the data in those pages reach certain large limit.

Color code the Spring dependencies in the detail and dependency frequency views

It would be nice to provide a red-orange-yellow-green color coding correlated with: completely out-of-date, nearing end of support, in-support, and most recent Spring versions detected.

E.g.,

For versions of Spring Boot detected

Green is 3.2.x
Yellow is 3.0.x to 3.1.x
Orange is 2.7.x
Red is < 2.7.x

We'd similarly color code for all other Spring projects in eco-system we wish to report on.

Going to investigate using this at work, will provide feedback / use-cases.

This is a sporadic and generally useless comment, but, just wanted to say I'm inspired by your other projects like cf-butler, and I'm excited to try this out too. We're getting a lot of interest in cloud foundry internally at work, and value-stream mapping is getting more and more important. Just wanted to say I'm looking forward to trying this out, and will try to provide constructive feedback and use-cases.

I will start using this and get feedback, but I can already anticipate my boss's boss requesting features such as...

• Ability to aggregate data by selecting multiple orgs (or querying on annotations)
• Retaining historical data
• Calculating "trending" data, like onboarding rate of apps, etc.
• Listing total AIs/SIs, broken down by service, with an ability to setup filtering rules for non-billable SIs like Spring Cloud Config instances
• Querying for apps which haven't been re-pushed since X-days
• Combining this data with "showback" configuration, e.g. configuring a price plan for application gb/hr + configuring price plans for service instances

... but I promise I will be a good OSS citizen and file reasonable feedback with reasonable use-cases

Thanks for your time, I really appreciate it.

Update documentation to reflect rebranding

With the acquisition of Pivotal by VMWare, and the recent announcements regarding the Tanzu portfolio the README should be updated to reflect these updates. Some hyperlinks are now broken and will need to be fixed.

Add filtering in Detail Views

The Application and Service Instance Detail Views may contain more data than is consumable at a glance. Let's add filtering capability per column as in this example https://vaadin.com/components/vaadin-grid/java-examples/filtering.

Incorporate fallback behavior

E.g., in https://github.com/pacphi/cf-hoover-ui/blob/6d32fb034547b8d8b79941c1363c68f7c819a0ab/src/main/java/io/pivotal/cfapp/client/SnapshotClient.java#L10

We should add a fallbackFactory reference and implement the factory interface.

Do so likewise for UsageClient.

Dependabot couldn't find a build.gradle(.kts)? for this project

Dependabot couldn't find a build.gradle(.kts)? for this project.

Dependabot requires a build.gradle(.kts)? to evaluate your project's current Java dependencies. It had expected to find one at the path: /build.gradle(.kts)?.

If this isn't a Java project, or if it is a library, you may wish to disable updates for it from within Dependabot.

View the update logs.