Missing transaction for one background job worker

Hey there, we are experiencing a problem with gathering transaction data from our workers working in the background.

We are running multiple workers on multiple instances with the same command and base running code (the difference are deeper in the code implementation for each job consumer). They are running on python and we run them wrapped with newrelic-agent and configure each worker run with newrelic.agent.BackgroundTask to give it a name related to the task it is performing. Also we group them by the integration type, they are referring. So say TaskX is for IntegrationA group but also TaskX is for IntegrationB.

So when I go to the transaction table. I can see IntegrationA/TaskX and IntegrationB/TaskX. It works for all of our workers… except one.

It does not show up at all in our Transactions table. Given the example above it is like:

  • IntegrationA/TaskX - shows up
  • IntegrationB/TaskX - shows up
  • IntegrationC/TaskX - not showing up

But all other tasks from IntegrationC show up at the same time. All tasks from A or B also are there with no issue. There’s only this one missing. And since all tasks are running with the very same command (except the name of worker and integration) and very same code (same until BackgroundTask is defined), it should be there. The task is processing as we see changes and get logs from the worker.

Any idea, what we should do?

In total we have 85 transactions - don’t think it is matter of any limits. We have multiple workers processes running on multiple instances for the transaction, but we also do for others, so I don’t think this should be the issue.

I tried to search for anything similar, but with no success.

Our transaction table is: https://one.newrelic.com/launcher/nr1-core.explorer?launcher=eyJzZWxlY3RlZEluc3RhbmNlIjpudWxsfQ==&pane=eyJuZXJkbGV0SWQiOiJhcG0tbmVyZGxldHMudHJhbnNhY3Rpb25zIiwiZW50aXR5SWQiOiJOall5T0RVMWZFRlFUWHhCVUZCTVNVTkJWRWxQVG53MU1UazNPVGN4IiwidHJhbnNhY3Rpb25UeXBlIjp7InRyYW5zYWN0aW9uVHlwZSI6Ik90aGVyIiwic3VidHlwZSI6IndpeFJldGFpbGVyV29ya2VycyJ9LCJzaG93VHJhbnNhY3Rpb25zVGFibGUiOnRydWUsImRyaWxsZG93biI6bnVsbCwic2VsZWN0ZWRTZXJpZXMiOm51bGx9&sidebars[0]=eyJuZXJkbGV0SWQiOiJucjEtY29yZS5hY3Rpb25zIiwiZW50aXR5SWQiOiJOall5T0RVMWZFRlFUWHhCVUZCTVNVTkJWRWxQVG53MU1UazNPVGN4Iiwic2VsZWN0ZWROZXJkbGV0Ijp7Im5lcmRsZXRJZCI6ImFwbS1uZXJkbGV0cy50cmFuc2FjdGlvbnMifX0=&platform[timeRange][begin_time]=1601903280000&platform[timeRange][end_time]=1601905140000&platform[$isFallbackTimeRange]=false

There’s no transaction for worker we have properly displayed for another integration.
This is the same worker that is monitored properly for another integration:
https://one.newrelic.com/launcher/nr1-core.explorer?launcher=eyJzZWxlY3RlZEluc3RhbmNlIjpudWxsfQ==&pane=eyJuZXJkbGV0SWQiOiJhcG0tbmVyZGxldHMudHJhbnNhY3Rpb25zIiwiZW50aXR5SWQiOiJOall5T0RVMWZFRlFUWHhCVUZCTVNVTkJWRWxQVG53MU1UazNPVGN4IiwidHJhbnNhY3Rpb25UeXBlIjp7InRyYW5zYWN0aW9uVHlwZSI6Ik90aGVyIiwic3VidHlwZSI6InNob3BpZnlSZXRhaWxlcldvcmtlcnMifSwic2VsZWN0ZWRJbnN0YW5jZSI6bnVsbCwic29ydCI6InN1bSIsImRyaWxsZG93biI6eyJ0cmFuc2FjdGlvbk5hbWUiOiJPdGhlclRyYW5zYWN0aW9uL3Nob3BpZnlSZXRhaWxlcldvcmtlcnMvVXBkYXRlUHJvZHVjdFdlYmhvb2tRdWV1ZVByb2Nlc3NvciJ9LCJzZWxlY3RlZFNlcmllcyI6Ijg0MThjY2YwMTE3NjRiMTNkNjJiMTI2OTBjZjA4ZThhN2JmOGY3MzMifQ==&sidebars[0]=eyJuZXJkbGV0SWQiOiJucjEtY29yZS5hY3Rpb25zIiwiZW50aXR5SWQiOiJOall5T0RVMWZFRlFUWHhCVUZCTVNVTkJWRWxQVG53MU1UazNPVGN4Iiwic2VsZWN0ZWROZXJkbGV0Ijp7Im5lcmRsZXRJZCI6ImFwbS1uZXJkbGV0cy50cmFuc2FjdGlvbnMifX0=&platform[timeRange][begin_time]=1601903280000&platform[timeRange][end_time]=1601905140000&platform[$isFallbackTimeRange]=false

Somehow it started to show up today, even though the data contains some traces from 2 days ago. Pretty odd. Anyway, this ticket is no longer valid.

@janusz.kamienski Thank you for providing an update on your current situation. Glad to hear that it seems to have ironed itself out. What a mystery though… :slight_smile: