-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Production Endpoint for Product Telemetry #1563
Labels
area/telemetry
Issues related to collected telemetry data
refined
Requirements are refined and the issue is ready to be implemented.
size/small
Estimated to be completed within ~2 days
tests
Pull requests that update tests
Milestone
Comments
Closed
blocked by #1377 |
mpstefan
added
refined
Requirements are refined and the issue is ready to be implemented.
size/small
Estimated to be completed within ~2 days
labels
Feb 26, 2024
pleshakov
added a commit
to pleshakov/nginx-gateway-fabric
that referenced
this issue
Mar 13, 2024
Problem: Start sending product telemetry to the product F5 telemetry service. Solution: - Use the production telemetry endpoint in production NGF image, built using: - goreleaser - make commands from building the images doc - Introduce new targets in the Makefile for building prod images. Developer instructions for building NGF image remain unchanged, and such image will not send any telemetry, but will report it in the logs at the debug level. Testing: - Confirmed production NGF image built using make command sends telemetry. - Confirmed developer NGF image build using make command doesn't send any telemetry but reports it in the logs. CLOSES - nginxinc#1563
9 tasks
6 tasks
sjberman
pushed a commit
that referenced
this issue
Mar 15, 2024
Problem: Start sending product telemetry to the product F5 telemetry service. Solution: - Use the production telemetry endpoint in production NGF image, built using: - goreleaser - make commands from building the images doc - Introduce new targets in the Makefile for building prod images. Developer instructions for building NGF image remain unchanged, and such image will not send any telemetry, but will report it in the logs at the debug level. Testing: - Confirmed production NGF image built using make command sends telemetry. - Confirmed developer NGF image build using make command doesn't send any telemetry but reports it in the logs. CLOSES - #1563
Closed by #1699 |
github-project-automation
bot
moved this from 👀 In Review
to ✅ Done
in NGINX Gateway Fabric
Mar 15, 2024
amimimor
pushed a commit
to amimimor/nginx-gateway-fabric
that referenced
this issue
Apr 3, 2024
Problem: Start sending product telemetry to the product F5 telemetry service. Solution: - Use the production telemetry endpoint in production NGF image, built using: - goreleaser - make commands from building the images doc - Introduce new targets in the Makefile for building prod images. Developer instructions for building NGF image remain unchanged, and such image will not send any telemetry, but will report it in the logs at the debug level. Testing: - Confirmed production NGF image built using make command sends telemetry. - Confirmed developer NGF image build using make command doesn't send any telemetry but reports it in the logs. CLOSES - nginxinc#1563
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/telemetry
Issues related to collected telemetry data
refined
Requirements are refined and the issue is ready to be implemented.
size/small
Estimated to be completed within ~2 days
tests
Pull requests that update tests
As an NGF maintainer
I want to enable and test the production telemetry endpoint
So that I can collect and verify that data is exported properly
Acceptance
The text was updated successfully, but these errors were encountered: