-
Notifications
You must be signed in to change notification settings - Fork 422
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_sqlserver/data_stream/transaction_log: Add support for fetch_from_all_databases
for mssql
#7500
Conversation
fetch_from_all_databases
for mssql
Let's add a documentation update section in the integration README describing the capability from the user perspective. |
Sure. |
2379d3a
to
3e80ac9
Compare
🌐 Coverage report
|
@lalit-satapathy I have updated the docs. |
bd2be34
to
3a9bb5e
Compare
packages/microsoft_sqlserver/data_stream/transaction_log/manifest.yml
Outdated
Show resolved
Hide resolved
Co-authored-by: aliabbas-elastic <124054599+aliabbas-elastic@users.noreply.github.com>
packages/microsoft_sqlserver/data_stream/transaction_log/agent/stream/stream.yml.hbs
Show resolved
Hide resolved
packages/microsoft_sqlserver/data_stream/transaction_log/manifest.yml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Package microsoft_sqlserver - 2.2.0 containing this change is available at https://epr.elastic.co/search?package=microsoft_sqlserver |
What does this PR do?
To make the Microsoft SQL Server integration setup easier, there's no simple way of getting the predefined queries run against all databases of a server to get the desired metrics. Currently, the only way to add, modify or remove databases (both system and user-defined) is to do them manually while configuring the integration. However, if there are a large number of databases on the server, this manual process can be tedious and time-consuming. To address this issue, there is an option to enable fetching the required
transaction_log
metrics from all databases on the server, including system and user-defined databases.This option is controlled by a boolean field called
fetch_from_all_databases
. By default, this feature is set tofalse
. To use it, simply set the field totrue
. This will allow the integration to automatically find and fetch metrics from all databases on the server, without requiring users to manually enter each individual database.Also, fixed some issues in the documentation, etc.
Checklist
changelog.yml
file.How to test this PR locally
hello_world
. Already four system databases are present:master
,model
,tempdb
andmsdb
User:
SA
Password: *****
Related issues
fetch_from_all_databases
in integrations for mssql #7499Screenshots