Adding another option to reduce cost.

Author: RohitRanjanMS

articles/azure-functions/configure-monitoring.md

@@ -354,6 +354,8 @@ Function apps are an essential part of solutions that can cause high volumes of
 
 The generated telemetry can be consumed in real-time dashboards, alerting, detailed diagnostics, and so on. Depending on how the generated telemetry is consumed, you need to define a strategy to reduce the volume of data generated. This strategy allows you to properly monitor, operate, and diagnose your function apps in production. Consider the following options:
 
++ **Use the right table plan**:  [Table plans](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-platform-logs#table-plans:~:text=business%20needs.-,Table%20plans,-You%20can%20use) let you manage data costs based on how often you use the data in a table and the type of analysis you need the data for. Choosing the `Basic` plan can significantly lower expenses, though it lacks some features available in the `Analytics` plan.
+  
 + **Use sampling**: As mentioned [previously](#configure-sampling), sampling helps to dramatically reduce the volume of telemetry events ingested while maintaining a statistically correct analysis. It could happen that even using sampling you still get a high volume of telemetry. Inspect the options that [adaptive sampling](/azure/azure-monitor/app/sampling#configuring-adaptive-sampling-for-aspnet-applications) provides to you. For example, set the `maxTelemetryItemsPerSecond` to a value that balances the volume generated with your monitoring needs. Keep in mind that the telemetry sampling is applied per host executing your function app.
 
 + **Default log level**: Use `Warning` or `Error` as the default value for all telemetry categories. Later, you can decide which [categories](#configure-categories) you want to set at the `Information` level, so that you can monitor and diagnose your functions properly.