Port supports various visualizations in the form of widgets, allowing you to display data from your software catalog using graphic elements, making it easier to make sense of large datasets.
Dashboards are available in:
- The Home page of your Port app - the home page itself is a dashboard, allowing you to add and customize any of the widgets described on this page.
- Every entity page can have a
dashboardtab with its own widgets.
You can create a pie chart illustrating data from entities in your software catalog divided by categories and entity properties inside a specific entity page specific entity page.
|Pie chart title|
|Pie chart Icon|
|Pie chart description|
|The chosen blueprint from which related entities data is visualized|
|Group your chart by a specific property|
|Filters to include or exclude specific data based on Port's Search Rules|||
You can create a number chart visualization from related entities in the specific entity page. You can either count the entities or perform an aggregation function on a number property. You can also filter entities so the aggregation number chart will only apply to a limited set of entities with Port's Search Rules
Number chart properties
|Number Chart title|
|Number Chart Icon|
|Number Chart description|
|The chosen blueprint from which related entities data is visualized from|
|Aggregate by either counting the entities or perform a function on a property. Possible values: |
|The number chart value will be the selected property's aggregated value (according to the chosen function). The |
|In case |
|In case |
|Used to specify an alternative property to use as the time property for the average calculation instead of the default field which is |
|Filters to include or exclude specific data based on Port's search rules|||
|The unit of the number chart. Possible Values: |
|Text to display below the number value. The |
When performing calculations of average time intervals, such as by hour, day, week, or month, it is important to note that any partial interval is considered as a full interval. This approach ensures consistency across different time units.
For example, if the dataset includes information spanning across 2 hours and 20 minutes, but the selected average timeframe is
hour, then the summed value will be divided by 3 hours.
This widget allows you to display any markdown content you wish in formatted form:
Markdown widget properties
|Markdown widget title|
|Markdown widget Icon|
You can create an iframe widget to display an embedded url in the dashboard. The iframe widget is useful to display external dashboards or other external content. It also appends to the iframe URL query params the entity identifier and the blueprint identifier so the embedded page can use it for various purposes.
The entity identifier will be concatenated under the
entity query param and the blueprint identifier will be concatenated under the
blueprint query param. For example:
|Iframe widget title|
|Iframe widget Icon|
|Iframe widget description|
|Iframe widget url|
|If the |
|If the |
|If the |
|If the |
This widget allows you to create tables displaying all entities based on a selected blueprint.
Tables can be searched, filtered and customized as you wish, using the corresponding buttons in the widget.
Pie charts, number charts and tables support filters, which allow you to include or exclude specific data from them. The filters are based on Port's Search Rules, and are set when creating the widget:
Filter example: only deployment entities from the last week
Let's assume we have a blueprint that is called
Service which is related to another blueprint called
Deployment, and we want to create visualizations on top of the last week's deployments of this service.
To achieve this desired state, we can go into one of the
Service's profile pages and create a new visualization. After selecting the
Deployment blueprint in the dropdown, we can add the following filter to the
You can use properties of the logged-in user when filtering a widget, by using the following functions:
- getUserTeams - a list of the teams the user belongs to.
- getUserEmail - the user's email.
- getUserFullName - the user's full name.
- blueprint - the blueprint identifier of the current page.