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

[Microsoft SQL Server]: Update documentation and grok error codes #12832

Open
tehbooom opened this issue Feb 18, 2025 · 0 comments
Open

[Microsoft SQL Server]: Update documentation and grok error codes #12832

tehbooom opened this issue Feb 18, 2025 · 0 comments

Comments

@tehbooom
Copy link
Member

Integration Name

Microsoft SQL Server [microsoft_sqlserver]

Dataset Name

log

Integration Version

2.9.4

Agent Version

8.17.2

OS Version and Architecture

Windows Server

User Goal

Update the documentation for the integration to highlight that you may need to set the encoding to utf-16le-bom

Also, grok error codes from messages to ECS mapping.
Example: Error: %{NUMBER:event.code}, Severity: %{NUMBER:event.severity}, State: %{NUMBER:microsoft_sqlserver.state}

Existing Features

We added the encoding variable but many users do not realize to set it. Also, we grab the message but do not do additional mappings on certain events that can be further mapped like error codes.

What did you see?

User ran into an issue related to not setting the encoding. Also, user wanted to get specific error codes from log message. Needed to add extra processor to @custom pipeline to get mappings using grok.

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant