CPU usage
- -**Descriptions** - -- warning precise-code-intel-worker: 95%+ CPU usage for 10m0s - -**Next steps** - -- Consider increasing CPU limits or scaling out. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-cpu_usage_percentage). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_cpu_usage_percentage" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -memory (RSS)
- -**Descriptions** - -- warning precise-code-intel-worker: 90%+ memory (RSS) for 10m0s - -**Next steps** - -- Consider increasing memory limits or scaling out. -- More help interpreting this metric is available in the [dashboards reference](dashboards#precise-code-intel-worker-memory_rss). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_memory_rss" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container cpu usage total (1m average) across all cores by instance
- -**Descriptions** - -- warning precise-code-intel-worker: 99%+ container cpu usage total (1m average) across all cores by instance - -**Next steps** - -- **Kubernetes:** Consider increasing CPU limits in the the relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `cpus:` of the precise-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-container_cpu_usage). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_container_cpu_usage" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container memory usage by instance
- -**Descriptions** - -- warning precise-code-intel-worker: 99%+ container memory usage by instance - -**Next steps** - -- **Kubernetes:** Consider increasing memory limit in relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `memory:` of precise-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-container_memory_usage). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_container_memory_usage" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container cpu usage total (90th percentile over 1d) across all cores by instance
- -**Descriptions** - -- warning precise-code-intel-worker: 80%+ container cpu usage total (90th percentile over 1d) across all cores by instance for 336h0m0s - -**Next steps** - -- **Kubernetes:** Consider increasing CPU limits in the `Deployment.yaml` for the precise-code-intel-worker service. -- **Docker Compose:** Consider increasing `cpus:` of the precise-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-provisioning_container_cpu_usage_long_term). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_provisioning_container_cpu_usage_long_term" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container memory usage (1d maximum) by instance
- -**Descriptions** - -- warning precise-code-intel-worker: 80%+ container memory usage (1d maximum) by instance for 336h0m0s - -**Next steps** - -- **Kubernetes:** Consider increasing memory limits in the `Deployment.yaml` for the precise-code-intel-worker service. -- **Docker Compose:** Consider increasing `memory:` of the precise-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-provisioning_container_memory_usage_long_term). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_provisioning_container_memory_usage_long_term" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container cpu usage total (5m maximum) across all cores by instance
- -**Descriptions** - -- warning precise-code-intel-worker: 90%+ container cpu usage total (5m maximum) across all cores by instance for 30m0s - -**Next steps** - -- **Kubernetes:** Consider increasing CPU limits in the the relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `cpus:` of the precise-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-provisioning_container_cpu_usage_short_term). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_provisioning_container_cpu_usage_short_term" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container memory usage (5m maximum) by instance
- -**Descriptions** - -- warning precise-code-intel-worker: 90%+ container memory usage (5m maximum) by instance - -**Next steps** - -- **Kubernetes:** Consider increasing memory limit in relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `memory:` of precise-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-provisioning_container_memory_usage_short_term). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_provisioning_container_memory_usage_short_term" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container OOMKILL events total by instance
- -**Descriptions** - -- warning precise-code-intel-worker: 1+ container OOMKILL events total by instance - -**Next steps** - -- **Kubernetes:** Consider increasing memory limit in relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `memory:` of precise-code-intel-worker container in `docker-compose.yml`. -- More help interpreting this metric is available in the [dashboards reference](dashboards#precise-code-intel-worker-container_oomkill_events_total). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_container_oomkill_events_total" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -maximum active goroutines
- -**Descriptions** - -- warning precise-code-intel-worker: 10000+ maximum active goroutines for 10m0s - -**Next steps** - -- More help interpreting this metric is available in the [dashboards reference](dashboards#precise-code-intel-worker-go_goroutines). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_go_goroutines" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -maximum go garbage collection duration
- -**Descriptions** - -- warning precise-code-intel-worker: 2s+ maximum go garbage collection duration - -**Next steps** - -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-go_gc_duration_seconds). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_precise-code-intel-worker_go_gc_duration_seconds" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -percentage pods available
- -**Descriptions** - -- critical precise-code-intel-worker: less than 90% percentage pods available for 10m0s - -**Next steps** - -- Determine if the pod was OOM killed using `kubectl describe pod precise-code-intel-worker` (look for `OOMKilled: true`) and, if so, consider increasing the memory limit in the relevant `Deployment.yaml`. -- Check the logs before the container restarted to see if there are `panic:` messages or similar using `kubectl logs -p precise-code-intel-worker`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-pods_available_percentage). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "critical_precise-code-intel-worker_pods_available_percentage" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -mean blocked seconds per conn request
- -**Descriptions** - -- warning syntactic-indexing: 0.1s+ mean blocked seconds per conn request for 10m0s -- critical syntactic-indexing: 0.5s+ mean blocked seconds per conn request for 10m0s - -**Next steps** - -- Increase SRC_PGSQL_MAX_OPEN together with giving more memory to the database if needed -- Scale up Postgres memory/cpus - [see our scaling guide](https://sourcegraph.com/docs/admin/config/postgres-conf) -- If using GCP Cloud SQL, check for high lock waits or CPU usage in query insights -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-mean_blocked_seconds_per_conn_request). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_mean_blocked_seconds_per_conn_request", - "critical_syntactic-indexing_mean_blocked_seconds_per_conn_request" -] -``` - -*Managed by the Sourcegraph Platform team.* - -CPU usage
- -**Descriptions** - -- warning syntactic-indexing: 95%+ CPU usage for 10m0s - -**Next steps** - -- Consider increasing CPU limits or scaling out. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-cpu_usage_percentage). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_cpu_usage_percentage" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -memory (RSS)
- -**Descriptions** - -- warning syntactic-indexing: 90%+ memory (RSS) for 10m0s - -**Next steps** - -- Consider increasing memory limits or scaling out. -- More help interpreting this metric is available in the [dashboards reference](dashboards#syntactic-indexing-memory_rss). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_memory_rss" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container cpu usage total (1m average) across all cores by instance
- -**Descriptions** - -- warning syntactic-indexing: 99%+ container cpu usage total (1m average) across all cores by instance - -**Next steps** - -- **Kubernetes:** Consider increasing CPU limits in the the relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `cpus:` of the syntactic-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-container_cpu_usage). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_container_cpu_usage" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container memory usage by instance
- -**Descriptions** - -- warning syntactic-indexing: 99%+ container memory usage by instance - -**Next steps** - -- **Kubernetes:** Consider increasing memory limit in relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `memory:` of syntactic-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-container_memory_usage). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_container_memory_usage" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container cpu usage total (90th percentile over 1d) across all cores by instance
- -**Descriptions** - -- warning syntactic-indexing: 80%+ container cpu usage total (90th percentile over 1d) across all cores by instance for 336h0m0s - -**Next steps** - -- **Kubernetes:** Consider increasing CPU limits in the `Deployment.yaml` for the syntactic-code-intel-worker service. -- **Docker Compose:** Consider increasing `cpus:` of the syntactic-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-provisioning_container_cpu_usage_long_term). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_provisioning_container_cpu_usage_long_term" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container memory usage (1d maximum) by instance
- -**Descriptions** - -- warning syntactic-indexing: 80%+ container memory usage (1d maximum) by instance for 336h0m0s - -**Next steps** - -- **Kubernetes:** Consider increasing memory limits in the `Deployment.yaml` for the syntactic-code-intel-worker service. -- **Docker Compose:** Consider increasing `memory:` of the syntactic-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-provisioning_container_memory_usage_long_term). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_provisioning_container_memory_usage_long_term" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container cpu usage total (5m maximum) across all cores by instance
- -**Descriptions** - -- warning syntactic-indexing: 90%+ container cpu usage total (5m maximum) across all cores by instance for 30m0s - -**Next steps** - -- **Kubernetes:** Consider increasing CPU limits in the the relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `cpus:` of the syntactic-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-provisioning_container_cpu_usage_short_term). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_provisioning_container_cpu_usage_short_term" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container memory usage (5m maximum) by instance
- -**Descriptions** - -- warning syntactic-indexing: 90%+ container memory usage (5m maximum) by instance - -**Next steps** - -- **Kubernetes:** Consider increasing memory limit in relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `memory:` of syntactic-code-intel-worker container in `docker-compose.yml`. -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-provisioning_container_memory_usage_short_term). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_provisioning_container_memory_usage_short_term" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -container OOMKILL events total by instance
+percentage pods available
**Descriptions** -- warning syntactic-indexing: 1+ container OOMKILL events total by instance +- critical precise-code-intel-worker: less than 90% percentage pods available for 10m0s **Next steps** -- **Kubernetes:** Consider increasing memory limit in relevant `Deployment.yaml`. -- **Docker Compose:** Consider increasing `memory:` of syntactic-code-intel-worker container in `docker-compose.yml`. -- More help interpreting this metric is available in the [dashboards reference](dashboards#syntactic-indexing-container_oomkill_events_total). +- Determine if the pod was OOM killed using `kubectl describe pod precise-code-intel-worker` (look for `OOMKilled: true`) and, if so, consider increasing the memory limit in the relevant `Deployment.yaml`. +- Check the logs before the container restarted to see if there are `panic:` messages or similar using `kubectl logs -p precise-code-intel-worker`. +- Learn more about the related dashboard panel in the [dashboards reference](dashboards#precise-code-intel-worker-pods_available_percentage). - **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: ```json "observability.silenceAlerts": [ - "warning_syntactic-indexing_container_oomkill_events_total" + "critical_precise-code-intel-worker_pods_available_percentage" ] ``` @@ -3189,67 +2520,44 @@ Generated query for warning alert: `max((max_over_time(cadvisor_container_memorymaximum active goroutines
+mean blocked seconds per conn request
**Descriptions** -- warning syntactic-indexing: 10000+ maximum active goroutines for 10m0s +- warning syntactic-indexing: 0.1s+ mean blocked seconds per conn request for 10m0s +- critical syntactic-indexing: 0.5s+ mean blocked seconds per conn request for 10m0s **Next steps** -- More help interpreting this metric is available in the [dashboards reference](dashboards#syntactic-indexing-go_goroutines). +- Increase SRC_PGSQL_MAX_OPEN together with giving more memory to the database if needed +- Scale up Postgres memory/cpus - [see our scaling guide](https://sourcegraph.com/docs/admin/config/postgres-conf) +- If using GCP Cloud SQL, check for high lock waits or CPU usage in query insights +- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-mean_blocked_seconds_per_conn_request). - **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: ```json "observability.silenceAlerts": [ - "warning_syntactic-indexing_go_goroutines" + "warning_syntactic-indexing_mean_blocked_seconds_per_conn_request", + "critical_syntactic-indexing_mean_blocked_seconds_per_conn_request" ] ``` -*Managed by the Sourcegraph Code Understanding team.* +*Managed by the Sourcegraph Platform team.*maximum go garbage collection duration
- -**Descriptions** - -- warning syntactic-indexing: 2s+ maximum go garbage collection duration - -**Next steps** - -- Learn more about the related dashboard panel in the [dashboards reference](dashboards#syntactic-indexing-go_gc_duration_seconds). -- **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: - -```json -"observability.silenceAlerts": [ - "warning_syntactic-indexing_go_gc_duration_seconds" -] -``` - -*Managed by the Sourcegraph Code Understanding team.* - -CPU usage
-Refer to the [alerts reference](alerts#precise-code-intel-worker-cpu_usage_percentage) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=100700` on your Sourcegraph instance. @@ -12284,9 +12284,7 @@ max by (name) (container_memory_working_set_bytes{name=~"^precise-code-intel-worMemory (RSS)
-The total anonymous memory in use by the application, which includes Go stack and heap. This memory is is non-reclaimable, and high usage may trigger OOM kills. Note: the metric is named RSS because to match the cadvisor name, but `anonymous` is more accurate." - -Refer to the [alerts reference](alerts#precise-code-intel-worker-memory_rss) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=100710` on your Sourcegraph instance. @@ -12390,7 +12388,7 @@ count by(name) ((time() - container_last_seen{name=~"^precise-code-intel-worker.Container cpu usage total (1m average) across all cores by instance
-Refer to the [alerts reference](alerts#precise-code-intel-worker-container_cpu_usage) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=100801` on your Sourcegraph instance. @@ -12412,7 +12410,7 @@ cadvisor_container_cpu_usage_percentage_total{name=~"^precise-code-intel-worker.Container memory usage by instance
-Refer to the [alerts reference](alerts#precise-code-intel-worker-container_memory_usage) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=100802` on your Sourcegraph instance. @@ -12461,7 +12459,7 @@ sum by(name) (rate(container_fs_reads_total{name=~"^precise-code-intel-worker.*"Container cpu usage total (90th percentile over 1d) across all cores by instance
-Refer to the [alerts reference](alerts#precise-code-intel-worker-provisioning_container_cpu_usage_long_term) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=100900` on your Sourcegraph instance. @@ -12483,7 +12481,7 @@ quantile_over_time(0.9, cadvisor_container_cpu_usage_percentage_total{name=~"^prContainer memory usage (1d maximum) by instance
-Refer to the [alerts reference](alerts#precise-code-intel-worker-provisioning_container_memory_usage_long_term) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=100901` on your Sourcegraph instance. @@ -12505,7 +12503,7 @@ max_over_time(cadvisor_container_memory_usage_percentage_total{name=~"^precise-cContainer cpu usage total (5m maximum) across all cores by instance
-Refer to the [alerts reference](alerts#precise-code-intel-worker-provisioning_container_cpu_usage_short_term) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=100910` on your Sourcegraph instance. @@ -12527,7 +12525,7 @@ max_over_time(cadvisor_container_cpu_usage_percentage_total{name=~"^precise-codeContainer memory usage (5m maximum) by instance
-Refer to the [alerts reference](alerts#precise-code-intel-worker-provisioning_container_memory_usage_short_term) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=100911` on your Sourcegraph instance. @@ -12549,10 +12547,7 @@ max_over_time(cadvisor_container_memory_usage_percentage_total{name=~"^precise-cContainer OOMKILL events total by instance
-This value indicates the total number of times the container main process or child processes were terminated by OOM killer. -When it occurs frequently, it is an indicator of underprovisioning. - -Refer to the [alerts reference](alerts#precise-code-intel-worker-container_oomkill_events_total) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=100912` on your Sourcegraph instance. @@ -12576,9 +12571,7 @@ max by (name) (container_oom_events_total{name=~"^precise-code-intel-worker.*"})Maximum active goroutines
-A high value here indicates a possible goroutine leak. - -Refer to the [alerts reference](alerts#precise-code-intel-worker-go_goroutines) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=101000` on your Sourcegraph instance. @@ -12600,7 +12593,7 @@ max by(instance) (go_goroutines{job=~".*precise-code-intel-worker"})Maximum go garbage collection duration
-Refer to the [alerts reference](alerts#precise-code-intel-worker-go_gc_duration_seconds) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-code-intel-worker?viewPanel=101001` on your Sourcegraph instance. @@ -13213,7 +13206,7 @@ sum by (app_name, db_name) (increase(src_pgsql_conns_closed_max_idle_time{app_naCPU usage
-Refer to the [alerts reference](alerts#syntactic-indexing-cpu_usage_percentage) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100400` on your Sourcegraph instance. @@ -13283,9 +13276,7 @@ max by (name) (container_memory_working_set_bytes{name=~"^syntactic-code-intel-wMemory (RSS)
-The total anonymous memory in use by the application, which includes Go stack and heap. This memory is is non-reclaimable, and high usage may trigger OOM kills. Note: the metric is named RSS because to match the cadvisor name, but `anonymous` is more accurate." - -Refer to the [alerts reference](alerts#syntactic-indexing-memory_rss) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100410` on your Sourcegraph instance. @@ -13389,7 +13380,7 @@ count by(name) ((time() - container_last_seen{name=~"^syntactic-code-intel-workeContainer cpu usage total (1m average) across all cores by instance
-Refer to the [alerts reference](alerts#syntactic-indexing-container_cpu_usage) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100501` on your Sourcegraph instance. @@ -13411,7 +13402,7 @@ cadvisor_container_cpu_usage_percentage_total{name=~"^syntactic-code-intel-workeContainer memory usage by instance
-Refer to the [alerts reference](alerts#syntactic-indexing-container_memory_usage) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100502` on your Sourcegraph instance. @@ -13460,7 +13451,7 @@ sum by(name) (rate(container_fs_reads_total{name=~"^syntactic-code-intel-worker.Container cpu usage total (90th percentile over 1d) across all cores by instance
-Refer to the [alerts reference](alerts#syntactic-indexing-provisioning_container_cpu_usage_long_term) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100600` on your Sourcegraph instance. @@ -13482,7 +13473,7 @@ quantile_over_time(0.9, cadvisor_container_cpu_usage_percentage_total{name=~"^syContainer memory usage (1d maximum) by instance
-Refer to the [alerts reference](alerts#syntactic-indexing-provisioning_container_memory_usage_long_term) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100601` on your Sourcegraph instance. @@ -13504,7 +13495,7 @@ max_over_time(cadvisor_container_memory_usage_percentage_total{name=~"^syntacticContainer cpu usage total (5m maximum) across all cores by instance
-Refer to the [alerts reference](alerts#syntactic-indexing-provisioning_container_cpu_usage_short_term) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100610` on your Sourcegraph instance. @@ -13526,7 +13517,7 @@ max_over_time(cadvisor_container_cpu_usage_percentage_total{name=~"^syntactic-coContainer memory usage (5m maximum) by instance
-Refer to the [alerts reference](alerts#syntactic-indexing-provisioning_container_memory_usage_short_term) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100611` on your Sourcegraph instance. @@ -13548,10 +13539,7 @@ max_over_time(cadvisor_container_memory_usage_percentage_total{name=~"^syntacticContainer OOMKILL events total by instance
-This value indicates the total number of times the container main process or child processes were terminated by OOM killer. -When it occurs frequently, it is an indicator of underprovisioning. - -Refer to the [alerts reference](alerts#syntactic-indexing-container_oomkill_events_total) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100612` on your Sourcegraph instance. @@ -13575,9 +13563,7 @@ max by (name) (container_oom_events_total{name=~"^syntactic-code-intel-worker.*"Maximum active goroutines
-A high value here indicates a possible goroutine leak. - -Refer to the [alerts reference](alerts#syntactic-indexing-go_goroutines) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100700` on your Sourcegraph instance. @@ -13599,7 +13585,7 @@ max by(instance) (go_goroutines{job=~".*syntactic-code-intel-worker"})Maximum go garbage collection duration
-Refer to the [alerts reference](alerts#syntactic-indexing-go_gc_duration_seconds) for 1 alert related to this panel. +This panel has no related alerts. To see this panel, visit `/-/debug/grafana/d/syntactic-indexing/syntactic-indexing?viewPanel=100701` on your Sourcegraph instance.