elastic / elastic/apm-agent-python

Enable custom transaction naming (GraphQL specific)

Open
#1,583 0 comments 0 reactions 0 assignees View on GitHub
agent-python community feature
Dominant language
Python
Stars
431
Forks
239
Avg merge
5d 10h
Merged PRs (30d)
7

Description

Hi, I've recently started using APM for a django based project using a GraphQL API (built with `graphene_django`). I find it very difficult to view the logs on my service with the current naming convention as they all start with the same prefix (see picture).

Screen Shot 2022-07-08 at 10 09 54 AM

The problem is further exasperated by the fact that the naming is based on what the frontend programmer defines. For ex, `GraphQL QUERY Name(value='TradeAssetAmountPickerQuery')`. If I were to change the name query on the frontend to `TradeAssetSomeOtherValuePickerQuery`, it would change the grouping on the dashboard. Given that I am planning on exposing this API publicly, this would make my logs next to impossible to organize based on the fact that developers could name their queries / mutations however they want.

**Describe the solution you'd like**
A hook where I can define my own naming convention for transactions - ideally based on what the mutation / query is actually called in the schema.

**Describe alternatives you've considered**
Forking the library and creating my own build, although I don't really have the time to do this.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.