Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,070
Community Members
 
Community Events
176
Community Groups

Log4j log monitoring

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? 

Kind regards,

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events