XMiDT

Multi-Tenant Metrics

To be able to see the traffic flows per tenant, it would be cool if we can add partner-id as a label to metrics that make sense. Ideally I don’t want to perform a special decode just to get this information.

Talaria Metrics

xmidt_talaria_outbound_requests
xmidt_talaria_hardware_model
xmidt_talaria_api_requests_total
(others that are easy and make sense to the implementer)

Caduceus Metrics

xmidt_caduceus_delivery_count
xmidt_caduceus_delivery_retry_count
(others that are easy and make sense to the implementer)

Scytale Metrics

xmidt_scytale_api_requests_total
(others that are easy and make sense to the implementer)

Tr1d1um (Webpa) Metrics

webpa_tr1d1um_api_requests_total
(others that are easy and make sense to the implementer)

Multiple Partner-Ids

My proposal for handling the possible multiple partner-ids:

  1. Provide a list of “ignore these” in configuration. This will let us ignore * for example.
  2. Make the list of remaining partner-ids an alphabetized, comma separated list like this:
    abe, crazy, dog as the “canonical” way to generate the the label.

Example 1

partner-ids: [ foo, bar, goo, *, dog ]
configuration says to ignore: *, foo

The canonical form: bar, dog, goo

Example 2

partner-ids: [ *, foo ]
configuration says to ignore: *, foo

The canonical form: <none>

Thoughts?
Wes

1 Like

Clarification questions:

  • What’s the max number of different partner-IDs we plan to support in the foreseeable future?
  • Would the “ignore these” config parameter be at the service level? i.e. scytale vs talaria could have different configs

support questions:
How to check the different types of config request in Webpa ?
Also, How to update wdmp in device using POST ?
There is no example of POST method in deploy

I’m not sure I understand the questions. Are they focused on multi-tenant metrics?