You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/actions-and-automations/create-self-service-experiences/create-self-service-experiences.md
+14-5Lines changed: 14 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,9 +169,9 @@ For complete examples of self-service actions using GitHub as the backend, check
169
169
170
170
## Track self-service actions
171
171
172
-
To gain visibility into how your self-service actions are being used and their performance, you can set up tracking for action runs. This allows you to monitor execution patterns, track success rates, and maintain audit trails what actions were executed and when.
172
+
To gain visibility into how your self-service actions are being used and their performance, you can set up tracking for action runs. This allows you to monitor execution patterns, track success rates, and maintain audit trails to follow what actions were executed and when.
173
173
174
-
The following tracking system works by creating a dedicated blueprint for action runs and setting up an automation that captures execution details whenever a specific self-service action is triggered as well as an automation that updates the action run's status. This approach can give you a centralized view of all action executions in your software catalog.
174
+
The following tracking system works by creating a dedicated blueprint for action runs and setting up an automation that captures execution details whenever a specific self-service action is triggered as well as an automation that updates the action run's status.
175
175
176
176
<h3>Set up data model</h3>
177
177
@@ -245,9 +245,9 @@ Create a blueprint for `Action run`:
245
245
</details>
246
246
247
247
248
-
<h3>Define the automations</h3>
248
+
<h3>Define the automation</h3>
249
249
250
-
The following automation updates the `Action run` entity with initial information regarding this run.
250
+
The following automation updates the `Action run` entity with information regarding this run.
251
251
To add it, follow these steps:
252
252
253
253
1. Go to the [Automations](https://app.getport.io/settings/automations) page of your portal.
@@ -299,4 +299,13 @@ To add it, follow these steps:
299
299
```
300
300
</details>
301
301
302
-
Using the blueprint and automation will give you a tracking system that captures all execution details of a self-service action, providing visibility into usage patterns.
302
+
Once implemented, you can track your self-service action runs and see how they are progressing.
303
+
For example, you can create the following widget to vizualize the distribution of action runs by their status:
304
+
305
+
1. Click **`+ Widget`** and select **Pie chart**.
306
+
307
+
2. Title: `Action run by status`.
308
+
309
+
3. Choose the `Action run` blueprint.
310
+
311
+
4. Under `Breakdown by property`, select the **status** property.
0 commit comments