microsoft_sqlserver/data_stream/transaction_log: Add support for fetch_from_all_databases for mssql#7500
Merged
shmsr merged 7 commits intoelastic:mainfrom Sep 21, 2023
Merged
Conversation
fetch_from_all_databases for mssql
Contributor
|
Let's add a documentation update section in the integration README describing the capability from the user perspective. |
Member
Author
Sure. |
2379d3a to
3e80ac9
Compare
🌐 Coverage report
|
Member
Author
@lalit-satapathy I have updated the docs. |
bd2be34 to
3a9bb5e
Compare
muthu-mps
reviewed
Aug 30, 2023
packages/microsoft_sqlserver/data_stream/transaction_log/manifest.yml
Outdated
Show resolved
Hide resolved
Contributor
Member
Author
ali786XI
reviewed
Aug 31, 2023
Co-authored-by: aliabbas-elastic <124054599+aliabbas-elastic@users.noreply.github.com>
Member
Author
shmsr
commented
Sep 8, 2023
ritalwar
reviewed
Sep 8, 2023
packages/microsoft_sqlserver/data_stream/transaction_log/agent/stream/stream.yml.hbs
Show resolved
Hide resolved
ritalwar
reviewed
Sep 8, 2023
packages/microsoft_sqlserver/data_stream/transaction_log/manifest.yml
Outdated
Show resolved
Hide resolved
ritalwar
approved these changes
Sep 21, 2023
|
Package microsoft_sqlserver - 2.2.0 containing this change is available at https://epr.elastic.co/search?package=microsoft_sqlserver |
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


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_logmetrics 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.ymlfile.How to test this PR locally
hello_world. Already four system databases are present:master,model,tempdbandmsdbUser:
SAPassword: *****
Related issues
fetch_from_all_databasesin integrations for mssql #7499Screenshots