Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upLogging subscription broadcast timing? #653
Closed
Labels
Comments
|
Absinthe should probably integrate with Telemetry to emit events. Notably, in this particular case all that Absinthe can measure is the time required to run / broadcast on a specific document topic. There may be multiple actual processes subscribed to that topic. Broadcasting to those would be handled by PhoenixPubSub so Absinthe isn't able to emit events at that level of granularity. PR is welcome with a telemetry integration. |
|
Telemetry is now included in Absinthe. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looking into tracking the delay between when a change in the data happens and the eventual
publish_subscriptionbroadcast that sends a message out to each subscribed user, there's currently no easy way to retrieve that information.Being able to measure how long it takes for the system to process an update and push it out to subscribed users would be nice to have from a performance benchmarking / monitoring perspective.