ai_ prometheus metrics produced with inconsistent pipeline tag

[pwilczynskiclearcode]

It's maybe not a bug but an inconvenience resulting in multiple similar tags being produced.

• pipeline value produced in
  monitor.AIProcessingError(err.Error(), pipeline, ... is equal to text-to-image, image-to-image, upscale, image-to-video, audio-to-text, segment-anything-2 - lowercased with - as a separator.
• In submitSegmentAnything2 it's produced as segment anything 2 (lower case, space separated).
• no orchestrators available... errors are produced using capName resulting in Text to image, Image to image, Image to video, Upscale, Audio to text, Segment anything 2 (First letter uppercase, space separated).

And because of that when trying to filter based on pipeline on Grafana we get "duplicates":

We need some unification.

[ad-astra-video]

This is a good find! Thank you for bringing this forward!

Could we use the PipelineToCapability function to make them all use the capability name? The PipelineToCapability function was introduced with the maxPricePerCapability addition to parse the pipelines input into the json pricing input to capabilities to try and avoid another a long switch statement to manually assign the capabilities based on the text input (see handleAIRequest as an example).

Open to alternative implementations of the PipelineToCapability function to make it less brittle. Maybe should remove the string parsing and just put in a switch statement in PipelineToCapability to assign the capabilities more directly? Other ideas welcomed here! An example of the brittle nature of this function is I provided incorrect advice to rename the Large Language Model capability description added with LLMs to Large language model in review of that PR. I think it should instead be Llm to correctly find the capability for the llm pipeline in the PipelineToCapability function.

[pwilczynskiclearcode]

I already posted a PR trying to transform capability to pipeline name (pipeline names aren't defined globally by any const).
The prometheus tag/label is called pipeline so I wanted to produce it in "pipeline" format, not capability.