Config sync
Reference table and example use cases to monitor the use of config sync based engagement rules for artifact replication.
- An API Provider can use Engagement to get notified:
- If the number of config sync records in a given period was less than expected, indicating that the sync failed to execute correctly.
- If the number of config sync records in a given period was more than expected, indicating that the customers on call based licensing would be charged more.
The following table shows the list of fields available for the config sync datasource. These fields are used as filters in the Rule definition list and you can select an option based on the data that is used to trigger the rule.
| Field | Type | Description |
|---|---|---|
| apis | integer | The number of apis |
| catalog_name | string | The name of the catalog. |
| catalog_id | string | The catalog ID. |
| consumer_orgs | number | The number of consumer organizations synchronized. |
| members | number | The number of members synchronized. |
| users | number | The number of users synchronized. |
| applications | number | The number of applications synchronized. |
| credentials | number | The number of credentials synchronized. |
| subscriptions | number | The number of subscriptions synchronized. |
| total items | number | The total number of items synchronized. |
| products | integer | The number of products |