Open RickMoynihan opened 2 years ago
We currently give datadog metrics on drafter.sparql.update.time which reports metrics on arbitrary sparql updates.
drafter.sparql.update.time
https://github.com/Swirrl/drafter/blob/master/drafter/src/drafter/rdf/sparql.clj#L40
It would be useful to break this down by operation too, to give us a little more visibility on what is happening and where time is spent.
The above function is called from approximately 21 other call sites e.g.
drafter.backend.draftset.draft-management/upsert-single-object!
drafter.backend.draftset.operations/delete-draftset-statements!
I think it makes sense to wrap a datadog/measure! over most (if not all) of these call sites to provide more visibility, on what is happening; and then surface this in our datadog boards.
datadog/measure!
We currently give datadog metrics on
drafter.sparql.update.timewhich reports metrics on arbitrary sparql updates.https://github.com/Swirrl/drafter/blob/master/drafter/src/drafter/rdf/sparql.clj#L40
It would be useful to break this down by operation too, to give us a little more visibility on what is happening and where time is spent.
The above function is called from approximately 21 other call sites e.g.
drafter.backend.draftset.draft-management/upsert-single-object!drafter.backend.draftset.operations/delete-draftset-statements!I think it makes sense to wrap a
datadog/measure!over most (if not all) of these call sites to provide more visibility, on what is happening; and then surface this in our datadog boards.