You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-grid/event-schema-media-services.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ See [Schema examples](#event-schema-examples) that follow.
53
53
54
54
| Event type | Description |
55
55
| ---------- | ----------- |
56
-
| Microsoft.Media.JobOutputProgress| This event reflects the job processing progress, from 0% to 100%. The service attempts to send an event if there has been 5% or greater increase in the progress value or it has been more than 30 seconds since the last event (heartbeat). The progress value isn't guaranteed to start at 0%, or to reach 100%, nor is it guaranteed to increase at a constant rate over time. This event should not be used to determine that the processing has been completed – you should instead use the state change events.|
56
+
| Microsoft.Media.JobOutputProgress| This event reflects the job processing progress, from 0% to 100%. The service attempts to send an event if there has been 5% or greater increase in the progress value or it has been more than 30 seconds since the last event (heartbeat). The progress value isn't guaranteed to start at 0%, or to reach 100%, nor is it guaranteed to increase at a constant rate over time. This event shouldn't be used to determine that the processing has been completed – you should instead use the state change events.|
57
57
58
58
See [Schema examples](#event-schema-examples) that follow.
59
59
@@ -894,10 +894,10 @@ The data object has the following properties:
894
894
|`nonIncreasingCount`| integer | Number of data chunks with timestamps in the past were received in last 20 seconds. |
895
895
|`unexpectedBitrate`| bool | If expected and actual bitrates differ by more than allowed limit in last 20 seconds. It's true if and only if, incomingBitrate >= 2* bitrate OR incomingBitrate <= bitrate/2 OR IncomingBitrate = 0. |
896
896
|`state`| string | State of the live event. |
897
-
|`healthy`| bool | Indicates whether ingest is healthy based on the counts and flags. Healthy is true if overlapCount = 0 && discontinuityCount = 0 && nonIncreasingCount = 0 && unexpectedBitrate = false. |
897
+
|`healthy`| bool | Indicates whether ingest is healthy, based on the counts and flags. Healthy is true if overlapCount = 0 && discontinuityCount = 0 && nonIncreasingCount = 0 && unexpectedBitrate = false. |
898
898
|`lastFragmentArrivalTime`| string |The last time stamp in UTC that a fragment arrived at the ingest endpoint. Example date format is "2020-11-11 12:12:12:888999" |
899
-
|`ingestDriftValue`| string | Indicates the speed of delay, in seconds-per-minute, of the incoming audio or video data during the last minute. The value is greater than zero if data is arriving to the live event slower than expected in the last minute; zero if data arrived with no delay; and "n/a" if no audio or video data was received. For example, if you have a contribution encoder sending in live content, and it is slowing down due to processing issues, or network latency, it may be only able to deliver a total of 58 seconds of audio or video in a one minute period. This would be reported as 2 seconds-per-minute of drift. If the encoder is able to catch up and send all 60 seconds or more of data every minute you will see this value reported as 0. If there was a disconnection, or discontinuity from the encoder, this value may still display as 0, as it does not account for breaks in the data - only data that is delayed in timestamps.|
900
-
|`transcriptionState`| string | This value is "On" for audio track heartbeats if live transcription is turned on, otherwise you will see an empty string. This state is only applicable totracktype of "audio" for Live transcription. All other tracks will have an empty value.|
899
+
|`ingestDriftValue`| string | Indicates the speed of delay, in seconds-per-minute, of the incoming audio or video data during the last minute. The value is greater than zero if data is arriving to the live event slower than expected in the last minute; zero if data arrived with no delay; and "n/a" if no audio or video data was received. For example, if you have a contribution encoder sending in live content, and it's slowing down due to processing issues, or network latency, it may be only able to deliver a total of 58 seconds of audio or video in a one minute period. This would be reported as 2 seconds-per-minute of drift. If the encoder is able to catch up and send all 60 seconds or more of data every minute you'll see this value reported as 0. If there was a disconnection, or discontinuity from the encoder, this value may still display as 0, as it doesn't account for breaks in the data - only data that is delayed in timestamps.|
900
+
|`transcriptionState`| string | This value is "On" for audio track heartbeats if live transcription is turned on, otherwise you'll see an empty string. This state is only applicable to`tracktype` of `audio` for Live transcription. All other tracks will have an empty value.|
901
901
|`transcriptionLanguage`| string | The language code (in BCP-47 format) of the transcription language. For example “de-de” indicates German (Germany). The value is empty for the video track heartbeats, or when live transcription is turned off. |
902
902
903
903
@@ -978,7 +978,7 @@ An event has the following top-level data:
978
978
979
979
| Property | Type | Description |
980
980
| -------- | ---- | ----------- |
981
-
|`topic`| string | The event grid topic. This property has the resource ID for the Media Services account. |
981
+
|`topic`| string | The Event Grid topic. This property has the resource ID for the Media Services account. |
982
982
|`subject`| string | The resource path for the Media Services channel under the Media Services account. Concatenating the topic and subject give you the resource ID for the job. |
983
983
|`eventType`| string | One of the registered event types for this event source. For example, "Microsoft.Media.JobStateChange". |
984
984
|`eventTime`| string | The time the event is generated based on the provider's UTC time. |
@@ -993,7 +993,7 @@ An event has the following top-level data:
993
993
994
994
| Property | Type | Description |
995
995
| -------- | ---- | ----------- |
996
-
|`source`| string | The event grid topic. This property has the resource ID for the Media Services account. |
996
+
|`source`| string | The Event Grid topic. This property has the resource ID for the Media Services account. |
997
997
|`subject`| string | The resource path for the Media Services channel under the Media Services account. Concatenating the topic and subject give you the resource ID for the job. |
998
998
|`type`| string | One of the registered event types for this event source. For example, "Microsoft.Media.JobStateChange". |
999
999
|`time`| string | The time the event is generated based on the provider's UTC time. |
@@ -1009,6 +1009,6 @@ See [Register for job state change events](/azure/media-services/latest/monitori
1009
1009
1010
1010
## See also
1011
1011
1012
-
-[EventGrid .NET SDK that includes Media Service events](https://www.nuget.org/packages/Microsoft.Azure.EventGrid/)
1012
+
-[Event Grid .NET SDK that includes Media Service events](https://www.nuget.org/packages/Microsoft.Azure.EventGrid/)
1013
1013
-[Definitions of Media Services events](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.Media/stable/2018-01-01/MediaServices.json)
0 commit comments