hiro/ray
1
0
Fork 0
mirror of https://github.com/vale981/ray synced 2025-03-06 02:21:39 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

[Serve] [Doc] fix custom metric link in serve doc (#20775)

Browse source
This commit is contained in:
architkulkarni 2021-12-01 15:39:22 -08:00 • committed by GitHub
parent da57c99f47
commit 765e8d8d53
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/source/ray-metrics.rst
View file

@ -164,6 +164,8 @@ Now, modify a Prometheus config to scrape the file for service discovery.
Prometheus will automatically detect that the file contents are changing and update addresses it scrapes to based on the service discovery file generated by Ray.
.. _application-level-metrics:
Application-level Metrics
-------------------------
Ray provides a convenient API in :ref:`ray.util.metrics <custom-metric-api-ref>` for defining and exporting custom metrics for visibility into your applications.

2
doc/source/serve/deployment.rst
View file

@ -453,7 +453,7 @@ For example, after running the script for some time and refreshing ``localhost:8
which indicates that the average processing latency is just over one second, as expected.
You can even define a :ref:`custom metric <ray-metrics>` to use in your deployment, and tag it with the current deployment or replica.
You can even define a :ref:`custom metric <application-level-metrics>` to use in your deployment, and tag it with the current deployment or replica.
Here's an example:
.. literalinclude:: ../../../python/ray/serve/examples/doc/snippet_custom_metric.py