Skip to content

Internal tracing of watchers end 2 end #97411

Open
@philippkahr

Description

@philippkahr

Description

Hi,

It would be great if I can use the internal instrumentation of Elasticsearch to identify what a watcher is doing from start to finish.

Right now, in Kibana instrumentation I get a task-run transaction that is per rule.
image

It would be great to get an individual transaction type like watcher and have it list out all watcher names / ids of the watchers and then I can drill down and see what exactly is going on in a single watcher. From the query, to transform, to conditions, to the actions. Each thing should be represented in it's own span, so I can identify if my query is bad, or if my transform with a complicated painless script is worse.

That is what an Kibana Rule looks like. I can see the full transaction and identify where the hookup is. I also get the failed transaction which would be me if the rule is broken. Would be helpful for Watchers as well.
overview elastic-cloud com_app_apm_services_kibana_transactions_view_kuery=labels deploymentId_%20%2212a0e5b525c14e57b156463ee7c8af67%22 rangeFrom=now-15m rangeTo=now environment=ENVIRONMENT_ALL serviceGroup= comparisonEnabled=true tran (2)

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions