Ingress logs are now available for Azure Time Series Insights environments

Azure Time Series Insights has released [Azure Monitor Logs](https://docs.microsoft.com/azure/azure-monitor/platform/data-platform-logs) for streaming [event sources](https://docs.microsoft.com/azure/time-series-insights/concepts-streaming-ingestion-event-sources). You can now query, analyze, and create alerts for errors that occur in the ingress pipeline. If your Azure Time Series Insights environment is only receiving a portion of your data, or if ingestion has stopped, you can now quickly self-diagnose and troubleshoot the issue. The following scenarios can be diagnosed: * Errors when attempting to connect to an event source: * A networking rule is preventing connection * An invalid key was provided, or the key does not have the correct level of access * The IoT hub or Event hub has been deleted * The consumer group is being used elsewhere * Errors when parsing telemetry: * Invalid JSON cannot be deserialzied * An empty JSON payload was received Read [Monitoring Azure Time Series Insights](https://docs.microsoft.com/azure/time-series-insights/how-to-monitor-tsi) for details on how you can use the features of Azure Monitor to analyze and alert on this data. * Features