If the event name equals "ai.custom", the event is converted to Event telemetry. This appears in the customEvents table.
The Name field is populated from the "ai.customEvent.name" attribute. Users may use the opentelemetry_application_insights::attrs::CUSTOM_EVENT_NAME key for convenience.
Issues/explanations:
Why "ai.custom"? - Just "custom" seems nicer. Though I wouldn't be surprised if some users already send events with the name "custom" and I would like to avoid breaking their code. "ai.custom" seems weird enough that hopefully no one uses that, yet.
Declaring the customEvent name as an attribute is slightly ugly. It would be much nicer if we could use the event name for that. But I'm not sure how else to identify the custom event.
Works similar to exceptions:
opentelemetry_application_insights::attrs::CUSTOM_EVENT_NAME
key for convenience.Issues/explanations:
Closes #53