Skip to content
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.

Sign up for GitHub

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

Jump to bottom

removing refernces of Metrika dashboard #926

Merged
merged 1 commit into from
Oct 3, 2024
Merged

removing refernces of Metrika dashboard #926

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/networks/node-ops/access-onchain-data/access-nodes/access-node-setup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Confirmation of a new node's inclusion in epoch N+1 is included in the [`EpochSe
## Limitations

There are five open slots for access nodes every epoch.
You can view the exact epoch phase transition time [here](https://app.metrika.co/flow/dashboard/network-overview?tr=1d) under `Epoch Phase`.
You can view the exact epoch phase transition time [here](https://dashboard.flow.com/) under `Epoch Phase`.

To summarize,

Expand Down
5 changes: 0 additions & 5 deletions docs/networks/node-ops/node-operation/monitoring-nodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,8 +91,3 @@ The metrics include the account address of the machine account (`acct_address` l
machine_account_balance{acct_address="7b16b57ae0a3c6aa"} 9.99464935
```

## Monitoring a Flow node using Metrika Monitoring

Metrika has developed the Flow node monitoring service and is the recommended way of monitoring a Flow node.
It is a free tool that uses the logs and metrics published by the node and provides access to private node-specific dashboards.
Follow this [link](https://app.metrika.co/flow/node/install-agent) to setup the Metrika monitoring for your node.
2 changes: 1 addition & 1 deletion docs/networks/node-ops/node-operation/protocol-state-bootstrap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ Two flags are used to specify when to bootstrap:
- `--dynamic-startup-epoch-phase` - the epoch phase to start up in (default `EpochPhaseSetup`)
- `--dynamic-startup-epoch` - the epoch counter to start up in (default `current`)

> You can check the current epoch phase of the network by running [this](https://github.com/onflow/flow-core-contracts/blob/master/transactions/epoch/scripts/get_epoch_phase.cdc) script. Alternatively, you can also check the current epoch phase [here](https://app.metrika.co/flow/dashboard/network-overview) under Epoch Phase.
> You can check the current epoch phase of the network by running [this](https://github.com/onflow/flow-core-contracts/blob/master/transactions/epoch/scripts/get_epoch_phase.cdc) script. Alternatively, you can also check the current epoch phase [here](https://dashboard.flow.com/) under Epoch Phase.

#### Bootstrapping Immediately

Expand Down
Loading