LOG-9190: Azure Monitor Logs Deprecation Alert#3237
LOG-9190: Azure Monitor Logs Deprecation Alert#3237Clee2691 wants to merge 1 commit intoopenshift:masterfrom
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@Clee2691: This pull request references LOG-9190 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.8.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/cherry-pick release-6.5 |
|
@Clee2691: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
| summary: |- | ||
| The Azure Monitor HTTP Data Collector API used by the azureMonitor output type will be retired on September 14, 2026. | ||
| After this date, log forwarding to Azure Monitor using this output type will stop functioning. | ||
| Administrators must migrate to the Azure Monitor Logs Ingestion output. |
There was a problem hiding this comment.
We should add some sort of RH link or information here regarding our new API and feature. @johnwilkins can you provide us with a link that will be used for this feature? Can we establish it before hand
It may even be better to remove the MS links from the alert and put them in our documentation so users are forced through our docs
There was a problem hiding this comment.
Our current Azure-specifc module is here: https://docs.redhat.com/en/documentation/red_hat_openshift_logging/6.4/html-single/configuring_logging/index#logging-forwarding-azure_configuring-log-forwarding
There was a problem hiding this comment.
@johnwilkins That specific doc will be obsolete after Sept 14th 2026 since forwarding logs to Azure with the Data Collector API will be retired. We should not add that link to this alert.
What Jeff was saying was that we need an updated doc about the AzureLogsIngestion sink which will need to be written with the feature in this PR #3223
There was a problem hiding this comment.
Thanks. Jeff left comments in another PR, so that doc has been updated accordingly. I've created a doc Jira to create new content for this.
| log_forwarder_output_type{output="azureMonitor"} > 0 | ||
| for: 1m | ||
| labels: | ||
| namespace: openshift-logging |
There was a problem hiding this comment.
CLFs are not restricted to this namespace
|
/approve |
|
@Clee2691 I'm not certain we can cherry-pick this to older releases without determining what are strategy will be. The verbiage may need change to identify the options we choose |
Yes you are right. I was overly zealous with the cherry picks. I'll close them when they come up. Is there a way to cancel cherry-picks? |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Clee2691, jcantrill The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
@Clee2691: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
5 participants
Description
Added alert for
AzureMonitorLogsdeprecation in favor ofAzureLogsIngestionoutput./cc @cahartma @vparfonov
/assign @jcantrill
Links