Skip to content

docs: fix links #1375

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
vigneshshanmugam merged 3 commits into from
Jun 14, 2023
Merged

docs: fix links #1375

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fafc574
docs: fix links
bmorelli25 Jun 13, 2023
18fc22a
empty commit
bmorelli25 Jun 13, 2023
bb50fb8
Apply suggestions from code review
bmorelli25 Jun 13, 2023
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
6 changes: 3 additions & 3 deletions docs/agent-api.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ For each call, the properties of the context argument are shallow merged with th
The given `context` argument must be an object and can contain any property that can be JSON encoded.

TIP: Before using custom context, ensure you understand the different types of
{apm-guide-ref}/metadata.html[metadata] that are available.
{apm-guide-ref}/api-metadata.html[metadata] that are available.


[float]
Expand All @@ -80,13 +80,13 @@ TIP: Before using custom context, ensure you understand the different types of
apm.addLabels({ [name]: value })
----

Set labels on transactions and errors.
Set labels on transactions and errors.
Starting with APM Server 7.6+, the labels are added to spans as well.

Labels are key/value pairs that are indexed by Elasticsearch and therefore searchable (as opposed to data set via <<apm-set-custom-context,`apm.setCustomContext()`>>). You can set multiple labels.

TIP: Before using custom labels, ensure you understand the different types of
{apm-guide-ref}/metadata.html[metadata] that are available.
{apm-guide-ref}/api-metadata.html[metadata] that are available.

Arguments:

Expand Down
6 changes: 3 additions & 3 deletions docs/sourcemap.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,12 +10,12 @@ without losing the ability to quickly and easily debug your applications.

There are three steps required to enable, upload, and apply a source map to error stack traces.
An overview is listed below, and a complete walk-through is available in the
{apm-guide-ref}/sourcemaps.html[generate and upload a source map] guide.
{apm-guide-ref}/source-map-how-to.html[generate and upload a source map] guide.

1. Set the <<service-version,`serviceVersion`>> when initializing the RUM Agent.
2. {apm-guide-ref}/sourcemaps.html#sourcemap-rum-generate[Generate a source map]
2. {apm-guide-ref}/source-map-how-to.html#source-map-rum-generate[Generate a source map]
for your application with the `serviceVersion` from step one.
3. {apm-guide-ref}/sourcemaps.html#sourcemap-rum-upload[Enable and upload the source map file] to APM Server.
3. {apm-guide-ref}/source-map-how-to.html#source-map-rum-upload[Enable and upload the source map file] to APM Server.

// Don't link to this section
[[secret-token]]
Expand Down
2 changes: 1 addition & 1 deletion docs/transaction-api.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ it will also get tagged with the same labels.
Labels are key/value pairs that are indexed by Elasticsearch and therefore searchable (as opposed to data set via <<apm-set-custom-context,`apm.setCustomContext()`>>).

TIP: Before using custom labels, ensure you understand the different types of
{apm-guide-ref}/metadata.html[metadata] that are available.
{apm-guide-ref}/api-metadata.html[metadata] that are available.

Arguments:

Expand Down