An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
Hi Anjali Gobari,
we don't get NodePID pressure by default from the Log analytics workspace. Node PID pressure occurs when a node is running too many processes and is running out of process IDs. Unlike memory or disk metrics, this isn't a standard performance counter, but we can write Bash script to fetch the Node PID pressure status and send those metrics to log analytics by using Log Analytics HTTP Data Collector. Then the data appears in custom log table. From that table, we can fetch the NodePID pressure details.
Please let me know if you have any questions.
Thank you