Feature ideas

Currently Ocean exposes Prometheus metrics at /metrics/. This feature request tracks adding an out-of-the-box ServiceMonitor manifest to the Ocean deployment (with appropriate labels, namespace, and endpoint configuration) so users can enable metrics scraping immediately without extra work.

Get AI-assistance when building calculation property, reducing the complexity of writing JQ manually

We have multiple different types of component . Currently we either need to model them as entirely separate blueprints or we try to merge them into one common shared blueprint. The latter has proven to be a bit unwieldy, when differences arise between types they tend to bleed through in the Port UI in certain places making the UX for the user a bit confusing.

The naming standards for some blueprints and their properties are inconsistent. If we look at something like the ADO Integration and the blueprints. * ADO Project - BP Identifier: "project" * ADO User - BP Identifier: "azureDevOpsUser" Additionally if take the ADO User BP identifier, it uses camel case whereas auto generated properties will utilise snake case. As a builder, by improving the naming standards/conventions, this would help remove ambiguity around things like mapping relations, utilising properties in widgets etc.

For some use cases the 30 character limit is restrictive and limits the capacity for some advanced workflows for auto-generating blueprints from a service prepended with some prefixes. An increase in the character limit would enable advanced use cases/workflows without having to resort to brittle workarounds.

Currently when configuring an aggregation Port can apply filters via "query" to the target blueprint. It would be useful if Port could apply filters to the source blueprint as well to only do the aggregation for specific entities.

Currently number fields don't have any formatting options. It would be nice to be able to declare how each numeric field should be displayed, e.g. the number in the picture would be nicer written as 13,850,834. Currency signs and decimal places would also be useful. https://cloud.google.com/looker/docs/custom-formatting Looker has good support for this as an example.

There is a not well documented 'jqQuery' option which appears to be usable in some 'value' fields but not others. It would be nice to document where this option may be used and also broaden the utilization to more areas like filters and queries

Currently, there is no option to add a mirrored property when the dependent blueprint property is a calculated item. Example: I have a blueprint with a URL-calculated property to display a Grafana dashboard. It would be beneficial if we could include this dashboard URL as a mirrored property for another blueprint that depends on it.

Today we have a Terraform & Pulumi provider Some companies use K8s to manage configuration using tools operators, so it would be great to have a Port operator, which will allow creating Port CRDs (Blueprints, entity, pages, etc) that contain the IDP configuration