# Merge commit error tracking

**URL:** <https://community.dynatrace.com/t/merge-commit-error-tracking/38710>\
**Category:** Open Q&A\
**Tags:** integrations, problems-classic\
**Created:** [March 6, 2023, 2:25pm UTC](https://community.dynatrace.com/t/merge-commit-error-tracking/38710 "2023-03-06T14:25:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tasjordao](https://avatars.discourse-cdn.com/v4/letter/t/b5ac83/32.png) [@tasjordao](https://community.dynatrace.com/u/tasjordao)\
**Post date:** [March 6, 2023, 2:25pm UTC](https://community.dynatrace.com/t/merge-commit-error-tracking/38710/1 "2023-03-06T14:25:30Z")

</div>

Hi Guys,

Is that possibly getting the merge commit that has started a specific error?

**Context:**

I have a front-end application configured by oneAgent. Once I get an error, I want to know the last merge commit before the error has started. This way, I might get the pull request which has started the issue.

---

<div class="post-metadata">

**Author:** ![tasjordao](https://avatars.discourse-cdn.com/v4/letter/t/b5ac83/32.png) [@tasjordao](https://community.dynatrace.com/u/tasjordao)\
**Post date:** [March 8, 2023, 8:34pm UTC](https://community.dynatrace.com/t/merge-commit-error-tracking/38710/2 "2023-03-08T20:34:04Z")

</div>

> I must inform you that in order to track the associated pull request of the merge commit, you do not need to directly monitor the commit in Dynatrace. When an application problem arises in Dynatrace, it will include information such as precise time of the error, root cause analysis, affected components and much more. Once you receive the error, you could check the time and match with the time of the commit performed to detect the commit in question. Problem detection is automatically done when installing OneAgent

Support reply