You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Component(s)
No response
Describe the issue you're reporting
In CronJob model it generates a few other components:
CronJob
> createsJob
> 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.
Expectation:
It should use the CronJob name as in
my-job
The text was updated successfully, but these errors were encountered: