feat: Add universe-based analytics events to core services

[roncodes]

Overview

This PR adds analytics-agnostic event tracking to core Fleetbase services using the universe service's built-in Evented system. Events are emitted using dot notation naming convention and can be consumed by any analytics provider (e.g., PostHog in the internals engine).

Changes

CRUD Service (addon/services/crud.js)

• Added universe service injection
• Added _triggerResourceEvent() helper method to emit both generic and specific events
• Emit resource.deleted and {model_name}.deleted events after successful deletion
• Emit resource.bulk_action event for bulk operations
• Emit resource.imported and {model_name}.imported events after successful import

Resource Action Service (addon/services/resource-action.js)

• Added universe service injection
• Added _triggerResourceEvent() helper method
• Emit resource.created and {model_name}.created events in createTask
• Emit resource.updated and {model_name}.updated events in updateTask
• Emit appropriate events in saveTask based on whether record is new or existing
• Emit resource.deleted and {model_name}.deleted events in deleteTask

Session Service (addon/services/session.js)

• Added universe service injection
• Added sessionStartTime tracked property for duration calculation
• Emit session.initialized event when user session is loaded
• Emit session.terminated event with session duration when user logs out

Event Naming Convention

All events use dot notation following existing Fleetbase patterns:

• Generic events: resource.{action} (e.g., resource.created, resource.updated, resource.deleted)
• Specific events: {model_name}.{action} (e.g., order.created, vehicle.updated, driver.deleted)
• Session events: session.{action} (e.g., session.initialized, session.terminated)

Event Payloads

Event	Payload
resource.created	(model)
resource.updated	(model)
resource.deleted	(model)
resource.imported	(modelName, response, files)
resource.bulk_action	(verb, selected, firstModel)
session.initialized	(user, organization)
session.terminated	(user, sessionDuration)

Usage Example

In the internals engine (or any other consumer), subscribe to these events:

// In an initializer
const universe = appInstance.lookup('service:universe');
const posthog = appInstance.lookup('service:posthog');

// Listen for generic resource creation
universe.on('resource.created', (model) => {
  const modelName = getModelName(model);
  posthog.trackEvent(`${modelName}_created`, { id: model.id });
});

// Listen for specific order creation
universe.on('order.created', (order) => {
  posthog.trackEvent('order_created', {
    order_id: order.id,
    // ... other properties
  });
});

// Listen for session events
universe.on('session.initialized', (user, organization) => {
  posthog.identify(user.id, {
    email: user.email,
    company: organization.name
  });
});

Benefits

✅ Analytics-agnostic: No PostHog or analytics-specific code in core
✅ Non-breaking: Events are optional, existing functionality unchanged
✅ Extensible: Can be used for webhooks, audit logs, or any analytics provider
✅ Consistent naming: Follows existing Fleetbase dot notation convention
✅ Dual events: Both generic (resource.created) and specific (order.created) events for flexibility

Testing

Tested locally by:

1. Subscribing to events in console
2. Verifying events fire on CRUD operations
3. Confirming both generic and specific events are emitted
4. Validating session events fire on login/logout

Next Steps

• Add similar events to ember-ui components (buttons, modals, forms)
• Implement analytics listener in internals engine
• Add router transition events