@Rajesh Kumar Mishra If the value is coming null then the Request Body JSON schema would be incorrect thereforethe value are not captured correctly. The suggestion would be use the body value
in your screenshoot to generate the schema using the Use sample payload to generate schema
option of your Request trigger
If your generated schema matches the request body that you are sending then the value should be assigned correctly as in the below image when I navigate to the run history
As I have tested with the below sample json input you will not see all the fields as per your screenshoot. You can use the body value of your request and then generate the right schema.
{
"schemaId":"azureMonitorCommonAlertSchema",
"data":{
"essentials":{
"alert ID":"/subscriptions/guid",
"alertRule":"test",
"severity":"Sev4",
"signalType":"Activity Log",
"monitorCondition":"Fired",
"monitoringService":"ServiceHealth",
"alertTargetIDs":[
"/subscriptiions/subscriptionID"
],
"originAlertId":"newid",
"firedDateTime":"2021-10-02T00:40:03.7826873",
"description":"Security advisor",
"essentialsVersion":"1.0",
"alertContextVersion":"1.0"
},
"alertContext":{
"authorization":null,
"channels":1,
"propeties":{
"title":"RCA etc"
}
}
}
}
Please let me know if you still facing the issue.