Skip to content

[docs] Fix image paths for docs-assembler #8498

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 16, 2025
+5 −15
Merged

[docs] Fix image paths for docs-assembler #8498

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions docs/reference/getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,15 +35,11 @@ var client = new ElasticsearchClient("<CLOUD_ID>", new ApiKey("<API_KEY>"));

Your Elasticsearch endpoint can be found on the **My deployment** page of your deployment:

:::{image} images/es-endpoint.jpg
:alt: Finding Elasticsearch endpoint
:::
![Finding Elasticsearch endpoint](images/es-endpoint.jpg)

You can generate an API key on the **Management** page under Security.

:::{image} images/create-api-key.png
:alt: Create API key
:::
![Create API key](images/create-api-key.png)

For other connection options, refer to the [*Connecting*](/reference/connecting.md) section.

Expand Down
12 changes: 3 additions & 9 deletions docs/reference/troubleshoot/logging-with-fiddler.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,7 @@ A web debugging proxy such as [Fiddler](http://www.telerik.com/fiddler) is a use

To capture traffic against a remote cluster is as simple as launching Fiddler! You may want to also filter traffic to only show requests to the remote cluster by using the filters tab

:::{image} ../images/elasticsearch-client-net-api-capture-requests-remotehost.png
:alt: Capturing requests to a remote host
:::
![Capturing requests to a remote host](../images/elasticsearch-client-net-api-capture-requests-remotehost.png)


## Capturing traffic to a local cluster [_capturing_traffic_to_a_local_cluster]
Expand All @@ -37,14 +35,10 @@ var client = new ElasticClient(connectionSettings);

With Fiddler running, the requests and responses will now be captured and can be inspected in the Inspectors tab

:::{image} ../images/elasticsearch-client-net-api-inspect-requests.png
:alt: Inspecting requests and responses
:::
![Inspecting requests and responses](../images/elasticsearch-client-net-api-inspect-requests.png)

As before, you may also want to filter traffic to only show requests to `ipv4.fiddler` on the port on which you are running Elasticsearch.

:::{image} ../images/elasticsearch-client-net-api-capture-requests-localhost.png
:alt: Capturing requests to localhost
:::
![Capturing requests to localhost](../images/elasticsearch-client-net-api-capture-requests-localhost.png)


Loading