---
id: analytics-platform.ChartCreated
name: ChartCreated
version: 1.0.0
summary: "Indicates that a user has created a chart in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# ChartCreated
Indicates that a user has created a chart in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ChartCreated",
"properties": {},
"note": "This event uses only BaseEvent properties with no additional event-specific properties"
}
---
id: analytics-platform.ChartDataLoaded
name: ChartDataLoaded
version: 1.0.0
summary: "Indicates that the data for a chart has been loaded"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# ChartDataLoaded
Indicates that the data for a chart has been loaded
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ChartDataLoaded",
"properties": {
"chartId": {
"description": "Unique identifier of the chart in Superset.",
"example": 42,
"format": "int64",
"type": "integer"
},
"vizType": {
"description": "Type of visualization (e.g., bar, line, pie) used in the chart.",
"example": "table",
"type": "string"
},
"dashboardId": {
"description": "Unique identifier of the dashboard in Superset.",
"example": 7,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.ChartDeleted
name: ChartDeleted
version: 1.0.0
summary: "Indicates that a user has deleted a chart in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# ChartDeleted
Indicates that a user has deleted a chart in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ChartDeleted",
"properties": {
"chartId": {
"description": "Unique identifier of the chart in Superset.",
"example": 42,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.ChartFavorited
name: ChartFavorited
version: 1.0.0
summary: "Indicates that a user has favorited a chart in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# ChartFavorited
Indicates that a user has favorited a chart in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ChartFavorited",
"properties": {
"chartId": {
"description": "Unique identifier of the chart in Superset.",
"example": 333,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.ChartUnfavorited
name: ChartUnfavorited
version: 1.0.0
summary: "Indicates that a user has unfavorited a chart in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# ChartUnfavorited
Indicates that a user has unfavorited a chart in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ChartUnfavorited",
"properties": {
"chartId": {
"description": "Unique identifier of the chart in Superset.",
"example": 42,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.ChartUpdated
name: ChartUpdated
version: 1.0.0
summary: "Indicates that a user has updated a chart in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# ChartUpdated
Indicates that a user has updated a chart in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ChartUpdated",
"properties": {
"chartId": {
"description": "Unique identifier of the chart in Superset.",
"example": 42,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.DashboardCreated
name: DashboardCreated
version: 1.0.0
summary: "Indicates that a user has created a dashboard in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# DashboardCreated
Indicates that a user has created a dashboard in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "DashboardCreated",
"properties": {
"dashboardId": {
"description": "Unique identifier of the dashboard in Superset.",
"example": 7,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.DashboardDeleted
name: DashboardDeleted
version: 1.0.0
summary: "Indicates that a user has deleted a dashboard in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# DashboardDeleted
Indicates that a user has deleted a dashboard in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "DashboardDeleted",
"properties": {
"dashboardId": {
"description": "Unique identifier of the dashboard in Superset.",
"example": 7,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.DashboardFavorited
name: DashboardFavorited
version: 1.0.0
summary: "Indicates that a user has favorited a dashboard in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# DashboardFavorited
Indicates that a user has favorited a dashboard in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "DashboardFavorited",
"properties": {
"dashboardId": {
"description": "Unique identifier of the dashboard in Superset.",
"example": 7,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.DashboardUnfavorited
name: DashboardUnfavorited
version: 1.0.0
summary: "Indicates that a user has unfavorited a dashboard in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# DashboardUnfavorited
Indicates that a user has unfavorited a dashboard in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "DashboardUnfavorited",
"properties": {
"dashboardId": {
"description": "Unique identifier of the dashboard in Superset.",
"example": 7,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.DashboardUpdated
name: DashboardUpdated
version: 1.0.0
summary: "Indicates that a user has updated a dashboard in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# DashboardUpdated
Indicates that a user has updated a dashboard in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "DashboardUpdated",
"properties": {
"dashboardId": {
"description": "Unique identifier of the dashboard in Superset.",
"example": 7,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.DashboardViewed
name: DashboardViewed
version: 1.0.0
summary: "Indicates that a user has viewed a dashboard in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# DashboardViewed
Indicates that a user has viewed a dashboard in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "DashboardViewed",
"properties": {
"dashboardId": {
"description": "Unique identifier of the dashboard in Superset.",
"example": 7,
"format": "int64",
"type": "integer"
}
}
}
---
id: analytics-platform.DatasetCreated
name: DatasetCreated
version: 1.0.0
summary: "Indicates that a user has created a dataset in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# DatasetCreated
Indicates that a user has created a dataset in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "DatasetCreated",
"properties": {},
"note": "This event uses only BaseEvent properties with no additional event-specific properties"
}
---
id: analytics-platform.DatasetDeleted
name: DatasetDeleted
version: 1.0.0
summary: "Indicates that a user has deleted a dataset in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# DatasetDeleted
Indicates that a user has deleted a dataset in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "DatasetDeleted",
"properties": {},
"note": "This event uses only BaseEvent properties with no additional event-specific properties"
}
---
id: analytics-platform.SavedQueryCreated
name: SavedQueryCreated
version: 1.0.0
summary: "Indicates that a user has created a saved query in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# SavedQueryCreated
Indicates that a user has created a saved query in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "SavedQueryCreated",
"properties": {},
"note": "This event uses only BaseEvent properties with no additional event-specific properties"
}
---
id: analytics-platform.SqlLabQueryExecutionFailed
name: SqlLabQueryExecutionFailed
version: 1.0.0
summary: "Indicates that a user has failed to execute a SQL Lab query in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# SqlLabQueryExecutionFailed
Indicates that a user has failed to execute a SQL Lab query in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "SqlLabQueryExecutionFailed",
"properties": {},
"note": "This event uses only BaseEvent properties with no additional event-specific properties"
}
---
id: analytics-platform.SqlLabQueryExecutionSucceeded
name: SqlLabQueryExecutionSucceeded
version: 1.0.0
summary: "Indicates that a user has successfully executed a SQL Lab query in Superset"
producers:
- analytics-platform
consumers: []
schemaPath: 'schema.json'
---
# SqlLabQueryExecutionSucceeded
Indicates that a user has successfully executed a SQL Lab query in Superset
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://eventcatalog.event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "SqlLabQueryExecutionSucceeded",
"properties": {
"dashboardId": {
"description": "Unique identifier of the dashboard in Superset.",
"example": 12,
"format": "int64",
"type": "integer"
}
}
}
---
id: businessobjects.AppPurgeReceived
name: AppPurgeReceived
version: 1.0.0
summary: "Indicates that a purge request has been received"
producers:
- businessobjects
consumers: []
schemaPath: 'schema.json'
---
# AppPurgeReceived
Indicates that a purge request has been received
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "AppPurgeReceived",
"properties": {
"baseUri": {
"description": "Base URL of the tenant's cloud environment",
"example": "https://example.d-velop.cloud",
"format": "uri",
"type": "string"
},
"received": {
"description": "Timestamp indicating when the purge request was received",
"example": "2025-07-08T10:31:11.311Z",
"format": "date-time",
"type": "string"
},
"referenceId": {
"description": "Unique reference identifier of this event instance",
"example": "01JZAGPG76SXYC523XJAA7XNM7",
"type": "string"
},
"comment": {
"description": "Information that the event was backfilled",
"example": "backfilled",
"type": "string"
},
"tn": {
"description": "Unique identifier of the tenant for which the purge request was received",
"example": "3b1",
"type": "string"
}
}
}
---
id: businessobjects.AppResubscribed
name: AppResubscribed
version: 1.0.0
summary: "Indicates that a tenant has re-subscribed to Business Objects"
producers:
- businessobjects
consumers: []
schemaPath: 'schema.json'
---
# AppResubscribed
Indicates that a tenant has re-subscribed to Business Objects
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "AppResubscribed",
"properties": {
"comment": {
"description": "Information that the event was backfilled",
"example": "backfilled",
"type": "string"
},
"tn": {
"description": "Unique identifier of the re-subscribing tenant",
"example": "3b1",
"type": "string"
},
"baseUri": {
"description": "Base URL of the tenant's cloud environment",
"example": "https://example.d-velop.cloud",
"format": "uri",
"type": "string"
},
"received": {
"description": "Timestamp indicating when the tenant's app re-subscription was received",
"example": "2025-07-08T10:31:11.311Z",
"format": "date-time",
"type": "string"
},
"referenceId": {
"description": "Unique reference identifier of this event instance",
"example": "01JZAGPG76SXYC523XJAA7XNM7",
"type": "string"
}
}
}
---
id: businessobjects.AppSubscribed
name: AppSubscribed
version: 1.0.0
summary: "Indicates that a tenant has successfully subscribed to Business Objects"
producers:
- businessobjects
consumers: []
schemaPath: 'schema.json'
---
# AppSubscribed
Indicates that a tenant has successfully subscribed to Business Objects
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "AppSubscribed",
"properties": {
"tn": {
"description": "Unique identifier of the subscribing tenant",
"example": "3b1",
"type": "string"
},
"baseUri": {
"description": "Base URL of the tenant's cloud environment",
"example": "https://example.d-velop.cloud",
"format": "uri",
"type": "string"
},
"received": {
"description": "Timestamp indicating when the tenant's app subscription was received",
"example": "2025-07-08T10:31:11.311Z",
"format": "date-time",
"type": "string"
},
"referenceId": {
"description": "Unique reference identifier of this event instance",
"example": "01JZAGPG76SXYC523XJAA7XNM7",
"type": "string"
},
"comment": {
"description": "Information that the event was backfilled",
"example": "backfilled",
"type": "string"
}
}
}
---
id: businessobjects.AppUnsubscribed
name: AppUnsubscribed
version: 1.0.0
summary: "Indicates that a tenant has unsubscribed from Business Objects"
producers:
- businessobjects
consumers: []
schemaPath: 'schema.json'
---
# AppUnsubscribed
Indicates that a tenant has unsubscribed from Business Objects
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "AppUnsubscribed",
"properties": {
"received": {
"description": "Timestamp indicating when the tenant's app unsubscription was received",
"example": "2025-07-08T10:31:11.311Z",
"format": "date-time",
"type": "string"
},
"referenceId": {
"description": "Unique reference identifier of this event instance",
"example": "01JZAGPG76SXYC523XJAA7XNM7",
"type": "string"
},
"comment": {
"description": "Information that the event was backfilled",
"example": "backfilled",
"type": "string"
},
"tn": {
"description": "Unique identifier of the unsubscribing tenant",
"example": "3b1",
"type": "string"
},
"baseUri": {
"description": "Base URL of the tenant's cloud environment",
"example": "https://example.d-velop.cloud",
"format": "uri",
"type": "string"
}
}
}
---
id: businessobjects.DatabaseStatisticsBuilt
name: DatabaseStatisticsBuilt
version: 1.0.0
summary: "Indicates that database statistics have been successfully built"
producers:
- businessobjects
consumers: []
schemaPath: 'schema.json'
---
# DatabaseStatisticsBuilt
Indicates that database statistics have been successfully built
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "DatabaseStatisticsBuilt",
"properties": {
"totalDataSize": {
"description": "The total size of the data held in the database (KiB)",
"example": 2097152,
"format": "int64",
"type": "integer"
},
"entityTypeCount": {
"description": "The total number of (custom) entity types in use",
"example": 150,
"format": "int64",
"type": "integer"
},
"dataSize": {
"description": "The total size of the data in use (KiB)",
"example": 1572864,
"format": "int64",
"type": "integer"
},
"indexCount": {
"description": "The total number of indexes in use",
"example": 240,
"format": "int64",
"type": "integer"
},
"trashedDataSize": {
"description": "The total size of the data for which the related entity types were moved to the trash (KiB)",
"example": 262144,
"format": "int64",
"type": "integer"
},
"orphanedEntitySetCount": {
"description": "The total number of entity sets that are orphaned",
"example": 100,
"format": "int64",
"type": "integer"
},
"totalIndexSize": {
"description": "The total size of all indexes (KiB)",
"example": 131072,
"format": "int64",
"type": "integer"
},
"totalIndexCount": {
"description": "The total number of indexes",
"example": 300,
"format": "int64",
"type": "integer"
},
"trashedEntityCount": {
"description": "The total number of entities for which the related entity types were moved to the trash",
"example": 8000,
"format": "int64",
"type": "integer"
},
"trashedIndexSize": {
"description": "The total size of all indexes for which the related entity types were moved to the trash (KiB)",
"example": 16384,
"format": "int64",
"type": "integer"
},
"referenceId": {
"description": "Unique reference identifier of this event instance",
"example": "01JZAGPG76SXYC523XJAA7XNM7",
"type": "string"
},
"created": {
"description": "The time the statistics were created",
"example": "2025-11-03T10:31:11.311Z",
"format": "date-time",
"type": "string"
},
"tenantCount": {
"description": "The number of tenants included in the statistics",
"example": 150,
"format": "int64",
"type": "integer"
},
"trashedModelCount": {
"description": "The total number of custom models that were moved to the trash",
"example": 3,
"format": "int64",
"type": "integer"
},
"orphanedEntityCount": {
"description": "The total number of entities that are orphaned",
"example": 2000,
"format": "int64",
"type": "integer"
},
"comment": {
"description": "Information that the event was backfilled",
"example": "backfilled",
"type": "string"
},
"modelCount": {
"description": "The total number of custom models in use",
"example": 25,
"format": "int64",
"type": "integer"
},
"trashedIndexCount": {
"description": "The total number of indexes for which the related entity types were moved to the trash",
"example": 40,
"format": "int64",
"type": "integer"
},
"orphanedIndexCount": {
"description": "The total number of indexes that are orphaned",
"example": 20,
"format": "int64",
"type": "integer"
},
"orphanedIndexSize": {
"description": "The total size of all orphaned indexes (KiB)",
"example": 12288,
"format": "int64",
"type": "integer"
},
"id": {
"description": "The unique identifier under which the statistics is stored",
"example": "01JZAGPG76SXYC523XJAA7XNM7",
"type": "string"
},
"entityCount": {
"description": "The total number of entities in use",
"example": 40000,
"format": "int64",
"type": "integer"
},
"totalEntitySetCount": {
"description": "The total number of entity sets",
"example": 1500,
"format": "int64",
"type": "integer"
},
"entitySetCount": {
"description": "The total number of entity sets in use",
"example": 1200,
"format": "int64",
"type": "integer"
},
"trashedEntityTypeCount": {
"description": "The total number of (custom) entity types that were moved to the trash",
"example": 20,
"format": "int64",
"type": "integer"
},
"indexSize": {
"description": "The total size of all indexes in use (KiB)",
"example": 102400,
"format": "int64",
"type": "integer"
},
"totalEntityCount": {
"description": "The total number of entities",
"example": 50000,
"format": "int64",
"type": "integer"
},
"trashedEntitySetCount": {
"description": "The total number of entity sets for which the related entity types were moved to the trash",
"example": 200,
"format": "int64",
"type": "integer"
},
"orphanedDataSize": {
"description": "The total size of the orphaned data (KiB)",
"example": 262144,
"format": "int64",
"type": "integer"
}
}
}
---
id: businessobjects.EntitySetQueryMetricsAggregated
name: EntitySetQueryMetricsAggregated
version: 1.0.0
summary: "Emitted after query metrics for an entity set have been aggregated."
producers:
- businessobjects
consumers: []
schemaPath: 'schema.json'
---
# EntitySetQueryMetricsAggregated
Emitted after query metrics for an entity set have been aggregated.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "EntitySetQueryMetricsAggregated",
"properties": {
"queryCount": {
"description": "Total number of queries executed for this entity set within the measured scope.",
"example": 133,
"minimum": 0,
"type": "integer"
},
"aggregationInterval": {
"description": "Duration of the aggregation window used for this event. Typically equals `aggregationWindowEnd` minus `aggregationWindowStart`. Must be an ISO 8601 duration (e.g. PT30S, PT5M, PT1H).\n",
"example": "PT30S",
"type": "string"
},
"dataSource": {
"description": "Identifier of the logical context or model against which the entity set query was executed. A data source groups multiple related entity types and entity sets and represents the functional context of that query.\n",
"example": "crm",
"type": "string"
},
"queryOptionCounts": {
"description": "Counter array representing how often specific query options were used. The array index corresponds to the internal QueryOptionFeatures flag position. Index 0 represents queries without any query options. The array contains 17 entries, one for each defined query option feature bit, including the `None` and `Unknown` flags.\n",
"example": [
5,
0,
3,
0,
1,
0,
0,
2,
0,
0,
0,
1,
0,
0,
0,
0,
0
],
"items": {
"minimum": 0,
"type": "integer"
},
"maxItems": 17,
"minItems": 17,
"type": "array"
},
"operatorCounts": {
"description": "Counter array representing how often specific filter operators were used. The array index corresponds to the internal OperatorFeatures flag position. Index 0 represents queries without operators. The array contains 19 entries, one for each defined operator feature bit, including the `None` and `Unknown` flags.\n",
"example": [
2,
0,
0,
4,
1,
0,
0,
3,
0,
0,
0,
1,
0,
0,
0,
0,
0,
0,
0
],
"items": {
"minimum": 0,
"type": "integer"
},
"maxItems": 19,
"minItems": 19,
"type": "array"
},
"functionCounts": {
"description": "Counter array representing how often specific query functions were used. The array index corresponds to the internal FunctionFeatures flag position. Index 0 represents queries without functions. The array contains 41 entries, one for each defined function feature bit, including the `None` and `Unknown` flags.\n",
"example": [
10,
0,
2,
1,
0,
0,
3,
5,
0,
0,
0,
1,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0
],
"items": {
"minimum": 0,
"type": "integer"
},
"maxItems": 41,
"minItems": 41,
"type": "array"
},
"aggregationWindowStart": {
"description": "Start timestamp (inclusive) of the aggregation window.\n",
"example": "2026-02-24T10:00:00Z",
"format": "date-time",
"type": "string"
},
"aggregationWindowEnd": {
"description": "End timestamp (exclusive) of the aggregation window.\n",
"example": "2026-02-24T10:00:30Z",
"format": "date-time",
"type": "string"
},
"schemaNamespace": {
"description": "Logical namespace of the schema in which the queried entity set is defined. Indicates whether the schema is system-provided (e.g. `core`) or tenant-specific (`custom`).\n",
"example": "custom",
"type": "string"
},
"entitySet": {
"description": "Name of the entity set that was queried.",
"example": "customers",
"type": "string"
},
"entitiesReturned": {
"description": "Total number of entities returned across all executed queries for this entity set within the measured scope.\n",
"example": 12509,
"minimum": 0,
"type": "integer"
}
}
}
---
id: businessobjects.EntitySetStatisticsBuilt
name: EntitySetStatisticsBuilt
version: 1.0.0
summary: "Indicates that entity set statistics have been successfully built"
producers:
- businessobjects
consumers: []
schemaPath: 'schema.json'
---
# EntitySetStatisticsBuilt
Indicates that entity set statistics have been successfully built
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "EntitySetStatisticsBuilt",
"properties": {
"name": {
"description": "The (logical) name of the entity set",
"example": "Products",
"type": "string"
},
"physicalName": {
"description": "The physical name of the entity set",
"example": "products_3b1_collection",
"type": "string"
},
"averageEntitySize": {
"description": "The average size of an entity in the entity set",
"example": 2,
"format": "int64",
"type": "integer"
},
"indexCount": {
"description": "The number of indexes",
"example": 3,
"format": "int64",
"type": "integer"
},
"comment": {
"description": "Information that the event was backfilled",
"example": "backfilled",
"type": "string"
},
"typeName": {
"description": "The type name of the entities in the entity set",
"example": "Product",
"type": "string"
},
"dataSize": {
"description": "The size of the data in the entity set (KiB)",
"example": 1024,
"format": "int64",
"type": "integer"
},
"entityCount": {
"description": "The number of entities in the entity set",
"example": 500,
"format": "int64",
"type": "integer"
},
"indexSize": {
"description": "The size of the indexes (KiB)",
"example": 128,
"format": "int64",
"type": "integer"
},
"kind": {
"description": "The kind of the entity set (e.g., trashed, active)",
"example": "active",
"type": "string"
},
"referenceId": {
"description": "Unique reference identifier of this event instance",
"example": "01JZAGPG76SXYC523XJAA7XNM7",
"type": "string"
},
"tn": {
"description": "Unique identifier of the tenant",
"example": "3b1",
"type": "string"
}
}
}
---
id: businessobjects.TenantComputedTierChanged
name: TenantComputedTierChanged
version: 1.0.0
summary: "Indicates that a tenant's computed tier has changed"
producers:
- businessobjects
consumers: []
schemaPath: 'schema.json'
---
# TenantComputedTierChanged
Indicates that a tenant's computed tier has changed
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "TenantComputedTierChanged",
"properties": {
"tn": {
"description": "Unique identifier of the tenant",
"example": "3b1",
"type": "string"
},
"oldTier": {
"description": "The previous computed tier of the tenant",
"example": "standard",
"type": "string"
},
"newTier": {
"description": "The new computed tier of the tenant",
"example": "basic",
"type": "string"
},
"tierDeterminants": {
"description": "The factors that determined the new tier calculation",
"example": "TotalEntityCount: 925, EntitySetMaxEntityCount: 382",
"type": "string"
}
}
}
---
id: businessobjects.TenantDatabaseStatisticsBuilt
name: TenantDatabaseStatisticsBuilt
version: 1.0.0
summary: "Indicates that tenant database statistics have been successfully built"
producers:
- businessobjects
consumers: []
schemaPath: 'schema.json'
---
# TenantDatabaseStatisticsBuilt
Indicates that tenant database statistics have been successfully built
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.int.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "TenantDatabaseStatisticsBuilt",
"properties": {
"trashedIndexSize": {
"description": "The total size of all indexes for which the related entity types were moved to the trash (KiB)",
"example": 8192,
"format": "int64",
"type": "integer"
},
"orphanedEntityCount": {
"description": "The total number of entities that are orphaned",
"example": 1000,
"format": "int64",
"type": "integer"
},
"orphanedIndexCount": {
"description": "The total number of indexes that are orphaned",
"example": 5,
"format": "int64",
"type": "integer"
},
"totalEntityCount": {
"description": "The total number of entities",
"example": 25000,
"format": "int64",
"type": "integer"
},
"entitySetCount": {
"description": "The total number of entity sets in use",
"example": 120,
"format": "int64",
"type": "integer"
},
"trashedModelCount": {
"description": "The total number of custom models that were moved to the trash",
"example": 2,
"format": "int64",
"type": "integer"
},
"orphanedEntitySetCount": {
"description": "The total number of entity sets that are orphaned",
"example": 10,
"format": "int64",
"type": "integer"
},
"created": {
"description": "The time the statistics were created",
"example": "2025-11-03T10:31:11.311Z",
"format": "date-time",
"type": "string"
},
"trashedEntityTypeCount": {
"description": "The total number of (custom) entity types that were moved to the trash",
"example": 8,
"format": "int64",
"type": "integer"
},
"trashedEntitySetCount": {
"description": "The total number of entity sets for which the related entity types were moved to the trash",
"example": 20,
"format": "int64",
"type": "integer"
},
"tn": {
"description": "Unique identifier of the tenant",
"example": "3b1",
"type": "string"
},
"totalEntitySetCount": {
"description": "The total number of entity sets",
"example": 150,
"format": "int64",
"type": "integer"
},
"dataSize": {
"description": "The total size of the data in use (KiB)",
"example": 786432,
"format": "int64",
"type": "integer"
},
"entityCount": {
"description": "The total number of entities in use",
"example": 20000,
"format": "int64",
"type": "integer"
},
"trashedIndexCount": {
"description": "The total number of indexes for which the related entity types were moved to the trash",
"example": 10,
"format": "int64",
"type": "integer"
},
"tenantDatabaseName": {
"description": "The name of the tenant database",
"example": "t_10qg",
"type": "string"
},
"modelCount": {
"description": "The total number of custom models in use",
"example": 12,
"format": "int64",
"type": "integer"
},
"referenceId": {
"description": "Unique reference identifier of this event instance",
"example": "01JZAGPG76SXYC523XJAA7XNM7",
"type": "string"
},
"id": {
"description": "The unique identifier under which the statistics is stored",
"example": "01JZAGPG76SXYC523XJAA7XNM7",
"type": "string"
},
"totalIndexSize": {
"description": "The total size of all indexes (KiB)",
"example": 65536,
"format": "int64",
"type": "integer"
},
"totalIndexCount": {
"description": "The total number of indexes",
"example": 75,
"format": "int64",
"type": "integer"
},
"indexSize": {
"description": "The total size of all indexes in use (KiB)",
"example": 51200,
"format": "int64",
"type": "integer"
},
"indexCount": {
"description": "The total number of indexes in use",
"example": 60,
"format": "int64",
"type": "integer"
},
"trashedDataSize": {
"description": "The total size of the data for which the related entity types were moved to the trash (KiB)",
"example": 131072,
"format": "int64",
"type": "integer"
},
"totalDataSize": {
"description": "The total size of the data held in the database (KiB)",
"example": 1048576,
"format": "int64",
"type": "integer"
},
"orphanedDataSize": {
"description": "The total size of the orphaned data (KiB)",
"example": 131072,
"format": "int64",
"type": "integer"
},
"orphanedIndexSize": {
"description": "The total size of all orphaned indexes (KiB)",
"example": 6144,
"format": "int64",
"type": "integer"
},
"entityTypeCount": {
"description": "The total number of (custom) entity types in use",
"example": 45,
"format": "int64",
"type": "integer"
},
"trashedEntityCount": {
"description": "The total number of entities for which the related entity types were moved to the trash",
"example": 4000,
"format": "int64",
"type": "integer"
}
}
}
---
id: dash.DashboardEdited
name: DashboardEdited
version: 1.0.0
summary: "Event emitted when a user edits their dashboard."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# DashboardEdited
Event emitted when a user edits their dashboard.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "DashboardEdited",
"properties": {
"kind": {
"description": "The kind of edit performed on the dashboard.",
"enum": [
"saved",
"discarded"
],
"type": "string"
},
"transactionId": {
"description": "Unique identifier of the edit transaction. This is set when the user opens the dashboard editor.",
"type": "string"
},
"dashboardId": {
"description": "Unique identifier of the dashboard that was edited.",
"type": "string"
}
}
}
---
id: dash.DashboardMetricsCollected
name: DashboardMetricsCollected
version: 1.0.0
summary: "Event emitted once a day containing collected dashboard metrics from the database."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# DashboardMetricsCollected
Event emitted once a day containing collected dashboard metrics from the database.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "DashboardMetricsCollected",
"properties": {
"tenantDashboardsPerTenantDistr": {
"additionalProperties": {
"description": "Number of tenants with the corresponding number of tenant dashboards.",
"type": "integer"
},
"description": "Distribution of the number of tenant dashboards per tenant.",
"propertyNames": {
"enum": [
"50",
"30",
"20",
"10",
"8",
"5",
"3",
"2",
"1",
"0"
]
},
"type": "object"
},
"totalTenantsWithWidgetVisEnable": {
"description": "Total number of tenants that have enabled widget visibility settings.",
"type": "integer"
},
"assignedTnDashboardsPerTnDistr": {
"additionalProperties": {
"description": "Number of tenants with the corresponding number of assigned tenant dashboards.",
"type": "integer"
},
"description": "Distribution of the number of assigned tenant dashboards per tenant.",
"propertyNames": {
"enum": [
"50",
"30",
"20",
"10",
"8",
"5",
"3",
"2",
"1",
"0"
]
},
"type": "object"
},
"avgConsumersPerWidgetVisConfig": {
"description": "Average number of consumers per widget visibility configuration.",
"format": "float",
"type": "number"
},
"avgUsersPerWidgetVisConfig": {
"description": "Average number of users per widget visibility configuration.",
"format": "float",
"type": "number"
},
"usersPerWidgetVisConfigDist": {
"additionalProperties": {
"description": "Number of widget visibility configurations with the corresponding number of users.",
"type": "integer"
},
"description": "Distribution of the number of users per widget visibility configuration.",
"propertyNames": {
"enum": [
"50",
"30",
"20",
"15",
"10",
"5",
"3",
"2",
"1",
"0"
]
},
"type": "object"
},
"groupsPerWidgetVisConfigDist": {
"additionalProperties": {
"description": "Number of widget visibility configurations with the corresponding number of groups.",
"type": "integer"
},
"description": "Distribution of the number of groups per widget visibility configuration.",
"propertyNames": {
"enum": [
"50",
"30",
"20",
"15",
"10",
"5",
"3",
"2",
"1",
"0"
]
},
"type": "object"
},
"tenantWidgetUsage": {
"description": "Total number of tenants that use tenant widgets.",
"type": "integer"
},
"totalTenantDashboardsCount": {
"description": "Total number of tenant dashboards across all tenants that use dashboard V2.",
"type": "integer"
},
"totalCustomizableTnBoardCount": {
"description": "Total number of customizable tenant dashboards across all tenants.",
"type": "integer"
},
"avgTenantDashboardsPerTenant": {
"description": "Average number of tenant dashboards per tenant.",
"format": "float",
"type": "number"
},
"avgAssignedTnDashboardsPerTnNew": {
"description": "Average number of assigned tenant dashboards per tenant.",
"format": "float",
"type": "number"
},
"avgGroupsPerWidgetVisConfig": {
"description": "Average number of groups per widget visibility configuration.",
"format": "float",
"type": "number"
},
"totalTenantWidgetsCount": {
"description": "Total number of tenant widgets across all tenants.",
"type": "integer"
},
"listTenantWidgetUsage": {
"description": "Total number of tenants that use tenant list widgets.",
"type": "integer"
},
"totalIFrameTenantWidgetsCount": {
"description": "Total number of tenant iframe widgets across all tenants.",
"type": "integer"
},
"totalV2TenantsCount": {
"description": "Total number of tenants that use dashboard V2.",
"type": "integer"
},
"totalListTenantWidgetsCount": {
"description": "Total number of tenant list widgets across all tenants.",
"type": "integer"
},
"iFrameTenantWidgetUsage": {
"description": "Total number of tenants that use tenant iframe widgets.",
"type": "integer"
},
"consumersPerWidgetVisConfigDist": {
"additionalProperties": {
"description": "Number of widget visibility configurations with the corresponding number of consumers.",
"type": "integer"
},
"description": "Distribution of the number of consumers per widget visibility configuration.",
"propertyNames": {
"enum": [
"50",
"30",
"20",
"15",
"10",
"5",
"3",
"2",
"1",
"0"
]
},
"type": "object"
},
"totalDisabledV2TenantsCount": {
"description": "Total number of tenants that have disabled dashboard V2.",
"type": "integer"
}
}
}
---
id: dash.DashboardPublicAPIRequestReceived
name: DashboardPublicAPIRequestReceived
version: 1.0.0
summary: "Event emitted when a request is made to the Dashboard Public API."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# DashboardPublicAPIRequestReceived
Event emitted when a request is made to the Dashboard Public API.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "DashboardPublicAPIRequestReceived",
"properties": {
"httpMethod": {
"description": "The HTTP method used for the request.",
"enum": [
"GET",
"POST",
"PUT",
"DELETE"
],
"type": "string"
},
"routeType": {
"description": "The type of route accessed in the Dashboard Public API.",
"enum": [
"collection",
"singleton"
],
"type": "string"
}
}
}
---
id: dash.DashboardPublicAPIRequestSuccessful
name: DashboardPublicAPIRequestSuccessful
version: 1.0.0
summary: "Event emitted when a request to the Dashboard Public API is successful."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# DashboardPublicAPIRequestSuccessful
Event emitted when a request to the Dashboard Public API is successful.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "DashboardPublicAPIRequestSuccessful",
"properties": {
"httpMethod": {
"description": "The HTTP method used for the request.",
"enum": [
"GET",
"POST",
"PUT",
"DELETE"
],
"type": "string"
},
"routeType": {
"description": "The type of route accessed in the Dashboard Public API.",
"enum": [
"collection",
"singleton"
],
"type": "string"
}
}
}
---
id: dash.DisableDashboardV2Changed
name: DisableDashboardV2Changed
version: 1.0.0
summary: "Event emitted when a tenant changes the feature preview to disable or enable Dashboard V2."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# DisableDashboardV2Changed
Event emitted when a tenant changes the feature preview to disable or enable Dashboard V2.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "DisableDashboardV2Changed",
"properties": {
"active": {
"description": "Indicates whether Dashboard V2 has been disabled (true) or enabled (false) by the tenant.",
"type": "boolean"
}
}
}
---
id: dash.EnableHomeAppChanged
name: EnableHomeAppChanged
version: 1.0.0
summary: "Event emitted when a tenant changes the feature preview to enable or disable the Home App."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# EnableHomeAppChanged
Event emitted when a tenant changes the feature preview to enable or disable the Home App.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "EnableHomeAppChanged",
"properties": {
"active": {
"description": "Indicates whether the Home App has been enabled (true) or disabled (false) by the tenant.",
"type": "boolean"
}
}
}
---
id: dash.FavoritesUpdated
name: FavoritesUpdated
version: 1.0.0
summary: "Event emitted when a user updates their favorites in the apps menu."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# FavoritesUpdated
Event emitted when a user updates their favorites in the apps menu.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "FavoritesUpdated",
"properties": {
"favorites": {
"description": "The list of favored apps.",
"items": {
"type": "string"
},
"type": "array"
},
"favoritesCount": {
"description": "The total number of favored apps.",
"type": "integer"
}
}
}
---
id: dash.LegacyWidgetsConverted
name: LegacyWidgetsConverted
version: 1.0.0
summary: "Event emitted when the widget converter has been executed."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# LegacyWidgetsConverted
Event emitted when the widget converter has been executed.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "LegacyWidgetsConverted",
"properties": {
"homeWidgetCount": {
"description": "The number of home widgets that were converted.",
"type": "integer"
},
"v1WidgetCount": {
"description": "The number of v1 dashboard widgets that were converted.",
"type": "integer"
},
"convertedWidgetCount": {
"description": "The total number of converted widgets after merging.",
"type": "integer"
}
}
}
---
id: dash.NavigatedViaAppsMenu
name: NavigatedViaAppsMenu
version: 1.0.0
summary: "Event emitted when a user navigates to an app via the apps menu."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# NavigatedViaAppsMenu
Event emitted when a user navigates to an app via the apps menu.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "NavigatedViaAppsMenu",
"properties": {
"widgetID": {
"description": "Unique identifier of the widget instance from which the navigation was initiated.",
"type": "string"
},
"isFavorite": {
"description": "Indicates whether the app navigated to is marked as a favorite by the user.",
"type": "boolean"
}
}
}
---
id: dash.NavigatedViaWidget
name: NavigatedViaWidget
version: 1.0.0
summary: "Event emitted when a user navigates to an app via a dashboard widget."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# NavigatedViaWidget
Event emitted when a user navigates to an app via a dashboard widget.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "NavigatedViaWidget",
"properties": {
"type": {
"description": "The type of the widget used for navigation.",
"enum": [
"shortcut",
"list",
"iframe"
],
"type": "string"
},
"widgetID": {
"description": "Unique identifier of the widget instance from which the navigation was initiated.",
"type": "string"
}
}
}
---
id: dash.ResetAllCustomDashboards
name: ResetAllCustomDashboards
version: 1.0.0
summary: "Event emitted when all custom user dashboards are reset."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# ResetAllCustomDashboards
Event emitted when all custom user dashboards are reset.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "ResetAllCustomDashboards",
"properties": {},
"note": "This event uses only BaseEvent properties with no additional event-specific properties"
}
---
id: dash.ResetUserDashboard
name: ResetUserDashboard
version: 1.0.0
summary: "Event emitted when a user resets their dashboard to the default dashboard."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# ResetUserDashboard
Event emitted when a user resets their dashboard to the default dashboard.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "ResetUserDashboard",
"properties": {},
"note": "This event uses only BaseEvent properties with no additional event-specific properties"
}
---
id: dash.TenantDashboardCreated
name: TenantDashboardCreated
version: 1.0.0
summary: "Event emitted when a tenant dashboard is created."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# TenantDashboardCreated
Event emitted when a tenant dashboard is created.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "TenantDashboardCreated",
"properties": {
"agent": {
"description": "The agent that created the tenant dashboard.",
"enum": [
"service",
"user"
],
"type": "string"
}
}
}
---
id: dash.TenantDashboardDeleted
name: TenantDashboardDeleted
version: 1.0.0
summary: "Event emitted when a tenant dashboard is deleted."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# TenantDashboardDeleted
Event emitted when a tenant dashboard is deleted.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "TenantDashboardDeleted",
"properties": {
"agent": {
"description": "The agent that deleted the tenant dashboard.",
"enum": [
"service",
"user"
],
"type": "string"
}
}
}
---
id: dash.WidgetAdded
name: WidgetAdded
version: 1.0.0
summary: "Event emitted when a user adds a widget to the v1 dashboard."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# WidgetAdded
Event emitted when a user adds a widget to the v1 dashboard.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "WidgetAdded",
"properties": {
"widgetID": {
"description": "Unique identifier of the added widget instance.",
"type": "string"
},
"registrationID": {
"description": "Registration ID of the added widget.",
"type": "string"
},
"widgetType": {
"description": "Type of the added widget.",
"enum": [
"shortcut",
"list",
"iframe"
],
"type": "string"
}
}
}
---
id: dash.WidgetAPIV2Used
name: WidgetAPIV2Used
version: 1.0.0
summary: "Event emitted when the Widget API V2 is used."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# WidgetAPIV2Used
Event emitted when the Widget API V2 is used.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "WidgetAPIV2Used",
"properties": {
"id": {
"description": "Unique identifier of the widget. If the collection route is used, this is just the app name.",
"examples": [
"app1/my-widget",
"app1"
],
"type": "string"
},
"method": {
"description": "The method of the Widget API V2 that was used.",
"enum": [
"GetAllWidgetsForApp",
"GetWidgetByID",
"UpsertWidget",
"DeleteWidget"
],
"type": "string"
}
}
}
---
id: dash.WidgetDeregistered
name: WidgetDeregistered
version: 1.0.0
summary: "Event emitted when a v1 widget is deregistered."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# WidgetDeregistered
Event emitted when a v1 widget is deregistered.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "WidgetDeregistered",
"properties": {
"widgetId": {
"description": "Unique identifier of the deregistered widget.",
"type": "string"
}
}
}
---
id: dash.WidgetRegistered
name: WidgetRegistered
version: 1.0.0
summary: "Event emitted when a new v1 widget is registered."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# WidgetRegistered
Event emitted when a new v1 widget is registered.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "WidgetRegistered",
"properties": {
"widgetId": {
"description": "Unique identifier of the newly registered widget.",
"type": "string"
},
"widgetType": {
"description": "Type of the newly registered widget.",
"enum": [
"shortcut",
"list",
"iframe"
],
"type": "string"
}
}
}
---
id: dash.WidgetRemoved
name: WidgetRemoved
version: 1.0.0
summary: "Event emitted when a user removes a widget from the v1 dashboard."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# WidgetRemoved
Event emitted when a user removes a widget from the v1 dashboard.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "WidgetRemoved",
"properties": {
"widgetID": {
"description": "Unique identifier of the removed widget instance.",
"type": "string"
}
}
}
---
id: dash.WidgetSettingsUpdated
name: WidgetSettingsUpdated
version: 1.0.0
summary: "Event emitted when a user updates the settings of a widget in the v1 dashboard."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# WidgetSettingsUpdated
Event emitted when a user updates the settings of a widget in the v1 dashboard.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "WidgetSettingsUpdated",
"properties": {
"widgetID": {
"description": "Unique identifier of the widget instance whose settings were updated.",
"type": "string"
}
}
}
---
id: dash.WidgetV2ReplacedOnDashboards
name: WidgetV2ReplacedOnDashboards
version: 1.0.0
summary: "Event emitted when a v1 widget is replaced by a v2 widget on dashboards."
producers:
- dash
consumers: []
schemaPath: 'schema.json'
---
# WidgetV2ReplacedOnDashboards
Event emitted when a v1 widget is replaced by a v2 widget on dashboards.
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "../../../base/base-event.yaml#/BaseEvent",
"eventType": "WidgetV2ReplacedOnDashboards",
"properties": {
"deletedWidget": {
"description": "Unique identifier of the v1 widget that was deleted.",
"type": "string"
},
"replacementWidget": {
"description": "Unique identifier of the v2 widget that replaced the v1 widget.",
"type": "string"
}
}
}
---
id: dvelop-actions.ExecuteAction
name: ExecuteAction
version: 1.0.0
summary: "Indicates that an action has been executed successfully"
producers:
- dvelop-actions
consumers: []
schemaPath: 'schema.json'
---
# ExecuteAction
Indicates that an action has been executed successfully
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ExecuteAction",
"properties": {
"volatile": {
"description": "Whether the action is marked as volatile or long term stable",
"example": false,
"type": "boolean"
},
"actionId": {
"description": "Unique identifier of the executed action",
"example": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"type": "string"
},
"executionMode": {
"description": "Whether the action was executed synchronously or asynchronously",
"enum": [
"sync",
"async"
],
"example": "sync",
"type": "string"
}
}
}
---
id: dvelop-actions.ExecuteEvent
name: ExecuteEvent
version: 1.0.0
summary: "Indicates that an incoming CloudEvent has been accepted and published to the event bus"
producers:
- dvelop-actions
consumers: []
schemaPath: 'schema.json'
---
# ExecuteEvent
Indicates that an incoming CloudEvent has been accepted and published to the event bus
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ExecuteEvent",
"properties": {
"eventDefinitionId": {
"description": "Composite identifier of the event definition that was received. Derived from CloudEvent headers in the format \"{appName}_{ceType}\".\n",
"example": "documents_dvelop.documents.document.created.v1",
"type": "string"
}
}
}
---
id: dvelop-actions.ExecuteRoutineWithAction
name: ExecuteRoutineWithAction
version: 1.0.0
summary: "Indicates that a routine has been triggered and routed to a registered action"
producers:
- dvelop-actions
consumers: []
schemaPath: 'schema.json'
---
# ExecuteRoutineWithAction
Indicates that a routine has been triggered and routed to a registered action
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ExecuteRoutineWithAction",
"properties": {
"eventDefinitionId": {
"description": "Identifier of the event definition that triggered this routine",
"example": "documents_dvelop.documents.document.created.v1",
"type": "string"
},
"actionId": {
"description": "Unique identifier of the action invoked by this routine",
"example": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"type": "string"
},
"mappingCount": {
"description": "Number of JSONPath mapping entries configured on the routine",
"example": 3,
"minimum": 0,
"type": "integer"
},
"rulesCount": {
"description": "Number of top-level conditions in the routine's JSONLogic rules expression",
"example": 2,
"minimum": 0,
"type": "integer"
}
}
}
---
id: dvelop-actions.ExecuteRoutineWithRelativeURL
name: ExecuteRoutineWithRelativeURL
version: 1.0.0
summary: "Indicates that a routine has been triggered and routed to a relative URL endpoint"
producers:
- dvelop-actions
consumers: []
schemaPath: 'schema.json'
---
# ExecuteRoutineWithRelativeURL
Indicates that a routine has been triggered and routed to a relative URL endpoint
## Base Schema
All analytics events are based on the **TrackEvent** schema which provides common properties like `messageId`, `userId`, `context`, timestamps, and more.
**Base Schema Reference**: [analytics-track.yaml](https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml)
## Event-Specific Properties
This schema shows only the event-specific properties that extend the base TrackEvent schema:
## Raw Schema:schema.json
{
"title": "Event-Specific Properties",
"type": "object",
"description": "Properties specific to this event type (extends BaseEvent)",
"extends": "https://event-catalog.prod.otc.fts.d-3.de/schemas/analytics-track.yaml#/TrackEvent",
"eventType": "ExecuteRoutineWithRelativeURL",
"properties": {
"eventDefinitionId": {
"description": "Identifier of the event definition that triggered this routine",
"example": "documents_dvelop.documents.document.created.v1",
"type": "string"
},
"url": {
"description": "The relative URL endpoint called by the routine",
"example": "/api/myapp/webhook",
"type": "string"
},
"mappingCount": {
"description": "Number of JSONPath mapping entries configured on the routine",
"example": 3,
"minimum": 0,
"type": "integer"
},
"rulesCount": {
"description": "Number of top-level conditions in the routine's JSONLogic rules expression",
"example": 2,
"minimum": 0,
"type": "integer"
}
}
}
---
id: analytics-platform
name: Analytics Platform - Analytics Events
version: 0.0.1
summary: "This AsyncAPI document describes analytics and tracking events related to the Analytics Platform application. These events are primarily used to analyze the use and development of the Analytics Platform. Essentially, certain log information from the Apache Superset analysis tool is used for this purpose."
sends:
- id: analytics-platform.DatasetDeleted
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.SqlLabQueryExecutionSucceeded
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.ChartCreated
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.DashboardViewed
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.DashboardDeleted
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.DatasetCreated
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.SavedQueryCreated
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.SqlLabQueryExecutionFailed
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.ChartUpdated
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.ChartDeleted
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.DashboardCreated
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.DashboardUpdated
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.ChartFavorited
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.ChartUnfavorited
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.ChartDataLoaded
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.DashboardFavorited
version: 1.0.0
to:
- id: analytics
- id: analytics-platform.DashboardUnfavorited
version: 1.0.0
to:
- id: analytics
receives: []
---
# Analytics Platform - Analytics Events
This AsyncAPI document describes analytics and tracking events related to the Analytics Platform application.
These events are primarily used to analyze the use and development of the Analytics Platform.
Essentially, certain log information from the Apache Superset analysis tool is used for this purpose.
## Events Sent
- [analytics-platform.DatasetDeleted](/docs/events/analytics-platform.DatasetDeleted/1.0.0)
- [analytics-platform.SqlLabQueryExecutionSucceeded](/docs/events/analytics-platform.SqlLabQueryExecutionSucceeded/1.0.0)
- [analytics-platform.ChartCreated](/docs/events/analytics-platform.ChartCreated/1.0.0)
- [analytics-platform.DashboardViewed](/docs/events/analytics-platform.DashboardViewed/1.0.0)
- [analytics-platform.DashboardDeleted](/docs/events/analytics-platform.DashboardDeleted/1.0.0)
- [analytics-platform.DatasetCreated](/docs/events/analytics-platform.DatasetCreated/1.0.0)
- [analytics-platform.SavedQueryCreated](/docs/events/analytics-platform.SavedQueryCreated/1.0.0)
- [analytics-platform.SqlLabQueryExecutionFailed](/docs/events/analytics-platform.SqlLabQueryExecutionFailed/1.0.0)
- [analytics-platform.ChartUpdated](/docs/events/analytics-platform.ChartUpdated/1.0.0)
- [analytics-platform.ChartDeleted](/docs/events/analytics-platform.ChartDeleted/1.0.0)
- [analytics-platform.DashboardCreated](/docs/events/analytics-platform.DashboardCreated/1.0.0)
- [analytics-platform.DashboardUpdated](/docs/events/analytics-platform.DashboardUpdated/1.0.0)
- [analytics-platform.ChartFavorited](/docs/events/analytics-platform.ChartFavorited/1.0.0)
- [analytics-platform.ChartUnfavorited](/docs/events/analytics-platform.ChartUnfavorited/1.0.0)
- [analytics-platform.ChartDataLoaded](/docs/events/analytics-platform.ChartDataLoaded/1.0.0)
- [analytics-platform.DashboardFavorited](/docs/events/analytics-platform.DashboardFavorited/1.0.0)
- [analytics-platform.DashboardUnfavorited](/docs/events/analytics-platform.DashboardUnfavorited/1.0.0)
---
id: businessobjects
name: Business Objects - Analytics Events
version: 0.0.2
summary: "This AsyncAPI document describes analytics and tracking events related to the Business Objects application. These events are primarily used for lifecycle tracking and product usage analysis within the d.velop Analytics Platform."
sends:
- id: businessobjects.EntitySetStatisticsBuilt
version: 1.0.0
to:
- id: analytics
- id: businessobjects.EntitySetQueryMetricsAggregated
version: 1.0.0
to:
- id: analytics
- id: businessobjects.AppSubscribed
version: 1.0.0
to:
- id: analytics
- id: businessobjects.AppResubscribed
version: 1.0.0
to:
- id: analytics
- id: businessobjects.TenantComputedTierChanged
version: 1.0.0
to:
- id: analytics
- id: businessobjects.TenantDatabaseStatisticsBuilt
version: 1.0.0
to:
- id: analytics
- id: businessobjects.AppUnsubscribed
version: 1.0.0
to:
- id: analytics
- id: businessobjects.AppPurgeReceived
version: 1.0.0
to:
- id: analytics
- id: businessobjects.DatabaseStatisticsBuilt
version: 1.0.0
to:
- id: analytics
receives: []
---
# Business Objects - Analytics Events
This AsyncAPI document describes analytics and tracking events related to the Business Objects application.
These events are primarily used for lifecycle tracking and product usage analysis within the d.velop Analytics
Platform.
## Events Sent
- [businessobjects.EntitySetStatisticsBuilt](/docs/events/businessobjects.EntitySetStatisticsBuilt/1.0.0)
- [businessobjects.EntitySetQueryMetricsAggregated](/docs/events/businessobjects.EntitySetQueryMetricsAggregated/1.0.0)
- [businessobjects.AppSubscribed](/docs/events/businessobjects.AppSubscribed/1.0.0)
- [businessobjects.AppResubscribed](/docs/events/businessobjects.AppResubscribed/1.0.0)
- [businessobjects.TenantComputedTierChanged](/docs/events/businessobjects.TenantComputedTierChanged/1.0.0)
- [businessobjects.TenantDatabaseStatisticsBuilt](/docs/events/businessobjects.TenantDatabaseStatisticsBuilt/1.0.0)
- [businessobjects.AppUnsubscribed](/docs/events/businessobjects.AppUnsubscribed/1.0.0)
- [businessobjects.AppPurgeReceived](/docs/events/businessobjects.AppPurgeReceived/1.0.0)
- [businessobjects.DatabaseStatisticsBuilt](/docs/events/businessobjects.DatabaseStatisticsBuilt/1.0.0)
---
id: dash
name: Dashboard-App - Analytics Events
version: 0.0.1
summary: "This AsyncAPI document describes analytics and tracking events related to the Dashboard-App. These events are primarily used to analyze the usage and development of the Dashboard-App."
sends:
- id: dash.WidgetRemoved
version: 1.0.0
to:
- id: analytics
- id: dash.TenantDashboardCreated
version: 1.0.0
to:
- id: analytics
- id: dash.WidgetV2ReplacedOnDashboards
version: 1.0.0
to:
- id: analytics
- id: dash.DashboardMetricsCollected
version: 1.0.0
to:
- id: analytics
- id: dash.WidgetAdded
version: 1.0.0
to:
- id: analytics
- id: dash.DashboardPublicAPIRequestReceived
version: 1.0.0
to:
- id: analytics
- id: dash.DashboardEdited
version: 1.0.0
to:
- id: analytics
- id: dash.ResetAllCustomDashboards
version: 1.0.0
to:
- id: analytics
- id: dash.WidgetSettingsUpdated
version: 1.0.0
to:
- id: analytics
- id: dash.WidgetAPIV2Used
version: 1.0.0
to:
- id: analytics
- id: dash.TenantDashboardDeleted
version: 1.0.0
to:
- id: analytics
- id: dash.DisableDashboardV2Changed
version: 1.0.0
to:
- id: analytics
- id: dash.EnableHomeAppChanged
version: 1.0.0
to:
- id: analytics
- id: dash.LegacyWidgetsConverted
version: 1.0.0
to:
- id: analytics
- id: dash.WidgetRegistered
version: 1.0.0
to:
- id: analytics
- id: dash.ResetUserDashboard
version: 1.0.0
to:
- id: analytics
- id: dash.DashboardPublicAPIRequestSuccessful
version: 1.0.0
to:
- id: analytics
- id: dash.WidgetDeregistered
version: 1.0.0
to:
- id: analytics
- id: dash.NavigatedViaAppsMenu
version: 1.0.0
to:
- id: analytics
- id: dash.NavigatedViaWidget
version: 1.0.0
to:
- id: analytics
- id: dash.FavoritesUpdated
version: 1.0.0
to:
- id: analytics
receives: []
---
# Dashboard-App - Analytics Events
This AsyncAPI document describes analytics and tracking events related to the Dashboard-App.
These events are primarily used to analyze the usage and development of the Dashboard-App.
## Events Sent
- [dash.WidgetRemoved](/docs/events/dash.WidgetRemoved/1.0.0)
- [dash.TenantDashboardCreated](/docs/events/dash.TenantDashboardCreated/1.0.0)
- [dash.WidgetV2ReplacedOnDashboards](/docs/events/dash.WidgetV2ReplacedOnDashboards/1.0.0)
- [dash.DashboardMetricsCollected](/docs/events/dash.DashboardMetricsCollected/1.0.0)
- [dash.WidgetAdded](/docs/events/dash.WidgetAdded/1.0.0)
- [dash.DashboardPublicAPIRequestReceived](/docs/events/dash.DashboardPublicAPIRequestReceived/1.0.0)
- [dash.DashboardEdited](/docs/events/dash.DashboardEdited/1.0.0)
- [dash.ResetAllCustomDashboards](/docs/events/dash.ResetAllCustomDashboards/1.0.0)
- [dash.WidgetSettingsUpdated](/docs/events/dash.WidgetSettingsUpdated/1.0.0)
- [dash.WidgetAPIV2Used](/docs/events/dash.WidgetAPIV2Used/1.0.0)
- [dash.TenantDashboardDeleted](/docs/events/dash.TenantDashboardDeleted/1.0.0)
- [dash.DisableDashboardV2Changed](/docs/events/dash.DisableDashboardV2Changed/1.0.0)
- [dash.EnableHomeAppChanged](/docs/events/dash.EnableHomeAppChanged/1.0.0)
- [dash.LegacyWidgetsConverted](/docs/events/dash.LegacyWidgetsConverted/1.0.0)
- [dash.WidgetRegistered](/docs/events/dash.WidgetRegistered/1.0.0)
- [dash.ResetUserDashboard](/docs/events/dash.ResetUserDashboard/1.0.0)
- [dash.DashboardPublicAPIRequestSuccessful](/docs/events/dash.DashboardPublicAPIRequestSuccessful/1.0.0)
- [dash.WidgetDeregistered](/docs/events/dash.WidgetDeregistered/1.0.0)
- [dash.NavigatedViaAppsMenu](/docs/events/dash.NavigatedViaAppsMenu/1.0.0)
- [dash.NavigatedViaWidget](/docs/events/dash.NavigatedViaWidget/1.0.0)
- [dash.FavoritesUpdated](/docs/events/dash.FavoritesUpdated/1.0.0)
---
id: dvelop-actions
name: Actions - Analytics Events
version: 1.0.0
summary: "This AsyncAPI document describes analytics and tracking events emitted by the d.velop Actions service. These events are primarily used for usage tracking and product analysis within the d.velop Analytics Platform."
sends:
- id: dvelop-actions.ExecuteAction
version: 1.0.0
to:
- id: analytics
- id: dvelop-actions.ExecuteEvent
version: 1.0.0
to:
- id: analytics
- id: dvelop-actions.ExecuteRoutineWithAction
version: 1.0.0
to:
- id: analytics
- id: dvelop-actions.ExecuteRoutineWithRelativeURL
version: 1.0.0
to:
- id: analytics
receives: []
---
# Actions - Analytics Events
This AsyncAPI document describes analytics and tracking events emitted by the d.velop Actions service.
These events are primarily used for usage tracking and product analysis within the d.velop Analytics Platform.
## Events Sent
- [dvelop-actions.ExecuteAction](/docs/events/dvelop-actions.ExecuteAction/1.0.0)
- [dvelop-actions.ExecuteEvent](/docs/events/dvelop-actions.ExecuteEvent/1.0.0)
- [dvelop-actions.ExecuteRoutineWithAction](/docs/events/dvelop-actions.ExecuteRoutineWithAction/1.0.0)
- [dvelop-actions.ExecuteRoutineWithRelativeURL](/docs/events/dvelop-actions.ExecuteRoutineWithRelativeURL/1.0.0)
---
id: analytics
name: Analytics
version: 1.0.0
summary: |
Channel used for emitting analytics events from the Actions service
---
## Overview
Channel used for emitting analytics events from the Actions service
## Messages
This channel handles the following messages:
- [dvelop-actions.ExecuteAction](/docs/services/dvelop-actions/events/dvelop-actions.ExecuteAction/1.0.0) - 1.0.0
- [dvelop-actions.ExecuteEvent](/docs/services/dvelop-actions/events/dvelop-actions.ExecuteEvent/1.0.0) - 1.0.0
- [dvelop-actions.ExecuteRoutineWithAction](/docs/services/dvelop-actions/events/dvelop-actions.ExecuteRoutineWithAction/1.0.0) - 1.0.0
- [dvelop-actions.ExecuteRoutineWithRelativeURL](/docs/services/dvelop-actions/events/dvelop-actions.ExecuteRoutineWithRelativeURL/1.0.0) - 1.0.0
## Operations
- sendExecuteAction
- sendExecuteEvent
- sendExecuteRoutineWithAction
- sendExecuteRoutineWithRelativeURL
## Server Endpoints
- **dap_cdp**