Skip to content

Commit

Permalink
split avail reports by chain (#128)
Browse files Browse the repository at this point in the history 
* chore: split avail reports by chain (#126)

* chore: hide Goldberg reports

* chore: split avail reports by chain and move goldberg reports to easy link

* fix: split avail reports by chain and fix the links

* added keydensity to menu

---------

Co-authored-by: guillaumemichel <[email protected]>
  • Loading branch information
@kasteph @guillaumemichel
kasteph and guillaumemichel authored Sep 6, 2024
1 parent 6929718 commit 727ac12
Show file tree
Hide file tree
Showing 31 changed files with 292 additions and 268 deletions.
20 changes: 10 additions & 10 deletions content.en/avail/dht/2024-10-report.md → ...t.en/avail/dht/goldberg/2024-10-report.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,19 +24,19 @@ Timestamps are in UTC if not mentioned otherwise.

This visualizes the uptime of peers over a specific period of time. The plot may display trends in churn rate, distribution of uptime periods, or patterns in peer activity. It helps analyze the stability and reliability of the network by identifying fluctuations in peer participation and examining potential factors influencing churn.

{{< plotly json="../../../plots/2024/03/04/avail-plot-churn.json" height="600px" >}}
{{< plotly json="/plots/2024/03/04/avail-plot-churn.json" height="600px" >}}

### Geolocation

Geographical data is sourced from the [MaxMind database](https://www.maxmind.com), which maps IP addresses to corresponding countries.

This bar plot illustrates the distribution of observed nodes across different countries.

{{< plotly json="../../../plots/2024/03/04/avail-geo-agent-All-bars.json" height="600px" >}}
{{< plotly json="/plots/2024/03/04/avail-geo-agent-All-bars.json" height="600px" >}}

This plot displays the weekly geographical distribution of nodes, categorized by country.

{{< plotly json="../../../plots/2024/03/04/avail-geo-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/04/avail-geo-agent-All-lines.json" height="600px" >}}

### Cloud Providers

Expand All @@ -48,29 +48,29 @@ This line chart displays the count of nodes within the Avail network that are ho

Regular analysis of this chart can reveal trends in the adoption of cloud services for nodes. Such information is crucial for understanding the network's resilience and the potential reliance on cloud infrastructure.

{{< plotly json="../../../plots/2024/03/04/avail-cloud-rate-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/04/avail-cloud-rate-agent-All-lines.json" height="600px" >}}

This bar chart presents the weekly distribution of Avail nodes among various cloud providers, including nodes not hosted within data centers (grouped under _Non-Datacenter_).

{{< plotly json="../../../plots/2024/03/04/avail-cloud-agent-All-bars.json" height="600px" >}}
{{< plotly json="/plots/2024/03/04/avail-cloud-agent-All-bars.json" height="600px" >}}

The line chart illustrates the trends in the distribution of all Avail nodes across cloud providers over the given time period. Note that nodes hosted outside of data centers are not included in this representation.

{{< plotly json="../../../plots/2024/03/04/avail-cloud-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/04/avail-cloud-agent-All-lines.json" height="600px" >}}

### Crawls

#### Protocols

This plot illustrates the evolving count of nodes supporting each of the listed protocols over time. It exclusively presents data gathered from nodes accessible through a libp2p connection via our crawler. The identification of supported protocols relies on the [libp2p identify protocol](https://github.com/libp2p/specs/tree/master/identify), hence necessitating a libp2p connection for discovery.

{{< plotly json="../../../plots/2024/03/04/avail-crawl-protocols.json" height="1200px" >}}
{{< plotly json="/plots/2024/03/04/avail-crawl-protocols.json" height="1200px" >}}

#### Errors

{{< plotly json="../../../plots/2024/03/04/avail-connection-errors-single.json" height="600px" >}}
{{< plotly json="/plots/2024/03/04/avail-connection-errors-single.json" height="600px" >}}

{{< plotly json="../../../plots/2024/03/04/avail-crawl-errors-single.json" height="600px" >}}
{{< plotly json="/plots/2024/03/04/avail-crawl-errors-single.json" height="600px" >}}

## Stale Node Records

Expand All @@ -82,4 +82,4 @@ Ensuring the reachability of referenced nodes shared within the network holds pa

For instance, if a node's record is present in the routing tables of 100 other nodes and the node is reachable, the plot will reflect an increase of 100 in the _online_ category.

{{< plotly json="../../../plots/2024/03/04/avail-stale-records-stacked.json" height="600px" >}}
{{< plotly json="/plots/2024/03/04/avail-stale-records-stacked.json" height="600px" >}}
20 changes: 10 additions & 10 deletions content.en/avail/dht/2024-11-report.md → ...t.en/avail/dht/goldberg/2024-11-report.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,19 +24,19 @@ Timestamps are in UTC if not mentioned otherwise.

This visualizes the uptime of peers over a specific period of time. The plot may display trends in churn rate, distribution of uptime periods, or patterns in peer activity. It helps analyze the stability and reliability of the network by identifying fluctuations in peer participation and examining potential factors influencing churn.

{{< plotly json="../../../plots/2024/03/11/avail-plot-churn.json" height="600px" >}}
{{< plotly json="/plots/2024/03/11/avail-plot-churn.json" height="600px" >}}

### Geolocation

Geographical data is sourced from the [MaxMind database](https://www.maxmind.com), which maps IP addresses to corresponding countries.

This bar plot illustrates the distribution of observed nodes across different countries.

{{< plotly json="../../../plots/2024/03/11/avail-geo-agent-All-bars.json" height="600px" >}}
{{< plotly json="/plots/2024/03/11/avail-geo-agent-All-bars.json" height="600px" >}}

This plot displays the weekly geographical distribution of nodes, categorized by country.

{{< plotly json="../../../plots/2024/03/11/avail-geo-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/11/avail-geo-agent-All-lines.json" height="600px" >}}

### Cloud Providers

Expand All @@ -48,29 +48,29 @@ This line chart displays the count of nodes within the Avail network that are ho

Regular analysis of this chart can reveal trends in the adoption of cloud services for nodes. Such information is crucial for understanding the network's resilience and the potential reliance on cloud infrastructure.

{{< plotly json="../../../plots/2024/03/11/avail-cloud-rate-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/11/avail-cloud-rate-agent-All-lines.json" height="600px" >}}

This bar chart presents the weekly distribution of Avail nodes among various cloud providers, including nodes not hosted within data centers (grouped under _Non-Datacenter_).

{{< plotly json="../../../plots/2024/03/11/avail-cloud-agent-All-bars.json" height="600px" >}}
{{< plotly json="/plots/2024/03/11/avail-cloud-agent-All-bars.json" height="600px" >}}

The line chart illustrates the trends in the distribution of all Avail nodes across cloud providers over the given time period. Note that nodes hosted outside of data centers are not included in this representation.

{{< plotly json="../../../plots/2024/03/11/avail-cloud-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/11/avail-cloud-agent-All-lines.json" height="600px" >}}

### Crawls

#### Protocols

This plot illustrates the evolving count of nodes supporting each of the listed protocols over time. It exclusively presents data gathered from nodes accessible through a libp2p connection via our crawler. The identification of supported protocols relies on the [libp2p identify protocol](https://github.com/libp2p/specs/tree/master/identify), hence necessitating a libp2p connection for discovery.

{{< plotly json="../../../plots/2024/03/11/avail-crawl-protocols.json" height="1200px" >}}
{{< plotly json="/plots/2024/03/11/avail-crawl-protocols.json" height="1200px" >}}

#### Errors

{{< plotly json="../../../plots/2024/03/11/avail-connection-errors-single.json" height="600px" >}}
{{< plotly json="/plots/2024/03/11/avail-connection-errors-single.json" height="600px" >}}

{{< plotly json="../../../plots/2024/03/11/avail-crawl-errors-single.json" height="600px" >}}
{{< plotly json="/plots/2024/03/11/avail-crawl-errors-single.json" height="600px" >}}

## Stale Node Records

Expand All @@ -82,4 +82,4 @@ Ensuring the reachability of referenced nodes shared within the network holds pa

For instance, if a node's record is present in the routing tables of 100 other nodes and the node is reachable, the plot will reflect an increase of 100 in the _online_ category.

{{< plotly json="../../../plots/2024/03/11/avail-stale-records-stacked.json" height="600px" >}}
{{< plotly json="/plots/2024/03/11/avail-stale-records-stacked.json" height="600px" >}}
20 changes: 10 additions & 10 deletions content.en/avail/dht/2024-12-report.md → ...t.en/avail/dht/goldberg/2024-12-report.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,19 +24,19 @@ Timestamps are in UTC if not mentioned otherwise.

This visualizes the uptime of peers over a specific period of time. The plot may display trends in churn rate, distribution of uptime periods, or patterns in peer activity. It helps analyze the stability and reliability of the network by identifying fluctuations in peer participation and examining potential factors influencing churn.

{{< plotly json="../../../plots/2024/03/18/avail-plot-churn.json" height="600px" >}}
{{< plotly json="/plots/2024/03/18/avail-plot-churn.json" height="600px" >}}

### Geolocation

Geographical data is sourced from the [MaxMind database](https://www.maxmind.com), which maps IP addresses to corresponding countries.

This bar plot illustrates the distribution of observed nodes across different countries.

{{< plotly json="../../../plots/2024/03/18/avail-geo-agent-All-bars.json" height="600px" >}}
{{< plotly json="/plots/2024/03/18/avail-geo-agent-All-bars.json" height="600px" >}}

This plot displays the weekly geographical distribution of nodes, categorized by country.

{{< plotly json="../../../plots/2024/03/18/avail-geo-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/18/avail-geo-agent-All-lines.json" height="600px" >}}

### Cloud Providers

Expand All @@ -48,29 +48,29 @@ This line chart displays the count of nodes within the Avail network that are ho

Regular analysis of this chart can reveal trends in the adoption of cloud services for nodes. Such information is crucial for understanding the network's resilience and the potential reliance on cloud infrastructure.

{{< plotly json="../../../plots/2024/03/18/avail-cloud-rate-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/18/avail-cloud-rate-agent-All-lines.json" height="600px" >}}

This bar chart presents the weekly distribution of Avail nodes among various cloud providers, including nodes not hosted within data centers (grouped under _Non-Datacenter_).

{{< plotly json="../../../plots/2024/03/18/avail-cloud-agent-All-bars.json" height="600px" >}}
{{< plotly json="/plots/2024/03/18/avail-cloud-agent-All-bars.json" height="600px" >}}

The line chart illustrates the trends in the distribution of all Avail nodes across cloud providers over the given time period. Note that nodes hosted outside of data centers are not included in this representation.

{{< plotly json="../../../plots/2024/03/18/avail-cloud-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/18/avail-cloud-agent-All-lines.json" height="600px" >}}

### Crawls

#### Protocols

This plot illustrates the evolving count of nodes supporting each of the listed protocols over time. It exclusively presents data gathered from nodes accessible through a libp2p connection via our crawler. The identification of supported protocols relies on the [libp2p identify protocol](https://github.com/libp2p/specs/tree/master/identify), hence necessitating a libp2p connection for discovery.

{{< plotly json="../../../plots/2024/03/18/avail-crawl-protocols.json" height="1200px" >}}
{{< plotly json="/plots/2024/03/18/avail-crawl-protocols.json" height="1200px" >}}

#### Errors

{{< plotly json="../../../plots/2024/03/18/avail-connection-errors-single.json" height="600px" >}}
{{< plotly json="/plots/2024/03/18/avail-connection-errors-single.json" height="600px" >}}

{{< plotly json="../../../plots/2024/03/18/avail-crawl-errors-single.json" height="600px" >}}
{{< plotly json="/plots/2024/03/18/avail-crawl-errors-single.json" height="600px" >}}

## Stale Node Records

Expand All @@ -82,4 +82,4 @@ Ensuring the reachability of referenced nodes shared within the network holds pa

For instance, if a node's record is present in the routing tables of 100 other nodes and the node is reachable, the plot will reflect an increase of 100 in the _online_ category.

{{< plotly json="../../../plots/2024/03/18/avail-stale-records-stacked.json" height="600px" >}}
{{< plotly json="/plots/2024/03/18/avail-stale-records-stacked.json" height="600px" >}}
20 changes: 10 additions & 10 deletions content.en/avail/dht/2024-13-report.md → ...t.en/avail/dht/goldberg/2024-13-report.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,19 +24,19 @@ Timestamps are in UTC if not mentioned otherwise.

This visualizes the uptime of peers over a specific period of time. The plot may display trends in churn rate, distribution of uptime periods, or patterns in peer activity. It helps analyze the stability and reliability of the network by identifying fluctuations in peer participation and examining potential factors influencing churn.

{{< plotly json="../../../plots/2024/03/25/avail-plot-churn.json" height="600px" >}}
{{< plotly json="/plots/2024/03/25/avail-plot-churn.json" height="600px" >}}

### Geolocation

Geographical data is sourced from the [MaxMind database](https://www.maxmind.com), which maps IP addresses to corresponding countries.

This bar plot illustrates the distribution of observed nodes across different countries.

{{< plotly json="../../../plots/2024/03/25/avail-geo-agent-All-bars.json" height="600px" >}}
{{< plotly json="/plots/2024/03/25/avail-geo-agent-All-bars.json" height="600px" >}}

This plot displays the weekly geographical distribution of nodes, categorized by country.

{{< plotly json="../../../plots/2024/03/25/avail-geo-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/25/avail-geo-agent-All-lines.json" height="600px" >}}

### Cloud Providers

Expand All @@ -48,29 +48,29 @@ This line chart displays the count of nodes within the Avail network that are ho

Regular analysis of this chart can reveal trends in the adoption of cloud services for nodes. Such information is crucial for understanding the network's resilience and the potential reliance on cloud infrastructure.

{{< plotly json="../../../plots/2024/03/25/avail-cloud-rate-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/25/avail-cloud-rate-agent-All-lines.json" height="600px" >}}

This bar chart presents the weekly distribution of Avail nodes among various cloud providers, including nodes not hosted within data centers (grouped under _Non-Datacenter_).

{{< plotly json="../../../plots/2024/03/25/avail-cloud-agent-All-bars.json" height="600px" >}}
{{< plotly json="/plots/2024/03/25/avail-cloud-agent-All-bars.json" height="600px" >}}

The line chart illustrates the trends in the distribution of all Avail nodes across cloud providers over the given time period. Note that nodes hosted outside of data centers are not included in this representation.

{{< plotly json="../../../plots/2024/03/25/avail-cloud-agent-All-lines.json" height="600px" >}}
{{< plotly json="/plots/2024/03/25/avail-cloud-agent-All-lines.json" height="600px" >}}

### Crawls

#### Protocols

This plot illustrates the evolving count of nodes supporting each of the listed protocols over time. It exclusively presents data gathered from nodes accessible through a libp2p connection via our crawler. The identification of supported protocols relies on the [libp2p identify protocol](https://github.com/libp2p/specs/tree/master/identify), hence necessitating a libp2p connection for discovery.

{{< plotly json="../../../plots/2024/03/25/avail-crawl-protocols.json" height="1200px" >}}
{{< plotly json="/plots/2024/03/25/avail-crawl-protocols.json" height="1200px" >}}

#### Errors

{{< plotly json="../../../plots/2024/03/25/avail-connection-errors-single.json" height="600px" >}}
{{< plotly json="/plots/2024/03/25/avail-connection-errors-single.json" height="600px" >}}

{{< plotly json="../../../plots/2024/03/25/avail-crawl-errors-single.json" height="600px" >}}
{{< plotly json="/plots/2024/03/25/avail-crawl-errors-single.json" height="600px" >}}

## Stale Node Records

Expand All @@ -82,4 +82,4 @@ Ensuring the reachability of referenced nodes shared within the network holds pa

For instance, if a node's record is present in the routing tables of 100 other nodes and the node is reachable, the plot will reflect an increase of 100 in the _online_ category.

{{< plotly json="../../../plots/2024/03/25/avail-stale-records-stacked.json" height="600px" >}}
{{< plotly json="/plots/2024/03/25/avail-stale-records-stacked.json" height="600px" >}}
Loading

0 comments on commit 727ac12

Please sign in to comment.