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
[docs] Update MSSQL README to use documentation guidelines #8240
Conversation
🌐 Coverage report
|
changes: | ||
- description: Update README to use documentation guidelines | ||
type: enhancement | ||
link: TBD |
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.
link: TBD | |
link: https://github.com/elastic/integrations/pull/8240 |
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.
Looks good!
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.
Thank you for improving the documentation 🎉
Package microsoft_sqlserver - 2.3.1 containing this change is available at https://epr.elastic.co/search?package=microsoft_sqlserver |
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.
Should we also keep security team informed on document changes to the audit data-streams (if any?)
|
||
Auditing an instance of the SQL Server Database Engine or an individual database involves tracking and logging events that occur on the Database Engine. | ||
For more information on SQL Server auditing, refer to [SQL Server Audit](https://docs.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-database-engine?view=sql-server-ver15). |
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.
The line in the beginning paragraph, somewhat looks mis-placed, since it is referring the audit data-stream primarily. It may wrongly infer referring to all data streams.
|
||
Microsoft SQL Server has a feature that allows running multiple databases on the same host (or clustered hosts) with separate settings. Establish a named instance connection by using the instance name along with the hostname (e.g. `host/instance_name` or `host:named_instance_port`) to collect metrics. Details of the host configuration are provided below. | ||
Find more details in [Logs](#logs-reference). |
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.
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.
Fix:
s/logs-reference/logs
|
||
## Host Configuration | ||
<!-- Additional set up instructions --> |
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.
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.
Ideally, this should have worked. On GitHub it does. Maybe for the website, we are using a different markdown renderer that does not support this?
|
||
Microsoft SQL Server has a feature that allows running multiple databases on the same host (or clustered hosts) with separate settings. Establish a named instance connection by using the instance name along with the hostname (e.g. `host/instance_name` or `host:named_instance_port`) to collect metrics. Details of the host configuration are provided below. | ||
Find more details in [Logs](#logs-reference). |
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.
Fix:
s/logs-reference/logs
* `performance` metrics gather the list of performance objects available on that server. Each server will have a different list of performance objects depending on the installed software. | ||
* `transaction_log` metrics collect all usage stats and the total space usage. | ||
|
||
Find more details in [Metrics](#metrics-reference). |
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.
Fix:
s/metrics-reference/metrics
|
||
## Host Configuration | ||
<!-- Additional set up instructions --> |
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.
Ideally, this should have worked. On GitHub it does. Maybe for the website, we are using a different markdown renderer that does not support this?
* address post-merge feedback in #8240 * add link to this pr
Proposed commit message
Update README to use documentation guidelines
Checklist
I have verified that all data streams collect metrics or logs.changelog.yml
file.I have verified that Kibana version constraints are current according to guidelines.Author's Checklist
How to test this PR locally
View the README.
Related issues
Related to elastic/observability-docs#3270