[AZINTS] update event hub forwarder installation docs#29224
Conversation
Preview links (active after the
|
| <div class="alert alert-info"> | ||
| Starting April 30, 2025, Azure no longer supports Node.js 18. To ensure compatibility, first update your forwarder code, then upgrade to the latest Azure LTS version of Node.js (20). | ||
| If you previously deployed with an ARM template, you can update using the template with the same parameters. | ||
| Starting April 30, 2025, Azure no longer supports Node.js 18. To ensure compatibility, update using the Deploy to Azure (ARM) template with the same parameters. |
There was a problem hiding this comment.
since we only support deploying with the arm template, we should only recommend that now.
| {{< tabs >}} | ||
|
|
||
| {{% tab "Automated installation" %}} | ||
| {{% tab "Event Hub" %}} |
There was a problem hiding this comment.
removes multiple options for event hub and renames for clarity
| [2]: https://manage.windowsazure.com | ||
| [3]: /help/ | ||
| [4]: /integrations/azure/?tab=azurecliv20#optional-parameters | ||
| [5]: /logs/indexes/#set-daily-quota |
rtrieu
left a comment
rtrieu
left a comment
There was a problem hiding this comment.
Hi @ava-silver I have a few suggestions and then the PR should be good to go. Let me know if you have any questions!
| <div class="alert alert-info"> | ||
| Starting April 30, 2025, Azure no longer supports Node.js 18. To ensure compatibility, first update your forwarder code, then upgrade to the latest Azure LTS version of Node.js (20). | ||
| If you previously deployed with an ARM template, you can update using the template with the same parameters. | ||
| Starting April 30, 2025, Azure no longer supports Node.js 18. To ensure compatibility, update using the Deploy to Azure (ARM) template with the same parameters. |
There was a problem hiding this comment.
"Azure ARM" would be redundant here
| Starting April 30, 2025, Azure no longer supports Node.js 18. To ensure compatibility, update using the Deploy to Azure (ARM) template with the same parameters. | |
| Starting April 30, 2025, Azure no longer supports Node.js 18. To ensure compatibility, update using the Deploy to Azure Resource Manager (ARM) template with the same parameters. |
There was a problem hiding this comment.
I was thinking either Deploy to Azure template, like the button says, or the actual name of the template: Azure Resource Manager template would be good. I'll opt for just the latter for simplicity, since combining the two into Deploy to Azure Resource Manager feels more confusing potentially.
Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com>
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
dd-mergequeue
Bot
deleted the
ava.silver/azints/update-event-hub-forwarder-installation-docs
branch
dd-devflow
Bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
2 participants
What does this PR do? What is the motivation?
Updates the docs due to the migration of the event hub forwarder to nodejs model v4: DataDog/datadog-serverless-functions#934
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes