You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Microsoft Monitoring Agent has limitations they refer to as "criteria" which must be adhered to in order for it to successfully collect logs (see https://docs.microsoft.com/en-us/azure/azure-monitor/agents/data-sources-custom-logs) i.e. log rotation not supported which is the default of Confluence and Jira. ( Servers are also on Azure Vm.s)
log4j in Jira and Confluence out of the box does not support the requirements (or at least I am not experienced enough to figure it out).
Is there any tools or solutions for this ? We need to collect our logs here but our workaround of "appending the contents to a single file for each day from which Microsoft Monitoring Agent is able to collect logs successfully and upload " causes too much IO in the system and causes performance problems & crashes for jira & confluence.
Any suggestions ? How can we send these logs to Azure shortly?
But I see that these constraints still apply on Linux no ? Can you help withe below queries ?
1. Which all log files are you forwarding to Log Analytics ? audit log, catalina log, custom script logs etc ?
2. Are you using File pattern or directory ? I think directory must have older log files as well..does Azure Analytics handle them fine ?
3. Are you by any chance using App Insights & VM Insights as well ?
Thank you in Advance !