Skip to content
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

Jump to bottom

Monitor query release date #16155

Merged
merged 2 commits into from
Jul 2, 2021
Merged

Monitor query release date #16155

merged 2 commits into from
Jul 2, 2021

Conversation

KarishmaGhiya
Copy link
Member

No description provided.

@ghost ghost added the Monitor Monitor, Monitor Ingestion, Monitor Query label Jul 2, 2021
@check-enforcer
Copy link

check-enforcer bot commented Jul 2, 2021

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run js - [service] - ci

@KarishmaGhiya
Copy link
Member Author

/azp run js - monitor - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

richardpark-msft
richardpark-msft approved these changes Jul 2, 2021
View reviewed changes
Copy link
Member

@richardpark-msft richardpark-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And with that - you are the primary maintainer :)

@KarishmaGhiya KarishmaGhiya merged commit 92c624a into main Jul 2, 2021
@KarishmaGhiya KarishmaGhiya deleted the monitor-query-release branch July 2, 2021 17:04
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-js that referenced this pull request Sep 27, 2021
@JunSun17 @norshtein @mslonli
CodeGen from PR 16155 in Azure/azure-rest-api-specs
3ed1442 
Improve desire count desc (Azure#16155)

* Adds base for updating Microsoft.ContainerService from version stable/2019-02-01 to version 2019-04-01

* Updates readme

* Updates API version in new specs and examples

* Adding windowsProfile and maxAgentPools property in the new 2019-04-01 api version (#5465)

* add maxAgentPools and windowsprofile properties

* fixing the sdk generation error

* adding load balancer sku property (#5556)

* Add support VMSS agent nodes with public IP. (#5748)

* Add identity property in managedCluster definition and add an example (#5709)

* Add identity property in managedCluster definition and add an example

* Fix typo

* Adds base for updating Microsoft.ContainerService from version stable/2020-02-01 to version 2020-03-01

* Updates readme

* Updates API version in new specs and examples

* added sku to managed cluster api (#8426)

* added sku to managed cluster api

* move managedcluster sku data model location

* improve count description

* remove useless file

Co-authored-by: Xiaofang Zhang <xizha@microsoft.com>
Co-authored-by: Jun Sun <33297523+JunSun17@users.noreply.github.com>
Co-authored-by: Tongyao Si <tosi@microsoft.com>
Co-authored-by: mslonli <lonli@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@richardpark-msft richardpark-msft richardpark-msft approved these changes

@maorleger maorleger Awaiting requested review from maorleger

Assignees
No one assigned
Labels
Monitor Monitor, Monitor Ingestion, Monitor Query
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@KarishmaGhiya @richardpark-msft