feat(ai): Options for custom model cost mappings

[vgrozdanic]

Since this is still a very young field, there is a lot of irregularities in model naming. This PR introduces an option to configure custom model mappings, where we can assign alternative names to existing models in our pricing map. Often the same models have different names, depending on where they are hosted.

For example:

We need to have a way to add custom mappings, which can be easily changed and quickly deployed - that's why the options are used.

[cursor]

Bug: Custom Model Mapping Validation Errors

The ai-agent-monitoring.custom-model-mapping option lacks sufficient validation, leading to several issues:

1. If the option is configured as a non-iterable value (e.g., None), iterating over it will raise a TypeError.
2. If the option's list contains non-dictionary items, attempting to call .get() on them will result in an AttributeError.
3. If a custom model mapping entry has a missing or None alternative_model_id, the code will incorrectly add None as a key to the models_dict, potentially causing downstream issues.
   These validation failures can cause the AI model costs fetching task to fail.

src/sentry/tasks/ai_agent_monitoring.py#L79-L88

sentry/src/sentry/tasks/ai_agent_monitoring.py

Lines 79 to 88 in 76fec8d

	# in different hosting providers. This allows us to map the alternative model id to the existing model id.
	for model_mapping in options.get("ai-agent-monitoring.custom-model-mapping"):
	alternative_model_id = model_mapping.get("alternative_model_id")
	existing_model_id = model_mapping.get("existing_model_id")
	if existing_model_id not in models_dict or alternative_model_id in models_dict:
	continue
	models_dict[alternative_model_id] = models_dict[existing_model_id]

Fix in Cursor

---

Was this report helpful? Give feedback by reacting with 👍 or 👎