chore: remove old dashboard leftovers (#19545)
Ilya Mashchenko committed
Jan 31, 2025 at 15:19 UTC
0164a51a8645bdb0bf923aad350c86759c3b2f10
9 files changed
+1
-78
.codacy.yml
-7
@@ -4,13 +4,6 @@ exclude_paths:
4
- src/collectors/python.d.plugin/python_modules/urllib3/**
5
- src/collectors/python.d.plugin/python_modules/third_party/**
6
- packaging/makeself/**
7
- - src/web/gui/css/**
8
- - src/web/gui/lib/**
9
- - src/web/gui/old/**
10
- - src/web/gui/src/**
11
- - src/web/gui/v1/**
12
- - src/web/gui/v2/**
13
- - src/web/gui/main.js
7
- tests/**
8
- aclk/tests/**
9
- src/libnetdata/libjudy/**
.github/workflows/dashboard-pr.yml
deleted
-54
@@ -1,54 +0,0 @@
1
----
2
-# Create a PR to update the react dashboard code.
3
-name: Dashboard Version PR
4
-
5
-on:
6
- workflow_dispatch:
7
- inputs:
8
- dashboard_version:
9
- # This must be specified, and must _exactly_ match the version
10
- # tag for the release to be used for the update.
11
- description: Dashboard Version
12
- required: true
13
-
14
-env:
15
- DISABLE_TELEMETRY: 1
16
-
17
-jobs:
18
- dashboard-pr:
19
- name: Generate Dashboard Version Bump PR
20
- runs-on: ubuntu-latest
21
- steps:
22
- - name: Checkout
23
- id: checkout
24
- uses: actions/checkout@v4
25
- - name: Update Files
26
- id: update
27
- run: |
28
- src/web/gui/bundle_dashboard_v1.py ${{ github.event.inputs.dashboard_version }}
29
- - name: Create Pull Request
30
- id: pr
31
- uses: peter-evans/create-pull-request@v7
32
- with:
33
- title: 'Update dashboard to version ${{ github.event.inputs.dashboard_version }}.'
34
- body: 'See https://github.com/netdata/dashboard/releases/tag/${{ github.event.inputs.dashboard_version }} for changes.'
35
- branch: dashboard-${{ github.event.inputs.dashboard_version }}
36
- branch-suffix: timestamp
37
- delete-branch: true
38
- commit-message: 'Update dashboard to version ${{ github.event.inputs.dashboard_version }}.'
39
- token: ${{ secrets.NETDATABOT_GITHUB_TOKEN }}
40
- - name: Failure Notification
41
- uses: rtCamp/action-slack-notify@v2
42
- env:
43
- SLACK_COLOR: 'danger'
44
- SLACK_FOOTER: ''
45
- SLACK_ICON_EMOJI: ':github-actions:'
46
- SLACK_TITLE: 'Dashboard update PR creation failed:'
47
- SLACK_USERNAME: 'GitHub Actions'
48
- SLACK_MESSAGE: |-
49
- ${{ github.repository }}: Failed to create PR to update dashboard code to newest release.
50
- Checkout: ${{ steps.checkout.outcome }}
51
- Update files: ${{ steps.update.outcome }}
52
- Create PR: ${{ steps.pr.outcome }}
53
- SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK_URL }}
54
- if: failure()
.gitignore
-8
@@ -60,14 +60,6 @@ README
60
TODO.md
61
TODO.txt
62
63
-src/web/gui/chart-info/
64
-src/web/gui/control.html
65
-src/web/gui/dashboard.js
66
-src/web/gui/datasource.css
67
-src/web/gui/gadget.xml
68
-src/web/gui/index_new.html
69
-src/web/gui/version.txt
70
-
63
# related to karma/javascript/node
64
/node_modules/
65
/coverage/
README.md
+1
-1
@@ -803,6 +803,6 @@ The Netdata ecosystem consists of three key parts:
803
804
- **Netdata Cloud**: A commercial, closed-source component, Netdata Cloud enhances the capabilities of the open-source Netdata Agent by providing horizontal scalability, centralized alert notification dispatch (including a mobile app), user management, role-based access control, and other enterprise-grade features. It is available both as a SaaS solution and for on-premises deployment, with a free-to-use community tier also offered.
805
806
-- **Netdata UI**: The Netdata UI is closed-source, and handles all visualization and dashboard functionalities related to metrics, logs and other collected data, as well as the central configuration and management of the Netdata ecosystem. It serves both the Netdata Agent and Netdata Cloud. The Netdata UI is distributed in binary form with the Netdata Agent and is publicly accessible via a CDN, licensed under the [Netdata Cloud UI License 1 (NCUL1)](https://app.netdata.cloud/LICENSE.txt). It integrates third-party open-source components, detailed in the [Netdata UI third-party licenses](https://github.com/netdata/netdata/blob/master/src/web/gui/v2/3D_PARTY_LICENSES.txt).
806
+- **Netdata UI**: The Netdata UI is closed-source, and handles all visualization and dashboard functionalities related to metrics, logs and other collected data, as well as the central configuration and management of the Netdata ecosystem. It serves both the Netdata Agent and Netdata Cloud. The Netdata UI is distributed in binary form with the Netdata Agent and is publicly accessible via a CDN, licensed under the [Netdata Cloud UI License 1 (NCUL1)](https://app.netdata.cloud/LICENSE.txt). It integrates third-party open-source components, detailed in the [Netdata UI third-party licenses](https://app.netdata.cloud/3D_PARTY_LICENSES.txt).
807
808
The binary installation packages provided by Netdata include the Netdata Agent and the Netdata UI. Since the Netdata Agent is open-source, it is frequently packaged by third parties (e.g., Linux Distributions) excluding the closed-source components (Netdata UI is not included). While their packages can still be useful in providing the necessary back-ends and the APIs of a fully functional monitoring solution, we recommend using the installation packages we provide to experience the full feature set of Netdata.
docs/dashboards-and-charts/README.md
-2
@@ -36,5 +36,3 @@ You can access the dashboard at <https://app.netdata.cloud/> and [sign-in with a
36
### Netdata Agent
37
38
To view your Netdata dashboard, open a web browser and enter the address `http://NODE:19999` - replace `NODE` with your Agent's IP address or hostname. If the Agent is on the same machine, use `http://localhost:19999`.
39
-
40
-Documentation for the previous Agent dashboard can still be found [here](/src/web/gui/README.md).
docs/developer-and-contributor-corner/python-collector.txt
-1
@@ -542,7 +542,6 @@ At minimum, to be buildable and testable, the PR needs to include:
542
- A basic configuration for the plugin in the appropriate global config file: `collectors/python.d.plugin/python.d.conf`, which is also in YAML format. Either add a line that reads `# <module_name>: yes` if the module is to be enabled by default, or one that reads `<module_name>: no` if it is to be disabled by default.
543
- A makefile for the plugin at `collectors/python.d.plugin/<module_dir>/Makefile.inc`. Check an existing plugin for what this should look like.
544
- A line in `collectors/python.d.plugin/Makefile.am` including the above-mentioned makefile. Place it with the other plugin includes (please keep the includes sorted alphabetically).
545
-- Optionally, chart information in `src/web/gui/dashboard_info.js`. This generally involves specifying a name and icon for the section, and may include descriptions for the section or individual charts.
545
- Optionally, some default alert configurations for your collector in `health/health.d/<module_name>.conf` and a line adding `<module_name>.conf` in `health/Makefile.am`.
546
547
## Framework class reference
docs/glossary.md
-2
@@ -35,8 +35,6 @@ Missing a term? Let us know or submit a request to expand our glossary. Together
35
36
- [**Context**](/docs/dashboards-and-charts/netdata-charts.md#contexts): A way of grouping charts by the types of metrics collected and dimensions displayed. It's kind of like a machine-readable naming and organization scheme.
37
38
-- [**Custom dashboards**](/src/web/gui/custom/README.md) A dashboard that you can create using simple HTML (no JavaScript is required for basic dashboards).
39
-
38
## D
39
40
- [**Dashboard**](/docs/dashboards-and-charts/README.md): Out-of-the-box visual representation of metrics to provide insight into your infrastructure, its health and performance.
src/collectors/statsd.plugin/README.md
-2
@@ -972,8 +972,6 @@ At this point, you have used StatsD to gather metrics for k6, creating a whole n
972
Netdata dashboard in the process. Moreover, you can further customize the icon of the particular section,
973
as well as the description for each chart.
974
975
-To edit the section, please follow the Netdata [documentation](/src/web/gui/README.md#customizing-the-local-dashboard).
976
-
975
While the following configuration will be placed in a new file, as the documentation suggests, it is
976
instructing to use `dashboard_info.js` as a template. Open the file and see how the rest of sections and collectors have been defined.
977
src/health/notifications/alarm-notify.sh.in
-1
@@ -2490,7 +2490,6 @@ send_ntfy() {
2490
msg="${host} ${status_message}: ${alarm} - ${info}"
2491
httpcode=$(docurl -X POST \
2492
"${ntfy_auth_header[@]}" \
2493
- -H "Icon: https://raw.githubusercontent.com/netdata/netdata/master/src/web/gui/dashboard/images/favicon-196x196.png" \
2493
-H "Title: ${host}: ${name//_/ }" \
2494
-H "Tags: ${emoji}" \
2495
-H "Priority: ${priority}" \