GitHub
01/07/2023, 8:19 AMGitHub
01/07/2023, 12:52 PMGitHub
01/07/2023, 3:28 PMGitHub
01/07/2023, 6:43 PMimage▾
GitHub
01/07/2023, 8:25 PMyarn
dependencies of this project.
Changes included in this PR
• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
• frontend/package.json
• frontend/yarn.lock
Vulnerabilities that will be fixed
With an upgrade:
(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.
* * *
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information: https://camo.githubusercontent.com/b2cdde6548b3770f34bce9823b7737ca71ba2e12c1d84b67abf173393e1dbeeb/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a684e7a64694f446b314e4330354d446b794c54517a4f4755744f5749314d5330774e574a6a4e5745345a544e684d6a6b694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d45334e3249344f5455304c546b774f5449744e444d345a533035596a55784c544131596d4d315954686c4d3245794f534a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)
SigNoz/signoz
GitHub Actions: playwright
GitHub Actions: lint-commits
GitHub Actions: Ensure Pull Request has a linked issue.
GitHub Actions: sonar-analysis
✅ 12 other checks have passed
12/16 successful checksGitHub
01/07/2023, 11:22 PMGitHub
01/08/2023, 6:40 AMGitHub
01/08/2023, 8:18 AMimage▾
GitHub
01/08/2023, 4:59 PM<https://github.com/SigNoz/signoz/tree/develop|develop>
by ankitnayan
<https://github.com/SigNoz/signoz/commit/b35bdf01ccb30484f1bd56c3e2fe9d201cbd45ed|b35bdf01>
- chore: 📌 pin versions: SigNoz 0.13.1
<https://github.com/SigNoz/signoz/commit/435d74c37e0f429979243e4cab84986de08d2691|435d74c3>
- Merge pull request #1996 from SigNoz/release/v0.13.1
SigNoz/signozGitHub
01/08/2023, 5:00 PMGitHub
01/08/2023, 5:42 PM<https://github.com/SigNoz/signoz/tree/develop|develop>
by ankitnayan
<https://github.com/SigNoz/signoz/commit/0c27d5acbc13339b4d1e1c0f4333647ee8a13595|0c27d5ac>
- chore: better error handling
<https://github.com/SigNoz/signoz/commit/215ea8d8199af6fe6aec7b7d8c8f8ebc8c6994fa|215ea8d8>
- chore: different ticker interval for active user
SigNoz/signozGitHub
01/08/2023, 5:43 PMGitHub
01/08/2023, 6:34 PMGitHub
01/08/2023, 6:37 PMGitHub
01/08/2023, 7:06 PM<https://github.com/SigNoz/charts/tree/main|main>
by ankitnayan
<https://github.com/SigNoz/charts/commit/0757895c00312a56218c89d8f0de7a7b9f6f6ed1|0757895c>
- fix duplicate metrics issue in OtelCollectors of SigNoz and K8s-Infra charts (#125)
SigNoz/chartsGitHub
01/08/2023, 7:06 PMGitHub
01/08/2023, 7:07 PMGitHub
01/09/2023, 7:56 AMimage▾
GitHub
01/09/2023, 8:02 AMrelabel_config
• introduce clusterName
configuration in both signoz and k8s-infra charts which is attached to telemetry data using resourcedection env
• introduce <http://apm.signoz.io/scrape|apm.signoz.io/scrape>
annotations for signoz apm spanmetrics
• use k8sattributes
processor in OtelCollector and resourcedetection
processor from missing pipelines
Note: After resource_to_telemetry_conversion
issue is resolved, we could include k8sattributes
, resourcedetection
or resource
processors in metrics pipeline.
SigNoz/chartsGitHub
01/09/2023, 11:59 AMimage▾
GitHub
01/09/2023, 12:11 PMGitHub
01/09/2023, 1:39 PMimage▾
image▾
GitHub
01/09/2023, 2:24 PMON
clause.
Earlier query built:
SELECT
A.service_name as service_name,
A.ts as ts,
A.value / (B.value + C.value) as value
FROM (
...
) as A JOIN (
...
) as B JOIN(
...
) as C USING (service, ts)
Correct query:
SELECT
A.service_name as service_name,
A.ts as ts,
A.value / (B.value + C.value) as value
FROM (
...
) as A JOIN (
...
) as B ON A.service_name = B.service_name AND A.ts = B.ts JOIN(
...
) as C ON B.service_name = C.service_name AND B.ts = C.ts
SigNoz/signoz
SonarCloud: Quality Gate failed
GitHub Actions: playwright
GitHub Actions: lint-commits
✅ 10 other checks have passed
10/13 successful checksGitHub
01/09/2023, 2:34 PMimage▾
image▾
GitHub
01/09/2023, 5:05 PMDynamic Volume Provisioning
enabled.
Hence I would like to ask if it's possible to support existingClaim
in queryService. persistence
and alertmanager.persistence
, similar to how it is possible for clickhouse.persistence
.
The use case for this is that if for some reason I want to redeploy SigNoz on my cluster, I want to control which persistent volumes each service will get.
Yesterday I was testing outage scenarios and came across the following situation:
1. Create 4 persistent volumes (pv1, pv2, pv3, pv4)
2. Deploy SigNoz
3. The query service persistent volume claim gets pv2
4. Register user
5. Remove SigNoz from the cluster
6. Deploy SigNoz again
7. The query service persistent volume claim gets pv3
8. The user registered in 4. is not found
SigNoz/chartsGitHub
01/09/2023, 5:51 PMGitHub
01/09/2023, 7:57 PMGitHub
01/09/2023, 7:57 PMGitHub
01/09/2023, 7:57 PMGitHub
01/09/2023, 8:48 PM/frontend
folder with the configuration added in this pull request:
❯ exportman --config exportman.json --onlyFiles
--- UNUSED FILES (26)
src/container/EditRules/styles.ts
src/container/FormAlertChannels/Settings/LabelFilter.tsx
src/container/ListOfDashboard/dashboardSearchAndFilter.ts
src/container/NewDashboard/DashboardSettings/General/Description/index.tsx
src/container/NewDashboard/DashboardSettings/General/Description/styles.ts
src/container/NewDashboard/DescriptionOfDashboard/NameOfTheDashboard/index.tsx
src/container/Trace/Filters/Panel/PanelBody/styles.ts
src/container/Trace/Filters/styles.ts
src/hooks/useMountedState.ts
src/lib/JSXtoHTML.ts
src/lib/convertIntoHr.ts
src/lib/getGlobalDropDownFormatedDate.ts
src/lib/getSettingsPeroid.ts
src/pages/CreateAlert/styles.ts
src/store/actions/logs/addToSelectedField.ts
src/store/actions/trace/selectTraceFilter.ts
src/store/actions/trace/updateTagsSelected.ts
src/types/api/alerts/queryType.ts
src/types/api/dashboard/shared.ts
src/types/api/logs/operator.ts
src/types/api/logs/removeSelectedField.ts
src/types/api/user/setUserPreference.ts
src/typings/environment.ts
src/typings/window.ts
src/utils/fixtures/TraceData.ts
src/utils/token.ts
The results seem pretty accurate, but I'm not 100% sure about each file separately. For instance, I see some styles.ts
files that are not imported anywhere, but they may be automatically included by a framework or build? If so, we can ignore such files and add them to the filePatterns
with !**/styles.ts
, and so on.
Running the tool without the --onlyFiles
flag will also report unused exports, unused types, and duplicate exports (didn't add them here for brevity).
I believe this tool can help significantly when maintaining (and refactoring) repositories like this.
Also see https://github.com/webpro/exportman if you're interested. Have a great day and best of luck with your project.
SigNoz/signoz
SonarCloud: Quality Gate failed
GitHub Actions: build-frontend
GitHub Actions: lint-commits
GitHub Actions: Ensure Pull Request has a linked issue.
GitHub Actions: Codeball
GitHub Actions: playwright
✅ 6 other checks have passed
6/12 successful checksGitHub
01/09/2023, 8:48 PM/frontend
folder with the configuration added in this pull request:
❯ exportman --config exportman.json --onlyFiles
--- UNUSED FILES (26)
src/container/EditRules/styles.ts
src/container/FormAlertChannels/Settings/LabelFilter.tsx
src/container/ListOfDashboard/dashboardSearchAndFilter.ts
src/container/NewDashboard/DashboardSettings/General/Description/index.tsx
src/container/NewDashboard/DashboardSettings/General/Description/styles.ts
src/container/NewDashboard/DescriptionOfDashboard/NameOfTheDashboard/index.tsx
src/container/Trace/Filters/Panel/PanelBody/styles.ts
src/container/Trace/Filters/styles.ts
src/hooks/useMountedState.ts
src/lib/JSXtoHTML.ts
src/lib/convertIntoHr.ts
src/lib/getGlobalDropDownFormatedDate.ts
src/lib/getSettingsPeroid.ts
src/pages/CreateAlert/styles.ts
src/store/actions/logs/addToSelectedField.ts
src/store/actions/trace/selectTraceFilter.ts
src/store/actions/trace/updateTagsSelected.ts
src/types/api/alerts/queryType.ts
src/types/api/dashboard/shared.ts
src/types/api/logs/operator.ts
src/types/api/logs/removeSelectedField.ts
src/types/api/user/setUserPreference.ts
src/typings/environment.ts
src/typings/window.ts
src/utils/fixtures/TraceData.ts
src/utils/token.ts
The results seem pretty accurate, but I'm not 100% sure about each file separately. For instance, I see some styles.ts
files that are not imported anywhere, but they may be automatically included by a framework or build? If so, we can ignore such files and add them to the filePatterns
with !**/styles.ts
, and so on.
Running the tool without the --onlyFiles
flag will also report unused exports, unused types, and duplicate exports (didn't add them here for brevity).
I believe this tool can help significantly when maintaining (and refactoring) repositories like this.
Also see https://github.com/webpro/exportman if you're interested. Have a great day and best of luck with your project.
SigNoz/signoz
SonarCloud: Quality Gate failed
GitHub Actions: build-frontend
GitHub Actions: lint-commits
GitHub Actions: Ensure Pull Request has a linked issue.
GitHub Actions: Codeball
GitHub Actions: playwright
✅ 6 other checks have passed
6/12 successful checks