parse-community / parse-community/parse-server

Request Tracking

Open
#6,323 13 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:feature
Dominant language
JavaScript
Stars
21.4k
Forks
4.8k
Avg merge
7h 45m
Merged PRs (30d)
11

Description

I am unable to track down the main start point of any api request made to parse-server.
For Example:

Parse.Cloud.define('A', async (req, option) => {
    console.log('>>>>CallToA', option);
    return new Parse.Query(Parse.User).findAll(option);
});

Parse.Cloud.define('B', async (req, option) => {
    console.log('>>>>CallToB', option);
    return Parse.Cloud.run('A', {}, option);
});

Parse.Cloud.define('C', async (req, option) => {
    console.log('>>>>CallToC', option);
    return Parse.Cloud.run('A', {}, option);
});

If I get some error while making query in User table defined Cloud function "A". I am unable to trace back wheather client started requested from Cloud function "A" or "B" or "C".

What I am looking is an option to pass requestId that I can trace back. Like I can pass sessionToken if I can also pass requestId along with the request options passed during Parse.Cloud.run or ParseQuery.find or ParseQuery.findAll or ParseObject.save. I can just log the requestId from option to trace back source of origin.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the request flow through Parse.Cloud.run, Parse.Query.find/findAll, and Parse.Object.save, including how their request options are propagated. Done means a requestId can be supplied through these entry points, preserved across nested Cloud calls and queries, and logged in the Cloud function to identify the originating request.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
api, backend, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.