Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[receiver/mongodbatlas] Raw log message is not the actual raw log message for JSON logs #14178

Closed
BinaryFissionGames opened this issue Sep 16, 2022 · 1 comment · Fixed by #14388
Labels
bug Something isn't working needs triage New item requiring triage receiver/mongodbatlas

Comments

@BinaryFissionGames
Copy link
Contributor

What happened?

## Description
When receiving JSON logs, the mongodbatlas receiver decodes them, and throws away the original lines. It then "reconstructs" the original line by re-marshaling. This is inaccurate, and makes it more difficult to see if there was something missed in the model when it was marshalled (see #14177). 

The original log line is also present in two locations, as the body, and as an attribute (`raw_log`); It only really needs to be present in one place (the body).

## Steps to Reproduce
Scrape any 4.4+ mongodb cluster

## Expected Result
The original log line is present

## Actual Result
The original log line is not present, and any unknown fields are stripped.

Collector version

v0.60.0

Environment information

No response

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

@BinaryFissionGames BinaryFissionGames added bug Something isn't working needs triage New item requiring triage labels Sep 16, 2022
@github-actions
Copy link
Contributor

Pinging code owners: @zenmoto. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage New item requiring triage receiver/mongodbatlas
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants