Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CronJob is generating the service_name as a Job #2716

Closed
janario opened this issue Mar 6, 2024 · 0 comments · Fixed by #2717
Closed

CronJob is generating the service_name as a Job #2716

janario opened this issue Mar 6, 2024 · 0 comments · Fixed by #2717

Comments

@janario
Copy link
Contributor

janario commented Mar 6, 2024

Component(s)

No response

Describe the issue you're reporting

In CronJob model it generates a few other components:

CronJob > creates Job > creates `Pod``

This is pretty similar to what we have for Deployment:
Deployment > ReplicaSet > Pod

The issue is that when a Job is detect its dynamic name is being used as the ServiceName and not the CronJob and this ends up generating a lot of APM with different name into our provider.

E.g.

  • CronJob: my-job, (*/5 * * * * ...)
  • Job:
    • my-job-28493760 << this is what it is using as the service name
    • my-job-28494300
    • ...
  • Pod
    • my-job-28493760mnhhw
    • my-job-284943005b2c4

Expectation:
It should use the CronJob name as in my-job

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant