Depends on: torrust/torrust-tracker#1263
The Index is associates to one Torrust Tracker.
{
"tracker": {
"api_url": "http://localhost:1212/",
"listed": false,
"private": false,
"token": "***",
"token_valid_seconds": 7257600,
"url": "udp://localhost:6969"
}
}It imports the torrents stats from the Tracker's REST API:
https://tracker.torrust-demo.com/api/v1/stats?token=MyAccessToken
{
"torrents": 446911,
"seeders": 76978,
"completed": 639079,
"leechers": 130149,
"tcp4_connections_handled": 619,
"tcp4_announces_handled": 619,
"tcp4_scrapes_handled": 0,
"tcp6_connections_handled": 0,
"tcp6_announces_handled": 0,
"tcp6_scrapes_handled": 0,
"udp_requests_aborted": 5218855,
"udp_requests_banned": 276466475,
"udp_banned_ips_total": 21954,
"udp_avg_connect_processing_time_ns": 1184148,
"udp_avg_announce_processing_time_ns": 24523507,
"udp_avg_scrape_processing_time_ns": 662305,
"udp4_requests": 2738665346,
"udp4_connections_handled": 890528651,
"udp4_announces_handled": 1446412778,
"udp4_scrapes_handled": 37958014,
"udp4_responses": 2462193944,
"udp4_errors_handled": 86755758,
"udp6_requests": 0,
"udp6_connections_handled": 0,
"udp6_announces_handled": 0,
"udp6_scrapes_handled": 0,
"udp6_responses": 0,
"udp6_errors_handled": 0
}I'm working on a big stats refactor and I've realized we are importing the global metrics.
The Torrust Tracker can run multiple trackers at the same time in different socket addresses. However, the Index is only linked to one of them because the Index configuration only allows to specified one tracker at the moment. In the example above the UDP tracker udp://localhost:6969.
That means metrics would be wrong if you run more than one tracker!
The good think is one of task I'm working on is to segregate metrics in the stats endpoint. we have to update the imported to use only the metrics from the tracker associated to the Index.
cc @da2ce7
Depends on: torrust/torrust-tracker#1263
The Index is associates to one Torrust Tracker.
{ "tracker": { "api_url": "http://localhost:1212/", "listed": false, "private": false, "token": "***", "token_valid_seconds": 7257600, "url": "udp://localhost:6969" } }It imports the torrents stats from the Tracker's REST API:
https://tracker.torrust-demo.com/api/v1/stats?token=MyAccessToken
{ "torrents": 446911, "seeders": 76978, "completed": 639079, "leechers": 130149, "tcp4_connections_handled": 619, "tcp4_announces_handled": 619, "tcp4_scrapes_handled": 0, "tcp6_connections_handled": 0, "tcp6_announces_handled": 0, "tcp6_scrapes_handled": 0, "udp_requests_aborted": 5218855, "udp_requests_banned": 276466475, "udp_banned_ips_total": 21954, "udp_avg_connect_processing_time_ns": 1184148, "udp_avg_announce_processing_time_ns": 24523507, "udp_avg_scrape_processing_time_ns": 662305, "udp4_requests": 2738665346, "udp4_connections_handled": 890528651, "udp4_announces_handled": 1446412778, "udp4_scrapes_handled": 37958014, "udp4_responses": 2462193944, "udp4_errors_handled": 86755758, "udp6_requests": 0, "udp6_connections_handled": 0, "udp6_announces_handled": 0, "udp6_scrapes_handled": 0, "udp6_responses": 0, "udp6_errors_handled": 0 }I'm working on a big stats refactor and I've realized we are importing the global metrics.
The Torrust Tracker can run multiple trackers at the same time in different socket addresses. However, the Index is only linked to one of them because the Index configuration only allows to specified one tracker at the moment. In the example above the UDP tracker
udp://localhost:6969.That means metrics would be wrong if you run more than one tracker!
The good think is one of task I'm working on is to segregate metrics in the stats endpoint. we have to update the imported to use only the metrics from the tracker associated to the Index.
cc @da2ce7