Fix examples to use API key authentication #924
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes a few small touch-ups to indicate that API key authentication is required on serverless, and generally recommended over basic auth. For the changes to the "debugging" example, I tested an agent policy and the resulting output from the
elastic-agent inspect
command to make sure that the updated formatting is correct.I've also updated the API key generation to note that the UI path is slightly different in a serverless project.
The examples in the nginx monitoring tutorials were fixed separately.
Closes: #693