Errors are reported in many lines
- Langage dominant
- Go
- Étoiles
- 8.8k
- Forks
- 383
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
## Prerequisites
* [X] I am running the latest version. (`up upgrade`)
* [X] I searched to see if the issue already exists.
* [ ] I inspected the verbose debug output with the `-v, --verbose` flag.
* [X] Are you an Up Pro subscriber?
## Description
We are using Up in 3 production systems; we are very happy... however, we ran into an issue or rather an _**inconvenience**_. We began using DataDog a couple of months ago. We are sending our cloudwatch logs to DataDog. One thing we noticed is that the error logs have multiple lines reported for one error.
For instance, on the patterns page in DataDog, I have an error that begins with "Patch rejected Error..." but you also see a bunch of error lines that begin with "at..." (see below).
You can see (Corresponding AWS Cloudwatch logs) that the "Patch rejected Error..." in one one line and the next line begins the stack trace " at t(/var/task/...".
Our question is, if there's a way to report errors as **one error entry** instead of reporting the error in **multiple lines** as we are seeing now.
## Steps to Reproduce
**DataDog - Error Patterns:**

**DataDog - Error List:**

**DataDog - Error Detail:**

**DataDog - Error in Context:**

**Corresponding AWS Cloudwatch logs:**

## Slack
Join us on Slack https://chat.apex.sh/
Guide de contribution
Ouvrir le guide de contribution
Évaluation
Cette issue n'a pas encore été évaluée.