nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Facing performance issues ran log analyzer need help figuring how to go deeper

Martynas_hofhom

We've been facing performance issues recently, I went ahead and ran log analyzer through our access logs, I've read through Atlassian's documentation and pretty much all the categories makes sense except one. I am very keen to know what exactly falls under "REST_OTHER"?

Accepted answers

Nic Brough -Adaptavist-

It's all the external REST API calls being made by other systems (including Confluence reports that use gadgets or the Jira macro) and the calls Jira dashboards make to itself

All comments

Nic Brough -Adaptavist-

It's all the external REST API calls being made by other systems (including Confluence reports that use gadgets or the Jira macro) and the calls Jira dashboards make to itself

Martynas_hofhom

Cool thanks, do you happen to know if there's an easy, clean way to look into them deeper as in exactly what kind of requests are being made other than manually going through the access logs?

Nic Brough -Adaptavist-

No, I'm afraid the log analyser doesn't go deeper, I believe we're stuck with going through access logs (I usually stick them through Splunk or other log file analysers)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server