topic Best practice for naming custom event name across platforms in Dynatrace in Real User Monitoring

Best practice for naming custom event name across platforms in Dynatrace

mkarmocha — Fri, 17 Apr 2026 06:48:04 GMT

I’m currently working on defining cross‑platform naming guidelines for custom Dynatrace events (Android, iOS, and Web) to ensure consistency and ease of use during incident analysis.

While reviewing Dynatrace documentation, I couldn’t find explicit guidance on recommended naming formats for custom events (for example:

UPPER_CASE_WITH_UNDERSCORES
camelCase
kebab-case / snake_case)

In practice, we see different conventions already in use across platforms, often driven by SDK or language norms.

I’d like to understand from a Dynatrace perspective:

Is there a preferred or recommended event naming format for custom events?
Are there any formats to avoid due to searchability, filtering, or correlation in Dynatrace?
Does Dynatrace have different recommendations per platform, or is a single convention preferred across all?
From an operations standpoint, what naming style tends to work best during incident investigation?

Could someone point me to right documentation or any guidance, examples, or pointers to best practices would be greatly appreciated.

Re: Best practice for naming custom event name across platforms in Dynatrace

t_pawlak — Fri, 17 Apr 2026 07:28:32 GMT

Dynatrace does not enforce a specific naming convention, but best practice is, use one consistent format across all platforms. Just try avoid mixed styles (camelCase + UPPER_CASE), spaces, platform-specific names, putting details into event name (use attributes instead)

Re: Best practice for naming custom event name across platforms in Dynatrace

mkarmocha — Mon, 20 Apr 2026 03:14:55 GMT

Thanks for the clarification — that’s helpful @t_pawlak .

I had one follow‑up question:
Do you mind sharing how Dynatrace typically names custom events internally or in examples across Android, iOS, and Web platforms?

In practice, we’re seeing different conventions already in use (for example, camelCase or kebab‑case on Android, potentially different styles on iOS, and UPPER_CASE_WITH_UNDERSCORES on Web).
I’m curious whether Dynatrace tends to follow platform‑native conventions in examples, or prefers a single uniform naming style across platforms when possible.

Any guidance or examples would be appreciated.

Re: Best practice for naming custom event name across platforms in Dynatrace

matthias_hochri — Mon, 20 Apr 2026 09:22:33 GMT

Are you talking about RUM on Grail Events? Or which APIs are you talking about? reportEvent? sendEvent? Action APIs?

Re: Best practice for naming custom event name across platforms in Dynatrace

mkarmocha — Mon, 20 Apr 2026 23:55:38 GMT

We are using the dtrum APIs on Web and Mobile (Android/iOS).
Specifically, we trigger events using addAction and leaveAction so i think its user action api's and reportCustomError to capture messages and properties in Dynatrace.

These events are operational/lifecycle events (for example: SDK initialization, identify, and evaluation failure).
The goal is to apply consistent naming across Android, iOS, and Web to support searchability and incident analysis.