LogoLogo
WebsiteYellowpaperTechnical DocumentationNuNet History and Operation
NuNet Public Alpha on Testnet (Deprecated)
NuNet Public Alpha on Testnet (Deprecated)
  • NuNet in Brief
  • NuNet Architecture
  • Fundamental Algorithms
  • Testing Use Cases
    • Decentralized ML Use Case
      • Compute Provider on NuNet
      • Service Provider on NuNet
  • Testing Configuration
    • Nami Wallet Setup
    • Eternl Wallet Setup
    • Cardano Testnet Guide: Basic Outline
    • tADA Faucet: Get tADA for transactions
    • mNTX Faucet: Get mNTX for testing
  • Components Installation
    • DMS (Device Management Service)
    • NuNet CLI: For Device Onboarding
    • Compute Provider Dashboard
    • Service Provider Dashboard
  • Telemetry Information
  • Troubleshooting Tools
  • Testing Campaigns - Get Involved
    • Stage 1: Create wallet (using Nami or Eternl)
    • Stage 2: Onboard on NuNet
    • Stage 3: Act as a Service Provider
    • Stage 4: Act as a Compute Provider
    • Request mNTX and Faucet
  • ML Code Examples
  • Research Papers
    • Extending GPU Container Support to AMD and Intel: A Developer Approach for Decentralized Scaling
  • Disclaimer
Powered by GitBook
On this page
Export as PDF

Telemetry Information

PreviousService Provider DashboardNextTroubleshooting Tools

Last updated 1 year ago

Please read NuNets before installing any software on your devices.

NuNet Network Status is live at , displaying real-time statistics about all computational processes executed on the network and their telemetry information. It tracks successful and failed processes, registered consumers, compute devices, and the amount of NuNet tokens paid by service providers to compute providers.

Dials on the right show available resources and current utilization percentages. Graphs on the left display resource availability over time.

The table at the bottom on the left displays the "heartbeats" (these are updated every minute) from currently active DMS nodes. You can expand the event to see the details.

The hearbeats list the onboarded ram and cpu for each dms so can be used to calculate the currenty available resources.

  • RAM: Memory used by a process, measured in megabyte seconds (MBs). The metric is calculated by adding spot RAM usages sampled every second for the entire time of execution, indicating actual memory consumption.

  • CPU: Processor work used to complete a process, measured in MTicks (million ticks), showing CPU time used during execution.

  • ID: lists the peer id for the heartbeat. This can be used to filter the dashboard to show events from a specific peer, see below.

The table at the bottom on the right hand side displays telemetry metrics for each process running on NuNet. You can expand these events to reveal the details.

You can see job status, time it took to run, ram, cpu and network used and the amount of ntx.

Disclaimer
Nunet Status Dashboard
Heartbeat events
Filtering for a specific peers events.
Service call details.