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
Ray integration docs #16594
Ray integration docs #16594
Conversation
Hi @RamanaReddy8801 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). If you add any more commits, you can comment |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
We created a ticket for this work for next sprint starting April 1st. |
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.
I added some suggestions! Feel free to take them or leave them🙂
- Ray integration | ||
- New Relic integrations | ||
metaDescription: Install our Ray dashboards and see your ray data in New Relic. | ||
freshnessValidatedDate: never |
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.
The date should be updated.
</Step> | ||
<Step> | ||
## Install the Prometheus integration | ||
1. Download the latest Prometheus release from the [Prometheus download page](https://prometheus.io/download/). Select the appropriate version for your operating system and architecture. For Linux, you'll likely choose the linux-amd64 version. Copy the download link for the tarball (`.tar.gz` file). |
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.
I'd add ``to linux-amd64, as follows linux-amd64
.
# Match the name of your cluster with the name seen in New Relic. | ||
targets: | ||
- description: Ray_Metrics | ||
urls: ["http://<YOUR_HOST_IP>:64747/metrics", "http://<YOUR_HOST_IP>:44217/metrics", "http://<YOUR_HOST_IP>:44227/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.
I think we shouldn't use <
or >
if we follow our style guide.
tags: | ||
- Ray integration | ||
- New Relic integrations | ||
metaDescription: Install our Ray dashboards and see your ray data in New Relic. |
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.
I'd write Ray instead of ray.
Ticket : https://issues.newrelic.com/browse/NR-249391
Description: Ray - created new integration documentation for Ray integration.
Preview image: