Define distributed RPC/Request TRACING strategy and tooling recommendation
Open, MediumPublicSpike
Actions

Assigned To

None

Authored By

	lmata
	Oct 5 2020, 8:46 PM

Description

I'm creating this task as an EPIC to hold the main case for defining a strategy, tool selection, user research and all the pertaining tasks to define what tracing looks like.

I have not found a similar or previous task related to this topic if there is one existing please link and we can use that to supersede this one.

Related Objects

Mentioned In: T263656: [spike] Correlate events between echo and push notifications service to extract metrics
Mentioned Here: T158691: Cassandra query tracing
T201409: Harmonise the identification of requests across our stack
T223727: Investigate OpenTracing integration with MediaWiki

Event Timeline

lmata created this task.Oct 5 2020, 8:46 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 5 2020, 8:46 PM

lmata renamed this task from Define & implement TRACING strategy and tooling to Define TRACING strategy and tooling recommendation.Oct 5 2020, 9:04 PM

lmata triaged this task as Medium priority.

lmata changed the subtype of this task from "Task" to "Spike".

thcipriani subscribed.Oct 5 2020, 9:36 PM

Some related earlier work:

T201409: Harmonise the identification of requests across our stack lots of work to get Request-ID headers consistently passed from service to service
T223727: Investigate OpenTracing integration with MediaWiki past Mediawiki Hackathon sprint but not clear if any code landed anywhere?
T158691 Cassandra-specific, but it still would be interesting/valuable to collect these traces (or trigger them when a user asks for tracing

I'm also being bold and retitling this bug to make its description a bit clearer IMO

CDanis renamed this task from Define TRACING strategy and tooling recommendation to Define distributed RPC/Request TRACING strategy and tooling recommendation.Oct 5 2020, 10:44 PM

LSobanski subscribed.Oct 6 2020, 9:33 AM

Jgiannelos mentioned this in T263656: [spike] Correlate events between echo and push notifications service to extract metrics.Oct 6 2020, 11:17 AM

herron subscribed.Oct 6 2020, 4:07 PM

• mmodell awarded a token.Oct 13 2020, 3:46 PM

• mmodell subscribed.

This looks interesting, though it's geared towards a microservice architecture. It might be worth looking at anyway: https://www.jaegertracing.io/

lmata edited projects, added SRE Observability; removed observability.Jul 12 2021, 2:21 AM

lmata moved this task from Inbox to Backlog on the SRE Observability board.Jul 15 2021, 4:08 AM

lmata edited projects, added SRE Observability (FY2021/2022-Q1); removed SRE Observability.Jul 15 2021, 4:13 AM

lmata edited projects, added SRE Observability; removed SRE Observability (FY2021/2022-Q1).Jul 26 2021, 3:22 PM

lmata edited projects, added Observability-Tracing; removed SRE Observability.Aug 9 2021, 2:42 AM

lmata removed lmata as the assignee of this task.Apr 4 2022, 4:25 PM

lmata moved this task from Inbox to Backlog on the Observability-Tracing board.Sep 14 2022, 7:15 PM

Define distributed RPC/Request TRACING strategy and tooling recommendationOpen, MediumPublicSpikeActions

Description

Related Objects

Event Timeline

Define distributed RPC/Request TRACING strategy and tooling recommendation
Open, MediumPublicSpike
Actions