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

Convert postgresql.statement.query.id to number #24359

Merged
merged 1 commit into from
Mar 5, 2021

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Mar 4, 2021

What does this PR do?

Send postgresql.statement.query.id as number.

Why is it important?

Found while migrating to package. This field is a number, and defined as number in fields.yml.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc. It doesn't change anything for users.

Related issues

It is a number, and defined as long in fields.yml, so send is as number
in the document.
@jsoriano jsoriano added the Team:Integrations Label for the Integrations team label Mar 4, 2021
@jsoriano jsoriano self-assigned this Mar 4, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Mar 4, 2021
@jsoriano jsoriano added the review label Mar 4, 2021
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #24359 opened

  • Start Time: 2021-03-04T17:10:49.855+0000

  • Duration: 36 min 40 sec

  • Commit: 4b25d9d

Test stats 🧪

Test Results
Failed 0
Passed 8316
Skipped 2111
Total 10427

Trends 🧪

Image of Build Times

Image of Tests

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 8316
Skipped 2111
Total 10427

@jsoriano jsoriano merged commit 5f4a5e6 into elastic:master Mar 5, 2021
@jsoriano jsoriano deleted the postgresql-statement-int-queryid branch March 5, 2021 09:56
jsoriano added a commit to jsoriano/beats that referenced this pull request Mar 5, 2021
It is a number, and defined as long in fields.yml, so send is as number
in the document.

(cherry picked from commit 5f4a5e6)
jsoriano added a commit to jsoriano/beats that referenced this pull request Mar 5, 2021
It is a number, and defined as long in fields.yml, so send is as number
in the document.

(cherry picked from commit 5f4a5e6)
jsoriano added a commit that referenced this pull request Mar 5, 2021
It is a number, and defined as long in fields.yml, so send is as number
in the document.

(cherry picked from commit 5f4a5e6)
jsoriano added a commit that referenced this pull request Mar 5, 2021
It is a number, and defined as long in fields.yml, so send is as number
in the document.

(cherry picked from commit 5f4a5e6)
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…tic#24378)

It is a number, and defined as long in fields.yml, so send is as number
in the document.

(cherry picked from commit a5ca07c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants