UBT and UBA Horde Analytics not appearing

Development Pipeline & Plugins
, ,
1

We’re able to see Editor, Cook, and Horde build times data.

  1. Is there a specific configuration needed for UBT and UBA metrics to show up on the Horde Analytics page?
  2. Do we need to upgrade our Engine from 5.5.4 or is it possibly because we’re running UBACacheService on a separate machine?
2

Steps to Reproduce
Setup is this:

  • Horde Server & Agent: 5.4.2
    • *.project.json configured `“telemetryStoreId”: “engine”`
    • using configuration from Defaults:
      • default-metrics.telemetry.json
      • default-analytics.dashboard.json
  • Engine: 5.5.4
    • DefaultEngine.ini configured `[StudioTelemetry.Provider.HordeAnalytics]`
  • UBACacheService: 5.6.0
    • running separate from Horde, on a machine on the same network as the Agents

Compile jobs running on the Horde Agents/Jobs look to be configured with UBA correctly. Logs show:

```

Using Unreal Build Accelerator executor to run 520 action(s)

…

Total time in Unreal Build Accelerator executor: 14.18 seconds

```

3

Hey there Nixon,

I think what may be amiss here is the section name:

Further to this, the providers sections are controlled via the BuildConfiguration.xml:

<Telemetry> <Providers> <Item>StudioTelemetry.Provider.EpicStudio</Item> <Item>StudioTelemetry.Provider.Horde</Item> </Providers> </Telemetry>Fundamentally, I don’t think your telemetry endpoint configuration is being parsed (and as such, no data will make it through). You can also verify this is a data egress problem by checking your MongoDB, particularly the Metrics collection. If you determine it’s an egress problem and you’ve switched the DefaultEngine.ini section to [StudioTelemetry.Provider.Horde], try adding a breakpoint here to see whether the Telemetry.cs endpoints from config is being extracted properly.

Let me know if that helps!

Kind regards,

Julian

4

Thank you, that section name change was it! All the telemetry is showing up now.