Skip to content
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

🐛 Bug: Disable Tooling Page analytics posting during dev mode to ensure accurate trend reports #1096

Open
DarhkVoyd opened this issue Nov 8, 2024 · 7 comments · May be fixed by #1134
Open
Assignees
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: Available No one has claimed responsibility for resolving this issue.

Comments

@DarhkVoyd
Copy link
Member

Describe the bug

Currently, analytics posting tooling page trends is active regardless of the environment (development or production), which can skew reports when development activity generates data that is irrelevant to real-world usage. To improve the accuracy of these reports, we should disable analytics tracking during development mode.

Steps To Reproduce

  1. Run the website in development mode.
  2. On /tools Tooling Page, trigger any event that would typically call the postAnalytics function, such as opening details modal for a tool or executing a search query for a tool.

Expected Behavior

  • During development, no analytics data should be posted to the endpoint.
  • During production, the analytics data should be posted as expected.

Screenshots

No response

Device Information [optional]

- OS:
- Browser:
- version:

Are you working on this issue?

No

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

@DarhkVoyd DarhkVoyd added 🐛 Bug Indicates that the issue is a bug or defect. Status: Triage This is the initial status for an issue that requires triage. labels Nov 8, 2024
@saurabhraghuvanshii
Copy link

saurabhraghuvanshii commented Nov 11, 2024

@DarhkVoyd can i Work on this if you assign to me

@saurabhraghuvanshii
Copy link

@DarhkVoyd can you assign me , I want to work on this

@DarhkVoyd
Copy link
Member Author

Hey @saurabhraghuvanshii, thanks for your interest. This issue is currently in the Status: Triage phase. Once it’s been discussed and approved to take on, it’ll be moved to the Status: Available phase and then you can work on it.

@saurabhraghuvanshii
Copy link

@DarhkVoyd thanks sir for informing

@benjagm
Copy link
Collaborator

benjagm commented Nov 23, 2024

Thanks @DarhkVoyd @saurabhraghuvanshii . This makes sense to me. Let's do it.

@benjagm benjagm added Status: Available No one has claimed responsibility for resolving this issue. and removed Status: Triage This is the initial status for an issue that requires triage. labels Nov 23, 2024
@saurabhraghuvanshii
Copy link

hii @benjagm @DarhkVoyd so, can I start working on it

@DarhkVoyd
Copy link
Member Author

Sure! @saurabhraghuvanshii please go ahead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: Available No one has claimed responsibility for resolving this issue.
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants