Skip to content

fixing-error #21778

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 3, 2025
Merged

fixing-error #21778

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
051ab32
fixing-error
sujitnewrelic Sep 24, 2025
6714231
Merge branch 'develop' into fixing-build-fail-error
sujitnewrelic Oct 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions ...synthetics/synthetic-monitoring/private-locations/job-manager-configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1881,7 +1881,7 @@ When `completions` is greater than 1, pods with a "Completed" status will remain

A Kubernetes Job age of 5 minutes (`kubectl get jobs -n YOUR_NAMESPACE`) is a conservative target to account for variability in how long it takes pods to complete and how many synthetics jobs need to run per minute (jobs rate). The following equations can be used as a starting point for `completions` and `parallelism` for each runtime. Adjustments may need to be made based on observations of private location queue growth.

```m
```math
completions = 300 / avg job duration (s)
parallelism = synthetics jobs per 5 minutes / completions
```
Expand Down Expand Up @@ -1963,10 +1963,10 @@ If your `parallelism` settings is working well to keep the queue at zero, settin

It's important to note that the `completions` value should not be too large or the CronJob will experience warning events like the following:

```
```sql
8m40s Warning TooManyMissedTimes cronjob/synthetics-node-browser-runtime too many missed start times: 101. Set or decrease .spec.startingDeadlineSeconds or check clock skew
```

<Callout variant="tip">
Please keep in mind that New Relic is not liable for any modifications you make to the synthetics job manager files.
</Callout>
New Relic is not liable for any modifications you make to the synthetics job manager files.
</Callout>
Loading