Skip to content

Statistics Page not Loading

Summary

For some projects, the Security & Compliance -> Threat Monitoring -> Statistics page fails to load the statistics chart for Container Network Security, even when Prometheus and Cilium are installed via GMAv2.

Steps to reproduce

  1. Install ingress, cilium, and prometheus via GMAv2
  2. Visit the Security & Compliance -> Threat Monitoring -> Statistics page
  3. Observe that the Container Network Security chart does not load

Additional details

From @aturinske:

It seems to be that there is no result (backend returns an empty object with a 202) and the frontend is configured to keep polling the endpoint until it gets a 200, so it never stops loading. I wonder if that is because in the backend the request for this data is async so it is waiting for a response.

Must be a configuration issue elsewhere? 🤷 I used managed apps v1 for https://staging.gitlab.com/defend-team-test/cnp-alert-demo 's cluster (checked the box saying to install Prometheus instead of adding it to the config.yml) and that seemed to work.

Example Project

What is the current bug behavior?

The chart gets stuck in a loading state and never comes out of the loading state.

What is the expected correct behavior?

The chart should load in a reasonable timeframe. If no data is available, then we should display an empty chart.

Relevant logs and/or screenshots

image

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes