Skip to content

Add operational metrics to API #35

@fabiante

Description

@fabiante

Related to #28

Having metrics for the API will allow close monitoring of the systems health, what is happending and how the API is used. It would be benefitial to have the ability to answer these questions:

  • how many purls are created per T
  • how many purls are resolved per T
  • how long is the average / median purl create time?
  • how long is the average / median purl resolve time?
  • how many domains exist
  • how many purls exist in total

With these questions answered, monitoring the systems overall health seems possible. It is important that PURL creation and resolution take at most X miliseconds even under high load (again, this is where #28 is important).

Metadata

Metadata

Assignees

No one assigned

    Labels

    storyUser story which adds any value to the project

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions