[Reorganization: monitoring] monitoring reorganization batch 2 - #2571
Conversation
…istics and update the page
# Conflicts: # docs/server/administration/statistics.mdx
…aintenance/get-stats to /monitoring/statistics/client-api and updated its layout and content (v7.2 for C#, PHP, python, node.js, java)
… to /monitoring/logs/overview and update its layout and content
…logs-configuration to /monitoring/logs/configuration, update layout and content, leave a reference page
… from client-api/operations/server-wide/logs into /monitoring/logs/client-api, update layout and content, leave reference pages in the original locations
…pages to /monitoring/traffic-watch, update layout and content, add missing content (Studio view), update redirects
…ing/debug, split all routes into source-verified debug and production tables, added a redirect from the old troubleshooting path
…/debug, update the redirects file, improve page layout
…package, add redirects
…ng/logs/configuration
…elocated /monitoring/debug pages
|
@Lwiel note: this is batch 2 of the monitoring reorganization, including pages under: |
…r support` to the root
9641a3f to
5611672
Compare
Lwiel
left a comment
There was a problem hiding this comment.
We should remove these leftover snagx files I think
docs/monitoring/debug/assets/snagit/admin-logs-view.snagx
docs/monitoring/debug/assets/snagit/microsoft-logs.snagx
docs/monitoring/debug/assets/snagit/server-logs.snagx
docs/monitoring/debug/assets/snagit/settings-logs-on-disk.snagx
docs/monitoring/debug/assets/snagit/traffic-watch-logs.snagx
| @@ -0,0 +1,4 @@ | |||
| { | |||
| "position": 13, | |||
There was a problem hiding this comment.
/monitoring sidebar positions have gaps now
There was a problem hiding this comment.
- leftover snagits removed
- sidebar positions gapped on purpose in preparation for expected additional pages (in next PR)
| make sure this directory exists on each node; otherwise, cluster setup may fail. | ||
|
|
||
| Learn more about the RavenDB logging system in [Logging](../../../server/troubleshooting/logging). | ||
| Learn more about the RavenDB logging system in the [Overview](../../../monitoring/logs/overview) page. |
| | - | - | | ||
| | Integrations (SNMP, OpenTelemetry) | [Integrations: Configuration](integrations/configuration.mdx) | | ||
| | Logs | [Logs: Configuration](logs/configuration.mdx) | | ||
| | Task errors | [Task errors: Configuration](task-errors/configuration.mdx) | |
There was a problem hiding this comment.
Should we add traffic watch here?
| @@ -0,0 +1,461 @@ | |||
| --- | |||
| title: "Logging: Overview" | |||
There was a problem hiding this comment.
In other files we use Logs, let's make it consistent
There was a problem hiding this comment.
right
unified to "logging", seems more accurate since we're talking mainly about the mechanism and how to configure it.
| | `/admin/stats` | GET | The node's uptime, start time, last request time, last non-ClusterAdmin authorized request time, and the last request time per client certificate thumbprint. | | ||
| | `/build/version` | GET | The server's build number, product version, commit hash, and full version string. | | ||
| | `/cluster/topology` | GET | The current [cluster topology](../../server/clustering/rachis/cluster-topology.mdx): members, watchers, and their URLs. | | ||
| | `/databases/*/admin/configuration/settings` | GET, PUT | The database's configuration settings. `GET` reads the effective settings; `PUT` updates them from the request body.<br /><br />**Parameters (`GET` only):**<ul><li>`scope`: filter to a configuration entry scope (`ServerWideOnly`, `ServerWideOrPerDatabase`, or `ServerWideOrPerDatabaseOrPerIndex`) (optional)</li></ul> | |
There was a problem hiding this comment.
Maybe we should explain that * is the database name placeholder
| title: "Configuration: Logs Options" | ||
| sidebar_label: Logs Configuration | ||
| description: "Configure RavenDB server logging behavior including log levels, output file paths, retention policies, and audit log enablement settings." | ||
| sidebar_label: "Logs Configuration" |
There was a problem hiding this comment.
Maybe we should get rid of this and add a redirect?
There was a problem hiding this comment.
normally we relocate pages and update the redirects table, but in the specific case of /server/configuration we always leave a stub behind, pointing to the new configuration page in its new location, to keep the /server/configuration configurations list full and allow readers familiar with this entry point to always find what they are looking for. so at least for now let's leave this as is.
| [GetDetailedStatisticsOperation](../../../client-api/operations/maintenance/get-stats.mdx#get-detailed-database-stats) | ||
| [GetCollectionStatisticsOperation](../../../client-api/operations/maintenance/get-stats.mdx#get-collection-stats) | ||
| [GetDetailedCollectionStatisticsOperation](../../../client-api/operations/maintenance/get-stats.mdx#get-detailed-collection-stats) | ||
| [GetStatisticsOperation](../../../monitoring/statistics/client-api.mdx#get-database-stats) |
There was a problem hiding this comment.
Should be #get-database-statistics anchor I think, same for other languages but Java. In Java we have #get-database-stats
Issue link
RDoc-3995
RDoc-3996
RDoc-3997
RDoc-3998
RDoc-3999
RDoc-4000
RDoc-4001
RDoc-4002
RDoc-4003
RDoc-4004
Additional description
move monitoring pages to /monitoring and update them as needed (statistics, logging, logging configuration page, traffic watch, traffic watch configuration page, debug endpoints,
collect info for support, debug package folder,get statistics APIpage)Type of change
/templatesor readme)Changes in docs URLs
/scripts/redirects.jsonfile, setDocuments MovedPR label)Changes in UX/UI