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

[Telemetry] Add eventlog endpoint for collecting client-side events #501

Closed
wants to merge 52 commits into from

Conversation

kiendang
Copy link
Contributor

@kiendang kiendang commented May 3, 2021

for client telemetry events. originally from #364, moved to a separate PR here after discussion at jupyter-server/team-compass#4.

need to be in sync with #364 and cannot be merged before #364 is merged and jupyter/telemetry#62 is resolved.

yuvipanda and others added 30 commits May 19, 2020 14:42
Bump telemetry extension commit as well
Experiments here informed the schema naming
recommendations in jupyter/telemetry#11
python 3.5 is still supported
This lets us add detailed documentation & description
to our schemas, which is very hard to do in JSON.

We also add a lot of documentation to the one
JSON schema we have
Primary advantage over JSON is that we can do multi-line strings
for more detailed documentation. We also expect humans to read &
write these, so YAML is a much better format there. All JSON
is also valid YAML, so that helps.

Depends on jupyter/telemetry#13
for client event schema files
.suffix is not included in importlib.resources APIs and so might not always work
@codecov-commenter
Copy link

codecov-commenter commented May 3, 2021

Codecov Report

Merging #501 (e15dd9b) into master (678878f) will decrease coverage by 0.08%.
The diff coverage is 66.40%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #501      +/-   ##
==========================================
- Coverage   77.73%   77.64%   -0.09%     
==========================================
  Files         106      108       +2     
  Lines        9288     9412     +124     
  Branches     1001     1018      +17     
==========================================
+ Hits         7220     7308      +88     
- Misses       1710     1745      +35     
- Partials      358      359       +1     
Impacted Files Coverage Δ
jupyter_server/services/eventlog/handlers.py 32.00% <32.00%> (ø)
jupyter_server/utils.py 60.81% <57.77%> (-1.33%) ⬇️
jupyter_server/serverapp.py 67.12% <60.00%> (-0.12%) ⬇️
jupyter_server/base/handlers.py 64.74% <100.00%> (+1.04%) ⬆️
jupyter_server/pytest_plugin.py 92.14% <100.00%> (+0.43%) ⬆️
jupyter_server/services/contents/handlers.py 84.93% <100.00%> (+0.76%) ⬆️
jupyter_server/tests/test_eventlog.py 100.00% <100.00%> (ø)
... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 678878f...e15dd9b. Read the comment docs.

@Zsailer Zsailer changed the title Add eventlog endpoint Add telemetry endpoint for collecting client-side events May 3, 2021
@Zsailer Zsailer changed the title Add telemetry endpoint for collecting client-side events [Telemetry] Add telemetry endpoint for collecting client-side events May 3, 2021
@Zsailer Zsailer changed the title [Telemetry] Add telemetry endpoint for collecting client-side events [Telemetry] Add eventlog endpoint for collecting client-side events May 3, 2021
@Zsailer Zsailer added the Telemetry Discussion or issues related to Telemetry/Event-logging label Jun 14, 2021
@Zsailer
Copy link
Member

Zsailer commented Aug 29, 2022

This work has been superceded by #862. Closing here.

@Zsailer Zsailer closed this Aug 29, 2022
@kiendang kiendang deleted the telemetry_client branch August 29, 2022 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Telemetry Discussion or issues related to Telemetry/Event-logging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants