Feature ideas

Introduce a way to trigger alerts when a data source sync fails, allowing teams to integrate Port with their monitoring/observability stack. This could be achieved via automation trigger (add a trigger for “sync failed” events scoped per exporter and/or per kind). Or, via a built-in alert configuration (add an alert configuration section within the Sync Status page, and allow users to define notification rules for failed syncs).

Request to add first-class support for the AWS::ECS::TaskDefinition resource type to the AWS v3 integration so ECS task definitions can be ingested as their own kind and mapped into Port blueprints, similar to the existing support for AWS::ECS::Cluster and AWS::ECS::Service. Today we can only access the task definition ARN via AWS::ECS::Service (.Properties.TaskDefinition), which is not enough to understand the actual container configuration or link services to internal components and images. The feature should expose key ECS task definition attributes so they can be mapped into a dedicated blueprint and used for catalog relationships and scorecards. Specifically, we’d like to ingest: TaskDefinitionArn Family Revision Status ContainerDefinitions (for image and container config) Cpu Memory NetworkMode RequiresCompatibilities Tags

Add option to specifically resync a predefined list of resources & do a scheduled resync only for a selected list of resources