Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

EVEREST-449 Set monitoring to false by default #164

Merged
merged 9 commits into from
Oct 9, 2023
Merged

Conversation

gen1us2k
Copy link
Contributor

@gen1us2k gen1us2k commented Oct 6, 2023

CHANGE DESCRIPTION

Problem:
EVEREST-449

Short explanation of the problem.

Related pull requests

  • [link]

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
Short explanation of the solution we are providing with this PR.

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?

Tests

  • Is an Integration test/test case added for the new feature/change?
  • Are unit tests added where appropriate?

@gen1us2k gen1us2k marked this pull request as ready for review October 6, 2023 13:10
@gen1us2k gen1us2k requested a review from a user October 6, 2023 13:10
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Code looks good.
Monitoring has been enabled by default by design though. It was requested by someone, not sure who though.

@gen1us2k gen1us2k merged commit 4ba98ad into main Oct 9, 2023
4 of 8 checks passed
@gen1us2k gen1us2k deleted the EVEREST-449 branch October 9, 2023 11:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants