Feature ideas

Currently Port does not have the ability to export action runs via the UI, only the API. It would be beneficial if an export button was added to the Runs History page similar to normal catalog pages.

Support streaming audit logs to a customer-managed data warehouse bucket, enabling customers to monitor Port activity in near real time.

Often I want to see when and by what a specific field was changed on an entity. The problem is we have some entities with hundreds or thousands of edits in the log. Tracking down the specific edit that changed that field last can be difficult. It would be really nice to see a breakdown of each of the edits to the entity that involved that specific field.

In addition to the general action runs audit log, a specific audit log for each action will be added to the "audit log" page Each action log will display as columns the general details of each run (ID, status, start, end) and also the specific inputs of the action inputted by the user who executed it.

Some customers would like the option to automatically report Port's information to an external SIEM system for security concern. https://www.ibm.com/topics/siem#:~:text=Security%20information%20and%20event%20management,chance%20to%20disrupt%20business%20operations . First and most important are the changes of Port's audit log

Make it possible to see login attempts (both successful and unsuccessful) in an organization's audit log

We now have multiple locations where we are using the API to update specific blueprints. Having all changes to blueprints made through the API under "Rest API" is too vague for us to know where specifically the change came from. It would be nice if we could include a name of the source in our blueprint change payload and then be able to see this reflect in the audit logs. For example: I change blueprint Service with a python script called "service_ changer.py " using a POST in the script - I can also pass into the body of the POST "updatedByAlias":"service_ changer.py " And then later, I can filter the audit log by "updatedByAlias":"service_ changer.py " to see all changes made through that specific script.

Provide audit log functionality for pages so that we can track which users create/edit/delete things like dashboards.

Problem When a self-service action creates another entity, the audit log shows the entity as being created by Port automation. While the action run itself contains the triggering user’s information, that context is not surfaced in the audit log. This makes it difficult to: Trace ownership and accountability Understand who initiated changes when reviewing audit logs investigate issues without jumping between audit logs and action runs Current behavior Audit log entry: Type “Port automation” Triggering user is only visible in the self-service action run details Expected behavior Audit logs should display the user who triggered the self-service action as the creator of any entities created by that action (or at least include them as additional context, e.g. “Created by Port automation (triggered by @username)”).

As a Platform Engineer launching a new dashboard in the Port catalogue I'd like to 1) track adoption and usage of the new dashboard/page and 2) have access to data so I can integrate my surveying tooling to survey the users who use the new dashboard. For big picture context. We are also a customer of DX who have a product called PlatformX. We have integrated this into our Self Service Actions. When a user (Bob) runs a self-service action via Port an event is fired off to DX saying that Bob did X event. DX looks to see if Bob is eligible for surveying based on the action (event) taken and if valid will send a survey to them personally on teams (MS Bot framework). This gives a very low friction option for Bob to provide feedback they might have otherwise not raised. We'd like to perform a similar integration but for important pages in the catalogue, like a newly launched dashboard. So, the user experience might be that Bob accesses the new port dashboard page for the first time and sometime later is pinged on teams saying "Hey we saw you used the ABC dashboard for the first time. Could you let us know what you thought etc..." Currently we don't have access to data that tells us who has accessed what pages in the catalogue at what time. Could this data/event telemetry be made available?