ui telemetry for all events

[pjain1]

Checklist:

• Covered by tests
• Ran it and it works as intended
• Reviewed the diff before requesting a review
• Checked for unhandled edge cases
• Linked the issues it closes
• Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
• Intend to cherry-pick into the release branch
• I'm proud of this work!

[AdityaHegde]

Since we are guarding against path not search params in layout, time range, filters etc might not get logged.

If we want url params then we need to remove the guard from layout around url path. But this will lead to explosion of events since url changes quite often, we could optimize debouncing by say 1sec, but might still be too much.

If we only want explore/canvas names then how about emitting just that? org, project_id, resourceName, resourceType might give full picture.

[pjain1]

I am not concerned about event volume, I think we can handle it. At some point it would be good to have info for at least most used time ranges, dimensions and measures but semantics is the issue here loading a dimension on dashboard may not mean it is being used, if its filtered on, expanded, sorted by etc. then it may counted as used and I think we may need it for canvas as well not just explore.

So may be we start simple for now with just resource name and type and then later add these things.