Closed colm-murphy-accenture closed 4 days ago
Howdy, can you share your steps to reproduce this? What Graylog image are you using? Is it Open or Enterprise? Can you share your (redacted) compose file? Are you using a path other than /
to access graylog?
For example: http://hostname:9000 vs http://hostname:9000/graylog
FWIW, we've not seen this in 6.1.0
, 6.1.1
, or 6.1.2
(Open and Enterprise) with GRAYLOG_TELEMETRY_ENABLED: "false"
.
Hi Drew, thanks for the fast response. We are using the Open Source version with a subpath /debug/graylog. This is compose section for the service
graylog:
image: graylog/graylog:6.1.2
labels:
service: "graylog"
extends:
file: common.yaml
service: common
container_name: "graylog"
environment:
- GRAYLOG_MONGODB_URI=mongodb://mongodb/graylog
- GRAYLOG_ELASTICSEARCH_HOSTS=http://opensearch:9200
- GRAYLOG_ROOT_USERNAME=${GRAYLOG_ROOT_USERNAME}
- GRAYLOG_ROOT_PASSWORD_SHA2=${GRAYLOG_ROOT_PASSWORD_SHA2}
- GRAYLOG_PASSWORD_SECRET=${GRAYLOG_PASSWORD_SECRET}
- GRAYLOG_TRUSTED_PROXIES=0.0.0.0/0
- GRAYLOG_TELEMETRY_ENABLED=false
tmpfs:
- /tmp
volumes:
- ./data/graylog/journal:/usr/share/graylog/data/journal
- ./data/graylog/plugins:/usr/share/graylog/plugins-merged
depends_on:
- mongodb
- opensearch
Using are using nginx as a reverse proxy and it is setting the subpath as follows
proxy_set_header X-Graylog-Server-URL $scheme://$http_host/debug/graylog/;
It seems that the issue might have already been found and fixed with #20909. I should have search closed as well as open tickets, sorry.
There still seems to a question however about how to globally disable telemetry for privacy reasons.
Hi @colm-murphy-accenture no worries. I was going to link that issue but glad you found it. This should be fixed in our next bug fix release which is on Wednesday, December 4.
There still seems to a question however about how to globally disable telemetry for privacy reasons.
What you have configured (GRAYLOG_TELEMETRY_ENABLED=false
) is correct.
@colm-murphy-accenture: The issue should be fixed in today's 6.1.3
release. It would be nice if you could test and close the issue if it has been fixed for you.
Can confirm - 6.1.3 seems to fix the problem.
@dennisoelkers: 6.1.3 fixes the issue. Thanks for the fast turnaround.
Expected Behavior
UI works as before
Current Behavior
Unexpected Application Error! Cannot read properties of null (reading 'at') TypeError: Cannot read properties of null (reading 'at') at n (https://dev-connect.scpmtk.com/debug/graylog/assets/app.43699a361c0b3855da5b.js:4886:55268) at https://dev-connect.scpmtk.com/debug/graylog/assets/app.43699a361c0b3855da5b.js:4886:55427 at https://dev-connect.scpmtk.com/debug/graylog/assets/app.43699a361c0b3855da5b.js:5266:2948 at Oa (https://dev-connect.scpmtk.com/debug/graylog/assets/vendor.437b8293e0632fce4768.js:692:25074) at Ts (https://dev-connect.scpmtk.com/debug/graylog/assets/vendor.437b8293e0632fce4768.js:692:43802) at z (https://dev-connect.scpmtk.com/debug/graylog/assets/vendor.437b8293e0632fce4768.js:692:37793) at Ar (https://dev-connect.scpmtk.com/debug/graylog/assets/vendor.437b8293e0632fce4768.js:690:3290) at ec (https://dev-connect.scpmtk.com/debug/graylog/assets/vendor.437b8293e0632fce4768.js:692:42596) at us (https://dev-connect.scpmtk.com/debug/graylog/assets/vendor.437b8293e0632fce4768.js:692:41562) at E (https://dev-connect.scpmtk.com/debug/graylog/assets/vendor.437b8293e0632fce4768.js:692:36565)
The browser console shows the following error
vendor.437b8293e0632fce4768.js:827 TypeError: Cannot read properties of null (reading 'at') at n (useSendTelemetry.tsx:33:47) at useSendTelemetry.tsx:43:19 at NavigationTelemetry.tsx:29:7 at Oa (vendor.437b8293e0632fce4768.js:692:25074) at Ts (vendor.437b8293e0632fce4768.js:692:43802) at z (vendor.437b8293e0632fce4768.js:692:37793) at Ar (vendor.437b8293e0632fce4768.js:690:3290) at ec (vendor.437b8293e0632fce4768.js:692:42596) at us (vendor.437b8293e0632fce4768.js:692:41562) at E (vendor.437b8293e0632fce4768.js:692:36565)
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
Telemetry is disabled using the GRAYLOG_TELEMETRY_ENABLED=false property in our docker compose