Determine what node an issue is created on

[Mario Perfetti]

Is there any way to determine what node an issue was created on, other than the JIRA logs?

[Nic Brough -Adaptavist- · Accepted solution]

Not unless you've configured something to capture it (outside the logs)

What problem would knowing this solve for you?

[Mario Perfetti]

Thanks Nic! I figured as much upon further reading.  It's more information for us since we integrate the issues from JIRA into downstream systems and know which node the issue was created on would help us with trouble shooting some data flows.  It really wouldn't "solve" any problem for us.

[Nic Brough -Adaptavist-]

My choice of "problem" probably was quite a bad choice, sorry. 

I can phrase "knowing where your data is flowing" as a perfectly good definition of a "problem to solve".

I've seen that done in three different ways very broadly:

• On a larger DC setup, knock one node off the load balancer for users and direct all REST interaction to it.  There's some quirks with it (Jira talks to itself in some cases, so a human using a browser can cause REST calls to the node from Jira or gadgets in Confluence etc, but they're a lot easier to filter out than "drinking from the firehose")
• When interacting via REST, set something up that you ask your users to do when they make REST calls (only really works for bespoke automations where you have friendly and helpful people willing to code for it)
• As you already suggested - logging.  But improving it - increased logging can help and getting a good tool to do log analysis is a good all-round solution.

[Mario Perfetti]

Thanks.. sorry for the late response.  We don't have a very large DC, but still think that knocking out one node may be the only way to do this. And these calls aren't being initiated by humans, I suspect that upstream process is making a duplicate call but we're still trying to track that down.  Thanks again!