fix external links that should contain .html

Author: colleenmcginnis

docs/reference/api-reference.md

@@ -62,7 +62,7 @@ except ValueError:
     client.capture_exception()
 ```
 
-* `exc_info`: A `(type, value, traceback)` tuple as returned by [`sys.exc_info()`](https://docs.python.org/3/library/sys.md#sys.exc_info). If not provided, it will be captured automatically.
+* `exc_info`: A `(type, value, traceback)` tuple as returned by [`sys.exc_info()`](https://docs.python.org/3/library/sys.html#sys.exc_info). If not provided, it will be captured automatically.
 * `date`: A `datetime.datetime` object representing the occurrence time of the error. If left empty, it defaults to `datetime.datetime.utcnow()`.
 * `context`: A dictionary with contextual information. This dictionary must follow the [Context](docs-content://solutions/observability/apps/elastic-apm-events-intake-api.md#apm-api-error) schema definition.
 * `custom`: A dictionary of custom data you want to attach to the event.
@@ -92,7 +92,7 @@ client.capture_message('Billing process succeeded.')
     ```
 
 * `stack`: If set to `True` (the default), a stacktrace from the call site will be captured.
-* `exc_info`: A `(type, value, traceback)` tuple as returned by [`sys.exc_info()`](https://docs.python.org/3/library/sys.md#sys.exc_info). If not provided, it will be captured automatically, if `capture_message()` was called in an `except` block.
+* `exc_info`: A `(type, value, traceback)` tuple as returned by [`sys.exc_info()`](https://docs.python.org/3/library/sys.html#sys.exc_info). If not provided, it will be captured automatically, if `capture_message()` was called in an `except` block.
 * `date`: A `datetime.datetime` object representing the occurrence time of the error. If left empty, it defaults to `datetime.datetime.utcnow()`.
 * `context`: A dictionary with contextual information. This dictionary must follow the [Context](docs-content://solutions/observability/apps/elastic-apm-events-intake-api.md#apm-api-error) schema definition.
 * `custom`: A dictionary of custom data you want to attach to the event.

docs/reference/configuration.md

@@ -699,7 +699,7 @@ This setting will be automatically rounded to 4 decimals of precision.
 | `ELASTIC_APM_INCLUDE_PATHS` | `INCLUDE_PATHS` | `[]` |
 | multiple values separated by commas, without spaces |  |  |
 
-A set of paths, optionally using shell globs (see [`fnmatch`](https://docs.python.org/3/library/fnmatch.md) for a description of the syntax). These are matched against the absolute filename of every frame, and if a pattern matches, the frame is considered to be an "in-app frame".
+A set of paths, optionally using shell globs (see [`fnmatch`](https://docs.python.org/3/library/fnmatch.html) for a description of the syntax). These are matched against the absolute filename of every frame, and if a pattern matches, the frame is considered to be an "in-app frame".
 
 `include_paths` **takes precedence** over `exclude_paths`.
 
@@ -711,7 +711,7 @@ A set of paths, optionally using shell globs (see [`fnmatch`](https://docs.pytho
 | `ELASTIC_APM_EXCLUDE_PATHS` | `EXCLUDE_PATHS` | Varies on Python version and implementation |
 | multiple values separated by commas, without spaces |  |  |
 
-A set of paths, optionally using shell globs (see [`fnmatch`](https://docs.python.org/3/library/fnmatch.md) for a description of the syntax). These are matched against the absolute filename of every frame, and if a pattern matches, the frame is considered to be a "library frame".
+A set of paths, optionally using shell globs (see [`fnmatch`](https://docs.python.org/3/library/fnmatch.html) for a description of the syntax). These are matched against the absolute filename of every frame, and if a pattern matches, the frame is considered to be a "library frame".
 
 `include_paths` **takes precedence** over `exclude_paths`.
 
@@ -1018,7 +1018,7 @@ This is useful if `HTTP_PROXY` / `HTTPS_PROXY` is set for other reasons than age
 
 ### `SSL_CERT_FILE` and `SSL_CERT_DIR` [config-ssl-cert-file]
 
-To tell the agent to use a different SSL certificate, you can use these environment variables. See also [OpenSSL docs](https://www.openssl.org/docs/manmaster/man7/openssl-env.md#SSL_CERT_DIR-SSL_CERT_FILE).
+To tell the agent to use a different SSL certificate, you can use these environment variables. See also [OpenSSL docs](https://www.openssl.org/docs/manmaster/man7/openssl-env.html#SSL_CERT_DIR-SSL_CERT_FILE).
 
 Please note that these variables may apply to other SSL/TLS communication in your service, not just related to the APM agent.
 

docs/reference/django-support.md

@@ -263,7 +263,7 @@ except MyModel.DoesNotExist:
 
 ## Celery integration [django-celery-integration]
 
-For a general guide on how to set up Django with Celery, head over to Celery’s [Django documentation](http://celery.readthedocs.org/en/latest/django/first-steps-with-django.md#django-first-steps).
+For a general guide on how to set up Django with Celery, head over to Celery’s [Django documentation](http://celery.readthedocs.org/en/latest/django/first-steps-with-django.html#django-first-steps).
 
 Elastic APM will automatically log errors from your celery tasks, record performance data and keep the trace.id when the task is launched from an already started Elastic transaction.
 

docs/reference/flask-support.md

@@ -24,7 +24,7 @@ For apm-server 6.2+, make sure you use version 2.0 or higher of `elastic-apm`.
 
 
 ::::{note}
-If you use Flask with uwsgi, make sure to [enable threads](http://uwsgi-docs.readthedocs.org/en/latest/Options.md#enable-threads).
+If you use Flask with uwsgi, make sure to [enable threads](http://uwsgi-docs.readthedocs.org/en/latest/Options.html#enable-threads).
 ::::
 
 

docs/reference/lambda-support.md

@@ -215,7 +215,7 @@ window.addEventListener("DOMContentLoaded", async () => {
                                 'COPY --from=python-agent /opt/python/ /opt/python/');
 });
 </script>
-Both the [{{apm-lambda-ext}}](apm-aws-lambda://reference/index.md) and the Python APM Agent are added to your Lambda function as [AWS Lambda Layers](https://docs.aws.amazon.com/lambda/latest/dg/invocation-layers.md). Therefore, you need to add the corresponding Layer ARNs (identifiers) to your Lambda function.
+Both the [{{apm-lambda-ext}}](apm-aws-lambda://reference/index.md) and the Python APM Agent are added to your Lambda function as [AWS Lambda Layers](https://docs.aws.amazon.com/lambda/latest/dg/invocation-layers.html). Therefore, you need to add the corresponding Layer ARNs (identifiers) to your Lambda function.
 
 :::::::{tab-set}
 

docs/reference/logs.md

@@ -35,7 +35,7 @@ The Agent provides integrations with both the default Python logging library, as
 
 #### `logging` [logging]
 
-We use [`logging.setLogRecordFactory()`](https://docs.python.org/3/library/logging.md#logging.setLogRecordFactory) to decorate the default LogRecordFactory to automatically add new attributes to each LogRecord object:
+We use [`logging.setLogRecordFactory()`](https://docs.python.org/3/library/logging.html#logging.setLogRecordFactory) to decorate the default LogRecordFactory to automatically add new attributes to each LogRecord object:
 
 * `elasticapm_transaction_id`
 * `elasticapm_trace_id`
@@ -48,7 +48,7 @@ You can disable this automatic behavior by using the [`disable_log_record_factor
 
 #### `structlog` [structlog]
 
-We provide a [processor](http://www.structlog.org/en/stable/processors.md) for [`structlog`](http://www.structlog.org/en/stable/) which will add three new keys to the event_dict of any processed event:
+We provide a [processor](http://www.structlog.org/en/stable/processors.html) for [`structlog`](http://www.structlog.org/en/stable/) which will add three new keys to the event_dict of any processed event:
 
 * `transaction.id`
 * `trace.id`
@@ -79,11 +79,11 @@ In order to correlate logs from your app with transactions captured by the Elast
 * `trace.id`
 * `span.id`
 
-If you’re using structured logging, either [with a custom solution](https://docs.python.org/3/howto/logging-cookbook.md#implementing-structured-logging) or with [structlog](http://www.structlog.org/en/stable/) (recommended), then this is fairly easy. Throw the [JSONRenderer](http://www.structlog.org/en/stable/api.md#structlog.processors.JSONRenderer) in, and use [Filebeat](https://www.elastic.co/blog/structured-logging-filebeat) to pull these logs into Elasticsearch.
+If you’re using structured logging, either [with a custom solution](https://docs.python.org/3/howto/logging-cookbook.html#implementing-structured-logging) or with [structlog](http://www.structlog.org/en/stable/) (recommended), then this is fairly easy. Throw the [JSONRenderer](http://www.structlog.org/en/stable/api.html#structlog.processors.JSONRenderer) in, and use [Filebeat](https://www.elastic.co/blog/structured-logging-filebeat) to pull these logs into Elasticsearch.
 
 Without structured logging the task gets a little trickier. Here we recommend first making sure your LogRecord objects have the elasticapm attributes (see [`logging`](#logging)), and then you’ll want to combine some specific formatting with a Grok pattern, either in Elasticsearch using [the grok processor](elasticsearch://reference/ingestion-tools/enrich-processor/grok-processor.md), or in [logstash with a plugin](logstash://reference/plugins-filters-grok.md).
 
-Say you have a [Formatter](https://docs.python.org/3/library/logging.md#logging.Formatter) that looks like this:
+Say you have a [Formatter](https://docs.python.org/3/library/logging.html#logging.Formatter) that looks like this:
 
 ```python
 import logging

docs/reference/opentelemetry-api-bridge.md

@@ -50,7 +50,7 @@ with tracer.start_as_current_span("test"):
 * `elasticapm_client`: an already instantiated Elastic APM client
 * `config`: a configuration dictionary, which will be used to instantiate a new Elastic APM client, e.g. `{"SERVER_URL": "https://example.org"}`. See [configuration](/reference/configuration.md) for more information.
 
-The `Tracer` object mirrors the upstream interface on the [OpenTelemetry `Tracer` object.](https://opentelemetry-python.readthedocs.io/en/latest/api/trace.md#opentelemetry.trace.Tracer)
+The `Tracer` object mirrors the upstream interface on the [OpenTelemetry `Tracer` object.](https://opentelemetry-python.readthedocs.io/en/latest/api/trace.html#opentelemetry.trace.Tracer)
 
 
 ## Caveats [opentelemetry-caveats]

docs/release-notes/breaking-changes.md

@@ -3,14 +3,14 @@ navigation_title: "Elastic APM Python Agent"
 ---
 
 # Elastic APM Python Agent breaking changes [elastic-apm-python-agent-breaking-changes]
-Before you upgrade, carefully review the Elastic APM RPython Agent breaking changes and take the necessary steps to mitigate any issues. 
+Before you upgrade, carefully review the Elastic APM RPython Agent breaking changes and take the necessary steps to mitigate any issues.
 
 To learn how to upgrade, check out <uprade docs>.
 
 % ## Next version [elastic-apm-python-agent-nextversion-breaking-changes]
 % **Release date:** Month day, year
 
-% ::::{dropdown} Title of breaking change 
+% ::::{dropdown} Title of breaking change
 % Description of the breaking change.
 % For more information, check [PR #](PR link).
 % **Impact**<br> Impact of the breaking change.
@@ -20,9 +20,9 @@ To learn how to upgrade, check out <uprade docs>.
 ## 6.0.0 [elastic-apm-python-agent-600-breaking-changes]
 **Release date:** February 1, 2021
 
-* Python 2.7 and 3.5 support has been deprecated. The Python agent now requires Python 3.6+. For more information, check [#1021](https://github.com/elastic/apm-agent-python/pull/1021). 
-* No longer collecting body for `elasticsearch-py` update and `delete_by_query`. For more information, check [#1013](https://github.com/elastic/apm-agent-python/pull/1013).  
-* Align `sanitize_field_names` config with the [cross-agent spec](https://github.com/elastic/apm/blob/3fa78e2a1eeea81c73c2e16e96dbf6b2e79f3c64/specs/agents/sanitization.md). If you are using a non-default `sanitize_field_names`, surrounding each of your entries with stars (e.g. `*secret*`) will retain the old behavior. For more information, check [#982](https://github.com/elastic/apm-agent-python/pull/982).  
-* Remove credit card sanitization for field values. This improves performance, and the security value of this check was dubious anyway. For more information, check [#982](https://github.com/elastic/apm-agent-python/pull/982).  
+* Python 2.7 and 3.5 support has been deprecated. The Python agent now requires Python 3.6+. For more information, check [#1021](https://github.com/elastic/apm-agent-python/pull/1021).
+* No longer collecting body for `elasticsearch-py` update and `delete_by_query`. For more information, check [#1013](https://github.com/elastic/apm-agent-python/pull/1013).
+* Align `sanitize_field_names` config with the [cross-agent spec](https://github.com/elastic/apm/blob/3fa78e2a1eeea81c73c2e16e96dbf6b2e79f3c64/specs/agents/sanitization.md). If you are using a non-default `sanitize_field_names`, surrounding each of your entries with stars (e.g. `*secret*`) will retain the old behavior. For more information, check [#982](https://github.com/elastic/apm-agent-python/pull/982).
+* Remove credit card sanitization for field values. This improves performance, and the security value of this check was dubious anyway. For more information, check [#982](https://github.com/elastic/apm-agent-python/pull/982).
 * Remove HTTP querystring sanitization. This improves performance, and is meant to standardize behavior across the agents, as defined in [#334](https://github.com/elastic/apm/pull/334). For more information, check [#982](https://github.com/elastic/apm-agent-python/pull/982).
-* Remove `elasticapm.tag()` (deprecated since 5.0.0). For more information, check [#1034](https://github.com/elastic/apm-agent-python/pull/1034). 
+* Remove `elasticapm.tag()` (deprecated since 5.0.0). For more information, check [#1034](https://github.com/elastic/apm-agent-python/pull/1034).