You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "ntheanh201 (via GitHub)" <gi...@apache.org> on 2024/01/24 14:20:09 UTC
[PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
ntheanh201 opened a new pull request, #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927
<!--
Thank you for contributing! Please be sure to read our contribution guidelines: https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md
If this closes or relates to an existing issue, please reference it using one of the following:
Closes: #ISSUE
Related: #ISSUE
If this PR fixes a security vulnerability, DO NOT submit! Instead, contact
the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
guidelines at https://apache.org/security regarding vulnerability disclosure.
-->
1. Upgrade to Grafana v10.2.3
2. Migrate Scripted Dashboards to Grafana Scenes
- I've transitioned our existing scripted dashboards to the new Grafana Scenes. The migration also ensures compatibility with future Grafana updates and aligns with Grafana's recommended best practices. Check it here: [New in Grafana 10: Grafana Scenes for building dynamic dashboarding experiences
](https://grafana.com/blog/2023/08/03/new-in-grafana-10-grafana-scenes-for-building-dynamic-dashboarding-experiences/)
<!-- **^ Add meaningful description above** --><hr/>
## Which Traffic Control components are affected by this PR?
- CDN in a Box
## What is the best way to verify this PR?
<!-- Please include here ALL the steps necessary to test your PR.
If your PR has tests (and most should), provide the steps needed to run the tests.
If not, please provide step-by-step instructions to test the PR manually and explain why your PR does not need tests. -->
- Run CDN in a Box with Grafana
- Go to Grafana, go to Apps -> TrafficControl Grafana Scenes
- See the dashboards
Check the images below
## If this is a bugfix, which Traffic Control versions contained the bug?
<!-- Delete this section if the PR is not a bugfix, or if the bug is only in the master branch.
Examples:
- 5.1.2
- 5.1.3 (RC1)
-->
## PR submission checklist
- [x] This PR has tests <!-- If not, please delete this text and explain why this PR does not need tests. -->
- [x] This PR has documentation <!-- If not, please delete this text and explain why this PR does not need documentation. -->
- [x] This PR has a CHANGELOG.md entry <!-- A fix for a bug from an ATC release, an improvement, or a new feature should have a changelog entry. -->
- [x] This PR **DOES NOT FIX A SERIOUS SECURITY VULNERABILITY** (see [the Apache Software Foundation's security guidelines](https://apache.org/security) for details)
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1469133484
##########
docs/source/admin/traffic_stats.rst:
##########
@@ -91,35 +91,9 @@ To easily create databases, retention policies, and continuous queries, run :pro
Configuring Grafana
-------------------
-In Traffic Portal the :menuselection:`Other --> Grafana` menu item can be configured to display Grafana graphs using InfluxDB data (when not configured, this menu item will not appear). In order for this to work correctly, you will need two things:
-
-#. A :term:`Parameter` with the graph URL (more information below)
-#. The graphs created in Grafana. See below for how to create some simple graphs in Grafana. These instructions assume that InfluxDB has been configured and that data has been written to it. If this is not true, you will not see any graphs.
-
-To create a graph in Grafana, you can follow these basic steps:
-
-#. Login to Grafana as an administrative user
-#. Click on :menuselection:`Data Sources --> Add New`
-#. Enter the necessary information to configure your data source
-#. Click on :menuselection:`Home --> New` at the bottom
-#. Click on :menuselection:`"Collapsed Menu Icon" Button --> Add Panel --> Graph`
-#. Where it says :guilabel:`No Title (click here)` click and choose edit
-#. Choose your data source at the bottom
-#. You can have Grafana help you create a query, or you can create your own.
-
- .. code-block:: postgresql
- :caption: Sample Query
-
- SELECT sum(value)*1000 FROM "monthly"."bandwidth.cdn.1min" GROUP BY time(60s), cdn;
-
-#. Once you have the graph the way you want it, click the :guilabel:`Save Dashboard` button at the top
-#. You should now have a new saved graph
-
-In order for Traffic Portal users to see Grafana graphs, Grafana will need to allow anonymous access. Information on how to configure anonymous access can be found on the configuration page of the `Grafana Website <http://docs.grafana.org/installation/configuration/#authanonymous>`_.
-
-Traffic Portal uses custom dashboards to display information about individual :term:`Delivery Services` or :term:`Cache Groups`. In order for the custom graphs to display correctly, the Javascript files in :atc-file:`traffic_stats/grafana/` need to be in the :file:`/usr/share/grafana/public/dashboards/` directory on the Grafana server. If your Grafana server is the same as your Traffic Stats server the RPM install process will take care of putting the files in place. If your Grafana server is different from your Traffic Stats server, you will need to manually copy the files to the correct directory.
-
-.. seealso:: More information on custom scripted graphs can be found in the `scripted dashboards <http://docs.grafana.org/reference/scripting/>`_ section of the Grafana documentation.
+- Traffic Control using Scenes for building dynamic Grafana dashboards, the Scenes app is built under: :file:`/var/lib/grafana/plugins/trafficcontrol-scenes-app`
+- To see Traffic Control dashboards, go to: :file:`https://grafanaHost/a/trafficcontrol-scenes-app`
+.. seealso:: More information on Grafana Scenes can be found in `Grafana Scenes introduction <https://grafana.com/blog/2023/08/03/new-in-grafana-10-grafana-scenes-for-building-dynamic-dashboarding-experiences/>`_
Review Comment:
Currently, I let the trafficcontrol-scenes into Grafana CiaB folder, it means this plugin will be built and run when running CiaB with Grafana.
But I'm thinking about let this plugin inside Traffic Stats, and will be built with Traffic Stats. Then the user can use the folder: if the server is the same with Grafana, Grafana can use this plugin to display dashboards. If the server is different, they can copy it.
What do you think? @ocket8888
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#issuecomment-1961313099
> This all looks fine on GitHub. I'll carve out some time tomorrow to try to spin it up and see how it actually works (#5939 permitting).
Did you finish with checking?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1480842630
##########
infrastructure/cdn-in-a-box/traffic_stats/Dockerfile:
##########
@@ -29,9 +29,13 @@ RUN if [[ "${RHEL_VERSION%%.*}" -eq 7 ]]; then \
yum -y install dnf || exit 1; \
fi
+RUN set -o pipefail && \
+ curl -sLf https://rpm.nodesource.com/setup_16.x | bash
Review Comment:
¯\\\_(ツ)\_/¯
I just looked at what GitHub showed me as a part of its notification. Thanks for letting me know, though, I'll take a closer look.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1506279362
##########
traffic_stats/build/build_rpm.sh:
##########
@@ -78,6 +78,19 @@ initBuildArea() {
go build -v -gcflags "$gcflags" -ldflags "$ldflags" create/create_ts_databases.go || \
{ echo "Could not build create_ts_databases binary"; return 1; })
+ # compile trafficcontrol-scenes
+ echo "Installing grafana scenes npm dependencies"
+ (cd trafficcontrol-scenes
+ npm i || \
Review Comment:
my build fails on this line with
```
----- Building traffic_stats ...
/usr/bin/realpath
git is /usr/bin/git
go is /usr/bin/go
/tmp/go/src/github.com/apache/trafficcontrol/build/functions.sh: line 182: type: npm: not found
npm not found in PATH
Error on line 1 of traffic_stats/build/build_rpm.sh
traffic_stats failed: traffic_stats/build/build_rpm.sh
The following subdirectories had errors:
traffic_stats
Error on line 1 of ./build/build.sh
```
I rebuilt the builder to be sure. Command I used to test was `./pkg -v -L -S traffic_stats_build`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1480833942
##########
infrastructure/cdn-in-a-box/traffic_stats/Dockerfile:
##########
@@ -29,9 +29,13 @@ RUN if [[ "${RHEL_VERSION%%.*}" -eq 7 ]]; then \
yum -y install dnf || exit 1; \
fi
+RUN set -o pipefail && \
+ curl -sLf https://rpm.nodesource.com/setup_16.x | bash
Review Comment:
It looks like the RPM build for Traffic Stats will use Node v20, but CiaB will use Node v16. Shouldn't those versions match?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1477545372
##########
docs/source/admin/traffic_stats.rst:
##########
@@ -91,35 +91,9 @@ To easily create databases, retention policies, and continuous queries, run :pro
Configuring Grafana
-------------------
-In Traffic Portal the :menuselection:`Other --> Grafana` menu item can be configured to display Grafana graphs using InfluxDB data (when not configured, this menu item will not appear). In order for this to work correctly, you will need two things:
-
-#. A :term:`Parameter` with the graph URL (more information below)
-#. The graphs created in Grafana. See below for how to create some simple graphs in Grafana. These instructions assume that InfluxDB has been configured and that data has been written to it. If this is not true, you will not see any graphs.
-
-To create a graph in Grafana, you can follow these basic steps:
-
-#. Login to Grafana as an administrative user
-#. Click on :menuselection:`Data Sources --> Add New`
-#. Enter the necessary information to configure your data source
-#. Click on :menuselection:`Home --> New` at the bottom
-#. Click on :menuselection:`"Collapsed Menu Icon" Button --> Add Panel --> Graph`
-#. Where it says :guilabel:`No Title (click here)` click and choose edit
-#. Choose your data source at the bottom
-#. You can have Grafana help you create a query, or you can create your own.
-
- .. code-block:: postgresql
- :caption: Sample Query
-
- SELECT sum(value)*1000 FROM "monthly"."bandwidth.cdn.1min" GROUP BY time(60s), cdn;
-
-#. Once you have the graph the way you want it, click the :guilabel:`Save Dashboard` button at the top
-#. You should now have a new saved graph
-
-In order for Traffic Portal users to see Grafana graphs, Grafana will need to allow anonymous access. Information on how to configure anonymous access can be found on the configuration page of the `Grafana Website <http://docs.grafana.org/installation/configuration/#authanonymous>`_.
-
-Traffic Portal uses custom dashboards to display information about individual :term:`Delivery Services` or :term:`Cache Groups`. In order for the custom graphs to display correctly, the Javascript files in :atc-file:`traffic_stats/grafana/` need to be in the :file:`/usr/share/grafana/public/dashboards/` directory on the Grafana server. If your Grafana server is the same as your Traffic Stats server the RPM install process will take care of putting the files in place. If your Grafana server is different from your Traffic Stats server, you will need to manually copy the files to the correct directory.
-
-.. seealso:: More information on custom scripted graphs can be found in the `scripted dashboards <http://docs.grafana.org/reference/scripting/>`_ section of the Grafana documentation.
+- Traffic Control using Scenes for building dynamic Grafana dashboards, the Scenes app is built under: :file:`/var/lib/grafana/plugins/trafficcontrol-scenes-app`
+- To see Traffic Control dashboards, go to: :file:`https://grafanaHost/a/trafficcontrol-scenes-app`
+.. seealso:: More information on Grafana Scenes can be found in `Grafana Scenes introduction <https://grafana.com/blog/2023/08/03/new-in-grafana-10-grafana-scenes-for-building-dynamic-dashboarding-experiences/>`_
Review Comment:
I updated the code and the docs to avoid confusion, the workflow stays the same, Traffic Control Grafana Scenes is built along with Traffic Stats. The only difference is that now people can visit: https://grafanaHost/a/trafficcontrol-scenes-app to view the dashboards
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1466747512
##########
infrastructure/cdn-in-a-box/optional/grafana/app.yaml.template:
##########
@@ -0,0 +1,30 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied. See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+# Refer to "http://docs.grafana.org/administration/provisioning/#example-datasource-config-file"
+# for the variables usages
+
+apiVersion: 1
+
+apps:
+ - type: 'trafficcontrol-scenes-app'
+ org_id: 1
+ org_name: 'apache'
+ disabled: false
+ jsonData:
+ apiUrl: https://trafficcontrol.apache.org/
+ isApiKeySet: true
Review Comment:
missing newline at EOF
##########
infrastructure/cdn-in-a-box/optional/grafana/datasources.yml.template:
##########
@@ -51,3 +51,14 @@ datasources:
database: deliveryservice_stats
basicAuth: false
isDefault: false
+
+- name: telegraf
+ type: influxdb
+ access: proxy
+ orgId: 1
+ url: http://$INFLUXDB_HOST:$INFLUXDB_PORT
+ password: $INFLUXDB_ADMIN_PASSWORD
+ user: $INFLUXDB_ADMIN_USER
+ database: telegraf
+ basicAuth: false
+ isDefault: false
Review Comment:
missing newlline at EOF
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/.eslintrc:
##########
@@ -0,0 +1,39 @@
+/*
+* Licensed under the Apache License, Version 2.0 (the "License");
+* you may not use this file except in compliance with the License.
+* You may obtain a copy of the License at
+*
+* http://www.apache.org/licenses/LICENSE-2.0
+*
+* Unless required by applicable law or agreed to in writing, software
+* distributed under the License is distributed on an "AS IS" BASIS,
+* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+* See the License for the specific language governing permissions and
+* limitations under the License.
+*/
+
+/*
+ * ⚠️⚠️⚠️ THIS FILE WAS SCAFFOLDED BY `@grafana/create-plugin`. DO NOT EDIT THIS FILE DIRECTLY. ⚠️⚠️⚠️
+ *
+ * In order to extend the configuration follow the steps in
+ * https://grafana.com/developers/plugin-tools/create-a-plugin/extend-a-plugin/extend-configurations#extend-the-eslint-config
+ */
+{
+ "extends": ["@grafana/eslint-config"],
Review Comment:
We really need a master ruleset at the root that each project extends from. Right now I just keep asking people to try to stick to the rules in the TPv2 project directory, which is understandably confusing and annoying. You don't have to do that now (at least partially because you'd have to know what subset of those rules to use as the base) but ideally the rules here would line up at least a little with the others - e.g. indentation and quote style, since they're the most pervasive.
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/CHANGELOG.md:
##########
@@ -0,0 +1,5 @@
+# Changelog
+
+## 1.0.0 (Unreleased)
+
+Initial release.
Review Comment:
I don't think we need this file, do we? Surely anything you'd put in here could just go in the project's CHANGELOG? Which probably wouldn't be much.
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/.gitignore:
##########
@@ -0,0 +1,20 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied. See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+
+node_modules
+dist
Review Comment:
missing newline at EOF
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/LICENSE:
##########
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "{}"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright {yyyy} {name of copyright owner}
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
Review Comment:
Do we need another copy of the license?
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/.prettierrc.js:
##########
@@ -0,0 +1,30 @@
+/*
+* Licensed under the Apache License, Version 2.0 (the "License");
+* you may not use this file except in compliance with the License.
+* You may obtain a copy of the License at
+*
+* http://www.apache.org/licenses/LICENSE-2.0
+*
+* Unless required by applicable law or agreed to in writing, software
+* distributed under the License is distributed on an "AS IS" BASIS,
+* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+* See the License for the specific language governing permissions and
+* limitations under the License.
+*/
+
+/*
+ * ⚠️⚠️⚠️ THIS FILE WAS SCAFFOLDED BY `@grafana/create-plugin`. DO NOT EDIT THIS FILE DIRECTLY. ⚠️⚠️⚠️
+ *
+ * In order to extend the configuration follow the steps in .config/README.md
+ */
+
+module.exports = {
+ endOfLine: 'auto',
+ printWidth: 120,
+ trailingComma: 'es5',
+ semi: true,
+ jsxSingleQuote: false,
+ singleQuote: true,
+ useTabs: false,
+ tabWidth: 2,
Review Comment:
We should avoid specifying conflicting specs for these settings; per `.editorconfig` and `.eslintrc.json` in the TPv2 directory (which is experimental but adhered to by other JS source files e.g. GHA action source files) indentation should use 1 tab character and quotes should be double.
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/src/img/logo.svg:
##########
Review Comment:
Is there any way to reuse the logo from its original source location under `misc/logos/`? I ran into issues with webpack not following symlinks in TPv2, which is why that has a copy (although it's been like 10 major revisions of the Angular framework since then, so maybe that should also be revisited), but ideally that would be avoided.
##########
docs/source/admin/traffic_stats.rst:
##########
@@ -91,35 +91,9 @@ To easily create databases, retention policies, and continuous queries, run :pro
Configuring Grafana
-------------------
-In Traffic Portal the :menuselection:`Other --> Grafana` menu item can be configured to display Grafana graphs using InfluxDB data (when not configured, this menu item will not appear). In order for this to work correctly, you will need two things:
-
-#. A :term:`Parameter` with the graph URL (more information below)
-#. The graphs created in Grafana. See below for how to create some simple graphs in Grafana. These instructions assume that InfluxDB has been configured and that data has been written to it. If this is not true, you will not see any graphs.
-
-To create a graph in Grafana, you can follow these basic steps:
-
-#. Login to Grafana as an administrative user
-#. Click on :menuselection:`Data Sources --> Add New`
-#. Enter the necessary information to configure your data source
-#. Click on :menuselection:`Home --> New` at the bottom
-#. Click on :menuselection:`"Collapsed Menu Icon" Button --> Add Panel --> Graph`
-#. Where it says :guilabel:`No Title (click here)` click and choose edit
-#. Choose your data source at the bottom
-#. You can have Grafana help you create a query, or you can create your own.
-
- .. code-block:: postgresql
- :caption: Sample Query
-
- SELECT sum(value)*1000 FROM "monthly"."bandwidth.cdn.1min" GROUP BY time(60s), cdn;
-
-#. Once you have the graph the way you want it, click the :guilabel:`Save Dashboard` button at the top
-#. You should now have a new saved graph
-
-In order for Traffic Portal users to see Grafana graphs, Grafana will need to allow anonymous access. Information on how to configure anonymous access can be found on the configuration page of the `Grafana Website <http://docs.grafana.org/installation/configuration/#authanonymous>`_.
-
-Traffic Portal uses custom dashboards to display information about individual :term:`Delivery Services` or :term:`Cache Groups`. In order for the custom graphs to display correctly, the Javascript files in :atc-file:`traffic_stats/grafana/` need to be in the :file:`/usr/share/grafana/public/dashboards/` directory on the Grafana server. If your Grafana server is the same as your Traffic Stats server the RPM install process will take care of putting the files in place. If your Grafana server is different from your Traffic Stats server, you will need to manually copy the files to the correct directory.
-
-.. seealso:: More information on custom scripted graphs can be found in the `scripted dashboards <http://docs.grafana.org/reference/scripting/>`_ section of the Grafana documentation.
+- Traffic Control using Scenes for building dynamic Grafana dashboards, the Scenes app is built under: :file:`/var/lib/grafana/plugins/trafficcontrol-scenes-app`
+- To see Traffic Control dashboards, go to: :file:`https://grafanaHost/a/trafficcontrol-scenes-app`
+.. seealso:: More information on Grafana Scenes can be found in `Grafana Scenes introduction <https://grafana.com/blog/2023/08/03/new-in-grafana-10-grafana-scenes-for-building-dynamic-dashboarding-experiences/>`_
Review Comment:
Grammar:
- Traffic Control us<del>ing</del><ins>es</ins> Scenes <del>for</del><ins>to</ins> build<del>ing</del> dynamic Grafana dashboards<del>,</del><ins>.</ins> <del>t</del><ins>T</ins>he Scenes app is built under<del>:</del> ...
- ... can be found in \`<ins>the </ins>Grafana Scenes introduction...
Also, regarding "the Scenes app is built under" - are you saying that in order to build the "Scene" I have to copy my source files into that directory? Or is it just supposed to be stored there on a Grafana host?
`https://grafanaHost/a/trafficcontrol-scenes-app` is not a `file`. Also, is that (relative) URL guaranteed to be the location of the Scene on whatever Grafana host and configuration I choose to use?
Should these two sentences really be separate unordered list items, or can it just be a single paragraph?
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/src/README.md:
##########
@@ -0,0 +1,70 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+<!-- This README file is going to be the one displayed on the Grafana.com website for your plugin. Uncomment and replace the content here before publishing.
Review Comment:
I think you should
> _"Uncomment and replace the content here..."_
because right now this README doesn't provide any useful information.
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/tsconfig.json:
##########
@@ -0,0 +1,20 @@
+{
+ "compilerOptions": {
+ "alwaysStrict": true,
+ "declaration": false,
+ "rootDir": "./src",
+ "baseUrl": "./src",
+ "typeRoots": ["./node_modules/@types"],
+ "resolveJsonModule": true
+ },
+ "ts-node": {
+ "compilerOptions": {
+ "module": "commonjs",
+ "target": "es5",
+ "esModuleInterop": true
+ },
+ "transpileOnly": true
+ },
+ "include": ["./src", "./types"],
+ "extends": "@grafana/tsconfig"
+}
Review Comment:
missing newline at EOF.
Also, this project should use strict typechecking
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1469676624
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/.eslintrc:
##########
@@ -0,0 +1,39 @@
+/*
+* Licensed under the Apache License, Version 2.0 (the "License");
+* you may not use this file except in compliance with the License.
+* You may obtain a copy of the License at
+*
+* http://www.apache.org/licenses/LICENSE-2.0
+*
+* Unless required by applicable law or agreed to in writing, software
+* distributed under the License is distributed on an "AS IS" BASIS,
+* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+* See the License for the specific language governing permissions and
+* limitations under the License.
+*/
+
+/*
+ * ⚠️⚠️⚠️ THIS FILE WAS SCAFFOLDED BY `@grafana/create-plugin`. DO NOT EDIT THIS FILE DIRECTLY. ⚠️⚠️⚠️
+ *
+ * In order to extend the configuration follow the steps in
+ * https://grafana.com/developers/plugin-tools/create-a-plugin/extend-a-plugin/extend-configurations#extend-the-eslint-config
+ */
+{
+ "extends": ["@grafana/eslint-config"],
Review Comment:
Understood. I copied the rules from TPv2 and only change a bit
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1480843850
##########
infrastructure/cdn-in-a-box/traffic_stats/Dockerfile:
##########
@@ -29,9 +29,13 @@ RUN if [[ "${RHEL_VERSION%%.*}" -eq 7 ]]; then \
yum -y install dnf || exit 1; \
fi
+RUN set -o pipefail && \
+ curl -sLf https://rpm.nodesource.com/setup_16.x | bash
Review Comment:
Yeah I don't see that anymore.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#issuecomment-1910565809
@jhg03a I also updated the Dockerfile of Grafana, I think you can give me some reviews
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1506296848
##########
traffic_stats/build/build_rpm.sh:
##########
@@ -78,6 +78,19 @@ initBuildArea() {
go build -v -gcflags "$gcflags" -ldflags "$ldflags" create/create_ts_databases.go || \
{ echo "Could not build create_ts_databases binary"; return 1; })
+ # compile trafficcontrol-scenes
+ echo "Installing grafana scenes npm dependencies"
+ (cd trafficcontrol-scenes
+ npm i || \
Review Comment:
It will install nodejs, so you will get npm for building Grafana Scenes in Traffic stats
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#issuecomment-1908229914
<img width="1512" alt="Screenshot 2024-01-24 at 15 13 06" src="https://github.com/apache/trafficcontrol/assets/29043139/cec09d6c-d913-426b-9ed8-7dce4a1d9d3b">
Server dashboard
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#issuecomment-1969416810
> Did you finish with checking?
Sorry, no, I got busy. And then... I forgot :sweat_smile:
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 merged PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#issuecomment-1908228706
<img width="1512" alt="Screenshot 2024-01-24 at 15 12 28" src="https://github.com/apache/trafficcontrol/assets/29043139/0572fd8b-23e6-4887-b415-7490d2154d37">
Cache Group dashboard
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1471607082
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/src/img/logo.svg:
##########
Review Comment:
Can you make this a symbolic link to `misc/logos/ATC-SVG.svg`? Or will that not work?
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/src/constants.ts:
##########
@@ -17,36 +17,36 @@
* under the License.
*/
-import pluginJson from './plugin.json';
+import pluginJson from "./plugin.json";
export const PLUGIN_BASE_URL = `/a/${pluginJson.id}`;
-export enum ROUTES {
- CacheGroup = 'cache-group',
- DeliveryService = 'delivery-service',
- Server = 'server',
-}
+export const ROUTES = {
Review Comment:
Feel free to use enums if you want
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/.eslintrc.json:
##########
@@ -238,7 +238,8 @@
"selector": "variable",
"format": [
"camelCase",
- "UPPER_CASE"
+ "UPPER_CASE",
+ "PascalCase"
Review Comment:
indentation here is 7 tab characters while on the preceding line it's 14 spaces (7 groups of 2 spaces, presumably). Indentation within a single file should be consistent (and ideally use one tab per indentation level).
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/src/utils/utils.plugin.ts:
##########
@@ -17,20 +17,14 @@
* under the License.
*/
-import React, { useContext } from 'react';
-import { AppRootProps } from '@grafana/data';
+import { AppRootProps } from "@grafana/data";
+import React from "react";
// This is used to be able to retrieve the root plugin props anywhere inside the app.
export const PluginPropsContext = React.createContext<AppRootProps | null>(null);
-export const usePluginProps = () => {
- const pluginProps = useContext(PluginPropsContext);
-
- return pluginProps;
-};
-
-export const usePluginMeta = () => {
- const pluginProps = usePluginProps();
-
- return pluginProps?.meta;
-};
+// export const usePluginProps = () => {
+// const pluginProps = useContext(PluginPropsContext);
+//
+// return pluginProps;
+// };
Review Comment:
Did you mean to comment this out? If it's not relevant, should it be removed?
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/webpack/webpack.config.ts:
##########
@@ -11,23 +11,18 @@
* See the License for the specific language governing permissions and
* limitations under the License.
*/
-/*
- * ⚠️⚠️⚠️ THIS FILE WAS SCAFFOLDED BY `@grafana/create-plugin`. DO NOT EDIT THIS FILE DIRECTLY. ⚠️⚠️⚠️
- *
- * In order to extend the configuration follow the steps in
- * https://grafana.com/developers/plugin-tools/create-a-plugin/extend-a-plugin/extend-configurations#extend-the-webpack-config
- */
+/* eslint-disable */
Review Comment:
You should probably disable a specific rule (with a comment explaining why) and not the entire linter.
##########
infrastructure/cdn-in-a-box/optional/grafana/trafficcontrol-scenes/src/components/App/App.tsx:
##########
@@ -17,17 +17,28 @@
* under the License.
*/
-import React from 'react';
-import { AppRootProps } from '@grafana/data';
-import { PluginPropsContext } from '../../utils/utils.plugin';
-import { Routes } from '../Routes';
+import { AppRootProps } from "@grafana/data";
+import React, { ReactElement } from "react";
+import { Routes } from "src/components/Routes";
+import { PluginPropsContext } from "src/utils/utils.plugin";
+
+/**
+ * Renders the component by providing the PluginPropsContext to its children.
+ *
+ * @returns {ReactElement} The rendered component.
Review Comment:
Classes don't need `@returns` annotations.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1506295232
##########
traffic_stats/build/build_rpm.sh:
##########
@@ -78,6 +78,19 @@ initBuildArea() {
go build -v -gcflags "$gcflags" -ldflags "$ldflags" create/create_ts_databases.go || \
{ echo "Could not build create_ts_databases binary"; return 1; })
+ # compile trafficcontrol-scenes
+ echo "Installing grafana scenes npm dependencies"
+ (cd trafficcontrol-scenes
+ npm i || \
Review Comment:
Because you need to rebuild the Docker image of Traffic stats, in the Dockerfile-traffic_stats I added:
`RUN curl -sL https://rpm.nodesource.com/setup_20.x | bash - && \
yum -y install nodejs`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1506290899
##########
traffic_stats/build/build_rpm.sh:
##########
@@ -78,6 +78,19 @@ initBuildArea() {
go build -v -gcflags "$gcflags" -ldflags "$ldflags" create/create_ts_databases.go || \
{ echo "Could not build create_ts_databases binary"; return 1; })
+ # compile trafficcontrol-scenes
+ echo "Installing grafana scenes npm dependencies"
+ (cd trafficcontrol-scenes
+ npm i || \
Review Comment:
when I build with `./pkg -v -L -S -b traffic_stats_build` it works though... I have no idea why
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1480841507
##########
infrastructure/cdn-in-a-box/traffic_stats/Dockerfile:
##########
@@ -29,9 +29,13 @@ RUN if [[ "${RHEL_VERSION%%.*}" -eq 7 ]]; then \
yum -y install dnf || exit 1; \
fi
+RUN set -o pipefail && \
+ curl -sLf https://rpm.nodesource.com/setup_16.x | bash
Review Comment:
> It looks like the RPM build for Traffic Stats will use Node v20, but CiaB will use Node v16. Shouldn't those versions match?
Actually, this is removed from the latest commits, did you check the latest commit?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1471620229
##########
docs/source/admin/traffic_stats.rst:
##########
@@ -91,35 +91,9 @@ To easily create databases, retention policies, and continuous queries, run :pro
Configuring Grafana
-------------------
-In Traffic Portal the :menuselection:`Other --> Grafana` menu item can be configured to display Grafana graphs using InfluxDB data (when not configured, this menu item will not appear). In order for this to work correctly, you will need two things:
-
-#. A :term:`Parameter` with the graph URL (more information below)
-#. The graphs created in Grafana. See below for how to create some simple graphs in Grafana. These instructions assume that InfluxDB has been configured and that data has been written to it. If this is not true, you will not see any graphs.
-
-To create a graph in Grafana, you can follow these basic steps:
-
-#. Login to Grafana as an administrative user
-#. Click on :menuselection:`Data Sources --> Add New`
-#. Enter the necessary information to configure your data source
-#. Click on :menuselection:`Home --> New` at the bottom
-#. Click on :menuselection:`"Collapsed Menu Icon" Button --> Add Panel --> Graph`
-#. Where it says :guilabel:`No Title (click here)` click and choose edit
-#. Choose your data source at the bottom
-#. You can have Grafana help you create a query, or you can create your own.
-
- .. code-block:: postgresql
- :caption: Sample Query
-
- SELECT sum(value)*1000 FROM "monthly"."bandwidth.cdn.1min" GROUP BY time(60s), cdn;
-
-#. Once you have the graph the way you want it, click the :guilabel:`Save Dashboard` button at the top
-#. You should now have a new saved graph
-
-In order for Traffic Portal users to see Grafana graphs, Grafana will need to allow anonymous access. Information on how to configure anonymous access can be found on the configuration page of the `Grafana Website <http://docs.grafana.org/installation/configuration/#authanonymous>`_.
-
-Traffic Portal uses custom dashboards to display information about individual :term:`Delivery Services` or :term:`Cache Groups`. In order for the custom graphs to display correctly, the Javascript files in :atc-file:`traffic_stats/grafana/` need to be in the :file:`/usr/share/grafana/public/dashboards/` directory on the Grafana server. If your Grafana server is the same as your Traffic Stats server the RPM install process will take care of putting the files in place. If your Grafana server is different from your Traffic Stats server, you will need to manually copy the files to the correct directory.
-
-.. seealso:: More information on custom scripted graphs can be found in the `scripted dashboards <http://docs.grafana.org/reference/scripting/>`_ section of the Grafana documentation.
+- Traffic Control using Scenes for building dynamic Grafana dashboards, the Scenes app is built under: :file:`/var/lib/grafana/plugins/trafficcontrol-scenes-app`
+- To see Traffic Control dashboards, go to: :file:`https://grafanaHost/a/trafficcontrol-scenes-app`
+.. seealso:: More information on Grafana Scenes can be found in `Grafana Scenes introduction <https://grafana.com/blog/2023/08/03/new-in-grafana-10-grafana-scenes-for-building-dynamic-dashboarding-experiences/>`_
Review Comment:
I don't really know anything about Grafana, but all of our dashboards (is that even the right term?) currently live under `traffic_stats/grafana`, so that would seem a sensible place to put it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1506296907
##########
traffic_stats/build/build_rpm.sh:
##########
@@ -78,6 +78,19 @@ initBuildArea() {
go build -v -gcflags "$gcflags" -ldflags "$ldflags" create/create_ts_databases.go || \
{ echo "Could not build create_ts_databases binary"; return 1; })
+ # compile trafficcontrol-scenes
+ echo "Installing grafana scenes npm dependencies"
+ (cd trafficcontrol-scenes
+ npm i || \
Review Comment:
I think the problem is that Docker won't accept that the current traffic stats builder image is newer than the one it can pull. So it's using the older one. I wonder if you were to rebase this on master if it would still have that problem?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ocket8888 (via GitHub)" <gi...@apache.org>.
ocket8888 commented on code in PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#discussion_r1506300983
##########
traffic_stats/build/build_rpm.sh:
##########
@@ -78,6 +78,19 @@ initBuildArea() {
go build -v -gcflags "$gcflags" -ldflags "$ldflags" create/create_ts_databases.go || \
{ echo "Could not build create_ts_databases binary"; return 1; })
+ # compile trafficcontrol-scenes
+ echo "Installing grafana scenes npm dependencies"
+ (cd trafficcontrol-scenes
+ npm i || \
Review Comment:
Regardless, that's something I can test on my own, and I now have an RPM so I can proceed with testing.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Migrate dynamic scripted Grafana Dashboards to Scenes [trafficcontrol]
Posted by "ntheanh201 (via GitHub)" <gi...@apache.org>.
ntheanh201 commented on PR #7927:
URL: https://github.com/apache/trafficcontrol/pull/7927#issuecomment-1908229399
<img width="1512" alt="Screenshot 2024-01-24 at 15 12 42" src="https://github.com/apache/trafficcontrol/assets/29043139/00ae9c8f-34e1-401e-8eaa-1268c9614d24">
Delivery Service dashboard
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org