@@ -397,8 +397,13 @@ For any questions, reach out to [#s_developer_experience](https://gitlab.enterpr
## Monitoring
*[Stage Group dashboard on Grafana](https://dashboards.gitlab.net/d/stage-groups-threat_insights/stage-groups-threat-insights-group-dashboard)
*[Largest Contentful Paint (LCP)](https://dashboards.gitlab.net/d/sftijGFMz/sitespeed-lcp-leaderboard?from=now-90d&orgId=1&to=now&refresh=30s&var-namespace=sitespeed_io&var-path=desktop&var-domains=gitlab_com&var-pages=Secure_Instance_Dashboard_Settings&var-pages=Secure_Instance_Security_Dashboard&var-pages=Secure_Instance_Vulnerability_Report&var-pages=Secure_Group_Security_Dashboard&var-pages=Secure_Group_Vulnerability_Report&var-pages=Secure_Project_Security_Dashboard&var-pages=Secure_Project_Vulnerability_Report&var-pages=Secure_Standalone_Vulnerability&var-browser=chrome&var-connectivity=cable&var-function=median) for our web pages.
We have two Slack alerts which post to our Slack channel when there are unexpected errors in the vulnerability ingestion
or SBoM ingestion processes respectively. These errors are usually indicative of a bug which is causing ingestion to fail.
Check the "job status ratio" chart on the Elastic dashboard to determine the severity of the bug.
These alerts can be tuned by editing the [watcher definitions](https://gitlab.com/gitlab-com/gl-infra/observability/elastic-cloud/-/tree/main/environments/gitlab-logs-prod/watchers?ref_type=heads).