While resolving #357, we found that some of the Oximeter types, e.g., OximeterMetadata appear in the dpd OpenAPI document. That's because they are returned by the (unpublished) oximeter_collect_meta_endpoint() API endpoint. They probably shouldn't be. The type here is entirely internal to Dendrite, and even for debugging purposes, the data it exposes is almost never relevant and can be retrieved through other means (SMF, pfiles, omdb, etc.).
If we remove this, then we can follow @jgallagher's good suggestion on #358, and move the oximeter configuration data to a shared crate, and then have specific methods for the tfportd or dpd producer IDs, or whatever new ones are added.
While resolving #357, we found that some of the Oximeter types, e.g.,
OximeterMetadataappear in thedpdOpenAPI document. That's because they are returned by the (unpublished)oximeter_collect_meta_endpoint()API endpoint. They probably shouldn't be. The type here is entirely internal to Dendrite, and even for debugging purposes, the data it exposes is almost never relevant and can be retrieved through other means (SMF,pfiles,omdb, etc.).If we remove this, then we can follow @jgallagher's good suggestion on #358, and move the oximeter configuration data to a shared crate, and then have specific methods for the
tfportdordpdproducer IDs, or whatever new ones are added.