Skip to content

Commit 4d4dda0

Browse files
authored
docs: fix mssql link (#615)
1 parent 31a068e commit 4d4dda0

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

distributions/nrdot-collector/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Note: See [general README](../README.md) for information that applies to all dis
1919
| ATP (Host Monitoring w/ process metrics) | `alpha` | N/A (new) | [Docs](https://docs.newrelic.com/docs/opentelemetry/nrdot/atp/overview/) |
2020
| Gateway Mode | `alpha` | N/A (new) | [See 'Gateway Mode' below](#gateway-mode) |
2121
| On-Host Integrations (OHI) | `alpha` | N/A (new) | [ECS](https://docs.newrelic.com/docs/opentelemetry/integrations/ecs-monitoring/overview/), [ElasticSearch](https://docs.newrelic.com/docs/opentelemetry/integrations/elasticsearch/elasticsearch-otel-integration-overview/), HAProxy (Coming Soon), [Kafka](https://docs.newrelic.com/docs/opentelemetry/integrations/kafka/overview/), [NGINX](https://docs.newrelic.com/docs/opentelemetry/integrations/nginx/nginx-otel-overview/), [RabbitMQ](https://docs.newrelic.com/docs/opentelemetry/integrations/rabbitmq/overview/), Redis (Coming Soon) |
22-
| Database Monitoring | `alpha` | N/A (new) | [SQL Server](https://docs.newrelic.com/docs/opentelemetry/database/otel-mssql/), [Oracle DB](https://docs.newrelic.com/docs/opentelemetry/database/otel-oracledb/) |
22+
| Database Monitoring | `alpha` | N/A (new) | [Microsoft SQL Server](https://docs.newrelic.com/docs/opentelemetry/database/mssql/introduction/), [Oracle DB](https://docs.newrelic.com/docs/opentelemetry/database/otel-oracledb/) |
2323

2424
Note: While it's technically possible to have a single collector serve multiple use cases at the same time, we generally do not recommend or support this pattern due to the operational complexity that comes with it (configuration, deployment, scaling, ...). Instead we recommend deploying one collector per use case and chain them as necessary. Please note that when we say 'one collector' we refer to a logical service, not a single instance, i.e. you should still employ common scaling practices to ensure your architecture is resilient.
2525

0 commit comments

Comments
 (0)