Azure Monitor doesn't support circular log rolling. Reconfigure server logs to roll daily instead. You need to provide a modified log configuration file, which is described in section Main Logs.

This is an example of modified appender configuration for all.log. Logs will roll over to a new log file every day, file names will contain the date, and files will be kept for 7 days.

<RollingFile name="allAppender"
    filePattern="${sys:clover.clover.home}/cloverlogs/all.%d{yyyy-MM-dd}.log">
    <PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss,SSS}[%15.15t] %-16.16c{1} %-5p %-3X{runId} %m%n" charset="UTF-8" />
    <Policies>
        <TimeBasedTriggeringPolicy />
    </Policies>
    <DirectWriteRolloverStrategy>
        <Delete basePath="${sys:clover.clover.home}/cloverlogs" followLinks="true">
            <IfFileName glob="all*.log" />
            <IfLastModified age="7d" />
        </Delete>
    </DirectWriteRolloverStrategy>
</RollingFile>

Connect the virtual machine to the Log Analytics workspace. Select the VM in the portal, select Logs in the left menu and click Enable to make the connection. Choose the workspace you have created in the previous step. This will automatically install an extension on the VM. This will take several minutes, wait until the process finishes.

Figure 12.24. Azure VM - enabling Logs

Now we need to define which logs should be sent to Azure Monitor. We will use the provided Custom Log option. Follow steps to add Custom Log data sources in Azure documentation. You will need to add a separate source for every log type you want to collect.

The most important server log file is all log. To collect the main log, we recommend following setup for Custom Log:

Another useful log to collect is performance log. For performance log we recommend following setup:

Do not forget to enable option Apply below configuration to my linux machines and to save the configuration.

Figure 12.25. Two custom log data sources

After you save the above configuration, it might take several hours before the collected log content will be available to view in Azure Portal. After that, you can view and query the collected logs in Log Analytics workspace. To start exploring the logs, follow Log Analytics tutorial.

Locate and open Network Security Group of the server. It’s in the same Resource Group where the server is deployed, next to all the other resources.

Figure 12.26. Azure resources - network security group

Add a new Inbound security rule to allow access from Let’s Encrypt servers. Set following properties:

Find the Virtual Machine resource and restart it. During its startup, the server automatically attempts a certificate renewal if the expiry time is 30 days or less.

Access the Server Console on HTTPS in your browser and verify that certificate has been renewed. You can check it by inspecting the lock icon next to the address box of the browser and checking the certificate validity. Your certificate should be valid for the next 90 days.

Remove the Inbound security rule you added in step 2. It is no longer necessary.

Create /var/clover/conf/customCertificate.jks keystore with your own server certificate. Do not use or modify the already existing file serverCertificate.jks - it is used and overwritten by automation scripts.

Modify the /opt/clover/tomcat/conf/server.xml Tomcat configuration file to use your customCertificate.jks file instead of serverCertificate.jks.

Modify files jmx-conf-core.properties and jmx-conf-worker.properties in directory /var/clover/conf/ to use your customCertificate.jks file instead of serverCertificate.jks.