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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Determine what node an issue is created on

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

1 answer

1 accepted

0 votes
Answer accepted

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

What problem would knowing this solve for you?

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.

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.
Like Mario Perfetti likes this

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!

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,193 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you