Hello Sankeerthana Desireddy,
**Thank you for submitting your question on Microsoft Q&A.
**
The absence of logs from your Notification Hub in the AzureDiagnostics table, even with correct configuration, often points to a specific logging detail or a delay in the data pipeline. Since you've already recreated the diagnostic settings, this is likely a more nuanced issue than a basic misconfiguration.
First, double-check your diagnostic settings. Make sure the "OperationalLogs" category is enabled this is essential for capturing the management and test notification activity you’re tracking. Also, verify your collection mode: if you’re using resource-specific mode, logs will appear in the NHOperationLogs table, not AzureDiagnostics. Adjust your queries accordingly.
Remember, Azure’s diagnostic pipeline isn’t real-time. There can be a delay of several minutes before logs show up in Log Analytics. Even after sending a test notification, you may need to wait before the data is available.
To confirm log arrival, use a targeted KQL query in Log Analytics. For AzureDiagnostics, try:
AzureDiagnostics
| where ResourceProvider == "MICROSOFT.NOTIFICATIONHUBS"
| where ResourceId contains "VN-a99fb"
| order by TimeGenerated desc
| take 50
If you’re using resource-specific mode, use:
NHOperationLogs
| where ResourceId contains "VN-a99fb"
| order by TimeGenerated desc
| take 50
Finally, ensure your test notifications are actually reaching the Notification Hub and generating events. Check the hub’s Metrics in the Azure Portal for “Incoming requests” or “Successful sends.” If metrics show activity but logs are missing, the issue is with the diagnostic pipeline; if metrics are flat, the notifications aren’t reaching the hub.