<p>In kubernetes cluster for microservice application to diagnose the issue we need logs. </p>

<ol>
<li>Is is good idea to use NFS persistent volume for all microservice logs?</li>
<li>If yes, Is it possible to apply log rotation policy on NFS persistent volume based on size or days?</li>
<li>If we use ELK stack with filebeat it will need more resources and learning for customer to get the required log.</li>
</ol>

<p>What will be best approach i.e NFS or ELK stack or mixed?</p>

Mr.Pramod Anarase
<ol>
<li>NFS is ok as long as it is able to offer required performance. </li>
<li>You should apply lifecycle policy at Elasticsearch indices level. Modern Kibana has a nice interface for creation of lifecycle policies and overall monitoring of ES.</li>
<li>Never worked with Filebeat. We use EFK stack - Elasticsearch, Fluentd and Kibana. It works pretty well and is installed only using Helm Charts.</li>
</ol>
