X-Git-Url: https://gerrit.fd.io/r/gitweb?p=csit.git;a=blobdiff_plain;f=docs%2Freport%2Ftrex_performance_tests%2Fthroughput_trending.rst;fp=docs%2Freport%2Ftrex_performance_tests%2Fthroughput_trending.rst;h=92adb1d0e1fb7dfbc532378d88e02c3b97f96d31;hp=9106cb4bdfac8ad88e75b6a731a86d950b785789;hb=c4275b598e6c333ecbbd45ad3742ab6cc6ba24b8;hpb=6034d72d01c76060e0f0804fd80e6b1308886cd3

diff --git a/docs/report/trex_performance_tests/throughput_trending.rst b/docs/report/trex_performance_tests/throughput_trending.rst
index 9106cb4bdf..92adb1d0e1 100644
--- a/docs/report/trex_performance_tests/throughput_trending.rst
+++ b/docs/report/trex_performance_tests/throughput_trending.rst
@@ -2,13 +2,4 @@ Throughput Trending
 -------------------
 
 CSIT provides continuous performance trending for master branch:
-
-#. `TRex Trending Graphs <https://s3-docs.fd.io/csit/master/trending/ndrpdr_trending/trex.html>`_:
-   per TRex test case throughput trend, trend compliance and summary of
-   detected anomalies. We expect TRex to hit the curently used bps or pps limit,
-   so no anomalies here (unless we change those limits in CSIT).
-
-#. `TRex Latency Graphs <https://s3-docs.fd.io/csit/master/trending/ndrpdr_latency_trending/trex.html>`_:
-   per TRex build NDRPDR latency measurements against the trendline.
-   We have seen in past that the latency numbers can depend on TRex version,
-   NIC firmware, or driver used.
+`C-Dash <http://csit.fd.io/trending/>`_