Skip to content

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

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 15, 2025
Merged

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

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
4 changes: 1 addition & 3 deletions docs/reference/azure-functions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,9 +70,7 @@ ELASTIC_APM_SECRET_TOKEN: <your APM secret token from the prerequisites step>

For example:

:::{image} images/azure-functions-configuration.png
:alt: Configuring the APM Agent in the Azure Portal
:::
![Configuring the APM Agent in the Azure Portal](images/azure-functions-configuration.png)

For local testing via `func start`, you can set these environment variables in your terminal, or in the "local.settings.json" file. See the [agent configuration guide](/reference/configuration.md) for full details on supported configuration variables.

Expand Down
5 changes: 1 addition & 4 deletions docs/reference/nextjs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,10 +96,7 @@ while true; do sleep 1; curl -i http://localhost:3000/api/hello; done

Visit your Kibana APM app and, after a few seconds, you should see a service entry for your Next.js app. The service name will be pulled from the "name" field in "package.json". It can be overriden with [`serviceName`](/reference/configuration.md#service-name). Here is an example:

:::{image} images/nextjs-my-app-screenshot.png
:alt: Kibana APM app showing Next.js my-app
:::

![Kibana APM app showing Next.js my-app](images/nextjs-my-app-screenshot.png)

## Limitations and future work [nextjs-limitations]

Expand Down
4 changes: 1 addition & 3 deletions docs/reference/supported-technologies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,7 @@ The Elastic APM Node.js Agent automatically instruments various APIs in Node.js

Support for the Elastic APM Node.js agent follows the [support schedule of Node.js itself](https://nodejs.org/en/about/releases/) to the end-of-life period of each version after its maintenance term. Versions of Node.js past their end-of-life date are not supported.

:::{image} images/node_release_schedule.svg
:alt: Node.js release schedule
:::
![Node.js release schedule](images/node_release_schedule.svg)

APM agent 4.x releases work with Node.js versions 14.17.0 and later. APM agent 3.x maintenance releases work with Node.js versions 8.6 and later. We will only break support for older Node.js versions with a major version release of the APM agent.

Expand Down
Loading