added cdr event as key

[afek854]

PR Type

bug_fix

---

Description

• Fixed the serialization tags for the cdr.CdrAlert field in the RuntimeAlert struct to ensure proper handling of JSON and BSON data.
• Changed the tags from inline to cdrevent for both JSON and BSON.

---

Changes walkthrough 📝

	Relevant files
Bug fix	runtimeincidents.go Fix serialization tags for CdrAlert in RuntimeAlert struct armotypes/runtimeincidents.go Changed the JSON and BSON tags for cdr.CdrAlert from inline to cdrevent. This change ensures correct serialization and deserialization of cdr.CdrAlert. +1/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Data Migration Changing the serialization format from inline to a named field may require data migration for existing records. Verify backwards compatibility or ensure proper migration strategy is in place.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
General	Use more descriptive field names in struct tags to improve code clarity and maintainability Consider using a more descriptive field name for the embedded CdrAlert struct. The current tag "cdrevent" is generic and could be ambiguous. Use a more specific name that reflects the nature of the CDR alert data. armotypes/runtimeincidents.go [160] -cdr.CdrAlert `json:"cdrevent" bson:"cdrevent"` +cdr.CdrAlert `json:"cdrAlertData" bson:"cdrAlertData"` Apply this suggestion Suggestion importance[1-10]: 4 Why: While the suggestion to use a more specific tag name is valid for better code clarity, changing from "cdrevent" to "cdrAlertData" offers only a moderate improvement in code readability and the existing name is already functional and clear enough.	4