DiffoExample.Nbn.NniGroupMetrics (DiffoExample v0.3.0)

Local metrics characteristic for an NNI Group — demand-side aggregates across assigned CVCs (cvcs_count, cvcs_total_bandwidth), capacity-side aggregates across comprised NNIs (nnis_count, nnis_total_bandwidth), and the derived utilization = cvcs_total_bandwidth / nnis_total_bandwidth.

Expected utilization range 0–1 under normal provisioning; >1 indicates deliberate oversubscription. Not inheritable.

Live metrics for an NNI Group — demand from CVCs, capacity from NNIs, and utilization

Summary

Types

t()

Functions

default_short_name()

input(opts)

Validates that the keys in the provided input are valid for at least one action on the resource.

input(opts, action)

Same as input/1, except restricts the keys to values accepted by the action provided.

primary_key_matches?(left, right)

Types

t()

@type t() :: %DiffoExample.Nbn.NniGroupMetrics{
  __lateral_join_source__: term(),
  __meta__: term(),
  __metadata__: term(),
  __order__: term(),
  aggregates: term(),
  calculations: term(),
  created_at: term(),
  feature: term(),
  feature_id: term(),
  id: term(),
  instance: term(),
  instance_id: term(),
  name: term(),
  updated_at: term(),
  value: term()
}

Functions

default_short_name()

input(opts)

@spec input(values :: map() | Keyword.t()) :: map() | no_return()

Validates that the keys in the provided input are valid for at least one action on the resource.

Raises a KeyError error at compile time if not. This exists because generally a struct should only ever be created by Ash as a result of a successful action. You should not be creating records manually in code, e.g %MyResource{value: 1, value: 2}. Generally that is fine, but often with embedded resources it is nice to be able to validate the keys that are being provided, e.g

Resource
|> Ash.Changeset.for_create(:create, %{embedded: EmbeddedResource.input(foo: 1, bar: 2)})
|> Ash.create()

input(opts, action)

@spec input(values :: map() | Keyword.t(), action :: atom()) :: map() | no_return()

Same as input/1, except restricts the keys to values accepted by the action provided.

primary_key_matches?(left, right)