summaryrefslogtreecommitdiff
path: root/app/assets/javascripts/performance_bar/components/performance_bar_app.vue
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-04-121-9/+11
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-04-111-3/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-04-061-4/+19
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-04-031-20/+29
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-03-211-0/+15
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-11-181-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-06-201-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-06-051-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-05-251-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-03-111-0/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-02-101-0/+12
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-10-041-5/+17
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-10-011-0/+9
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-09-091-1/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-09-021-2/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-07-281-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-05-271-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-05-261-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-04-081-4/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-03-241-6/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-03-051-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-02-181-0/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-02-111-7/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-02-111-0/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-02-011-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-01-221-3/+12
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-10-051-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-08-261-0/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-06-161-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-05-281-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-05-221-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-061-1/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-291-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-261-0/+12
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-251-0/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-301-4/+4
|
* Disable vue-i18n for non-autofix filesEzekiel Kigbo2019-08-081-1/+0
| | | | | | | Disables the vue-i18n eslint rules for files that are not able to be autofixed, this will stop these offences causing pipeline failures but they will need manual fixing.
* Remove GC metrics from performance barSean McGivern2019-08-061-6/+0
| | | | | | These were disabled in production mode, but that also broke the rest of the performance bar. As they were only enabled in development mode, we can just remove them for now.
* Remove line profiler from performance barSean McGivern2019-07-301-23/+0
| | | | | | | | | 1. The output isn't great. It can be hard to find hotspots and, even when you do find them, to find why those are hotspots. 2. It uses some jQuery-specific frontend code which we can remove now that we don't have this any more. 3. It's only possible to profile the initial request, not any subsequent AJAX requests.
* Replace peek-pg with our own implementationremove-peek-pgSean McGivern2019-07-261-5/+7
| | | | | | | | | | This uses an ActiveRecord subscriber to get queries and calculate the total query time from that. This means that the total will always be consistent with the queries in the table. It does however mean that we could potentially miss some queries that don't go through ActiveRecord. Making this change also allows us to unify the response JSON a little bit, making the frontend slightly simpler as a result.
* Autofix i18n lints for vue filesEzekiel Kigbo2019-07-251-2/+2
| | | | | Autofixes additional linting errors found in vue files.
* Add Rugged calls to performance barStan Hu2019-07-231-0/+6
| | | | | | This will help diagnose the source of excessive I/O from Rugged calls. To implement this, we need to obtain the full list of arguments sent to each request method.
* Add Redis call details in Peek performance barsh-improve-redis-peekStan Hu2019-07-021-9/+6
| | | | | | | | | | | | Since Redis timings appear to be increasing in production, this change makes it easier to see what exactly which queries are being called and where. This is done by prepending modules in peek-redis to store the call details. This commit redact values for all SET commands (e.g. HMSET, GETSET, etc.).
* Namespace performance bar translationsvue-i18n-js-performance-bar-directoryEzekiel Kigbo2019-06-281-6/+6
| | | | Added additional translations
* Vue-i18n: app/assets/javascripts/performance_bar/ directoryEzekiel Kigbo2019-06-271-6/+8
| | | | | i18n linting for .vue files under the app/assets/javascripts/performance_bar/ directory
* Add QA tests for the performance bar60356-add-qa-tests-for-the-performance-barSean McGivern2019-04-161-1/+1
| | | | | | | | These are very high-level. Currently, they test: 1. That the performance bar appears. 2. That it has detailed metrics for Postgres and Gitaly. 3. That AJAX requests are included in the request selector.
* Provide a performance bar link to the Jaeger UIan-peek-jaegerAndrew Newdigate2019-02-081-0/+7
| | | | | | | | | | Jaeger is a distributed tracing tool. This change adds a "Tracing" link to the performance bar to directly link to a current request in Jaeger. This is useful for two reasons: 1 - it provides affordance to developers that the distributed tracing tool is available, so that it can quickly be discovered. 2 - it allows developers to quickly find a specific trace without having to manually navigate to a second user-interface.
* Prettify all the thingsMike Greiling2018-11-201-38/+11
|
* Show if the host is a canary host in the perf barSean McGivern2018-10-121-1/+14
| | | | | | | | If the request came from a canary host, show this in the performance bar by: 1. Adding a bird emoji. 2. Colouring the hostname yellow.
* Fixes performance bar looking for a key in a undefined propFilipa Lacerda2018-09-271-1/+1
|