Skip to content

Custom actor type names are still not used in Phobos 2.6.2 #82

Closed
@object

Description

@object

I have updated Phobos library to the version 2.6.2 but the Phobos metrics dashboard panels still show type-derived actor names.
Here are examples from "Live actors by type":

  • FunPersistentActor`1
  • FunActor`1

"Actors Starts and Stops by Type":

  • Akkling.Actors.FunActor<Nrk.Oddjob.Core.MessageTypes+AcknowledgementCommand>
  • Akkling.Actors.FunActor
  • Akkling.Persistence.FunPersistentActor

    I think we have two issues here. First is the major one: customized actor type names are not used. The second one is that these two panels use different actor names: "Live actors by type" uses the type name as returned by reflection, "Actors Starts and Stops by Type" uses more delicate approach and expands parameterized types with its arguments, i.e. showing as different actor types actors with different message types. Shouldn't these two panels use the same naming schema?

    I think it might be easier to locate the problem if I create a small subset of our code base that reproduces the error. It will take some time to extract a small code set.

    For the reference, here's the F# code we use to customize actor type names:

        let withActorTypeName actorTypeName (props: Props<_>) =
            let settings =
                Phobos.Actor.Configuration
                    .PhobosActorSettings(false, true)
                    .WithActorTypeName(actorTypeName)
            let deploy =
                match props.Deploy with
                | Some deploy -> deploy.WithInstrumentation(settings)
                | None -> Deploy.Local.WithInstrumentation(settings)
            { props with Deploy = Some deploy }
    
    

Metadata

Metadata

Assignees

No one assigned

    Labels

    actor-integration 📬Integration with Akka.NET runtimebugSomething isn't workingconfiguration 📃Issues related to HOCON configuration for individual drivers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions