-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add the Ray integration #15441
Add the Ray integration #15441
Conversation
ec7b399
to
45d0ef9
Compare
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more. |
The |
1 similar comment
The |
721223f
to
3cfefce
Compare
ce5119f
to
fb1f75c
Compare
71fd9df
to
59decb6
Compare
5397704
to
c94210f
Compare
The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FlorentClarret This does not need Documentation review yet correct?
'ray_internal_num_infeasible_scheduling_classes': 'internal_num.infeasible_scheduling_classes', | ||
'ray_internal_num_processes_skipped_job_mismatch': 'internal_num.processes.skipped.job_mismatch', | ||
# There is a typo in their metric name, adding another entry to be ready as soon as they fix it | ||
'ray_internal_num_processes_skipped_runtime_enviornment_mismatch': 'internal_num.processes.skipped.runtime_environment_mismatch', # noqa: E501 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: is there a doc for these metrics? I know some are system metrics but not all. I was trying to find where the misspelled ray_internal_num_processes_skipped_runtime_enviornment_mismatch
is documented so we can check that doc in the future to know it has been fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://docs.ray.io/en/latest/ray-observability/reference/system-metrics.html#system-metrics
These metrics are all system metrics. "Application metrics" are manually added by the customer in their own code, so they would have to use the extras_metrics
option
This particular metric is not documented and this is why I added both versions so we are already ready when a patch will be out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They aren't all documented on that page though? I do not see ray_internal_num_infeasible_scheduling_classes
or ray_grpc_server_req_process_time_ms
for example, so I wasn't sure if there's a separate page for some of these metrics.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of the metrics are not documented. I had to take a look at the code to get them 😭
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah sad to hear 😢
@estherk15 Yes, I will open a PR dedicated to the documentation update to make it easier on our side if this sounds good to you. |
bd712ab
to
7fc36d6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ray/tests/docker/serve_tasks/__init__.py
needs a license header
🥇
ray/pyproject.toml
Outdated
[build-system] | ||
requires = [ | ||
"hatchling>=0.13.0", | ||
"setuptools>=66; python_version > '3.0'", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only required for editable installations on Python 2
"setuptools>=66; python_version > '3.0'", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it mean we can drop it from the templates? #15766
command: | ||
- /bin/bash | ||
- -c | ||
- | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ha nice I never thought to use multi-line strings to send to bash before
f11756b
to
7add4e1
Compare
76a2cb8
to
bdf9b76
Compare
bdf9b76
to
4cda273
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM again!
@FlorentClarret Not sure if you're aware, but it looks like the metrics metadata sync task is failing from this PR: see logs. |
What does this PR do?
Add the Ray integration
Motivation
2023Q3 OKR
Additional Notes
I will add the documentation and the assets in follow-up PRs to keep this PR as small as possible to focus on the implementation.
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attachedqa/skip-qa
label.