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.

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

Task 3: Open Source Proposal (inigoaa+jmaragna) #2465

Merged
merged 8 commits into from
Sep 22, 2024
Merged

Conversation

jackma-00
Copy link
Contributor

Assignment Proposal

Title

--enable-feature: Consider removing no-default-scrape-port

Names and KTH ID

Deadline

  • Task 3

Category

  • open-source

Description

Prometheus has different features available. However, some of them are not immediately available by default, but they can be enabled using flags. What the community is requesting is to enable some of these features by default. What we are proposing to do is to take this issue and resolve the problem.

Now, an outline of the various tasks we aim to solve:

  1. Understand the project architecture and source code.
  2. Set up the environment and run the project/tests.
  3. Tackle the problem itself:
    • By default, we want the no-default-scrape-port feature to be enabled.
    • Add the possibility to disable it on demand.
    • Update the documentation.

Relevance

Prometheus is crucial in DevOps for its ability to monitor (Week 7) and analyze system performance in real-time. It helps teams collect metrics, set alerts, and automate responses, ensuring system reliability and quick incident resolution. This enhances the core DevOps practices of continuous integration, deployment, and collaboration.

@jackma-00
Copy link
Contributor Author

@arejula27 and I are going to tackle this issue.
We wondered whether saying "Task 3" clearly means we want to deliver on Deadline 3 (October 15th).

@algomaster99 algomaster99 self-assigned this Sep 12, 2024
@algomaster99
Copy link
Collaborator

We wondered whether saying "Task 3" clearly means we want to deliver on Deadline 3 (October 15th).

This has clarified it. Thank you!

I wonder when should we merge this PR. After the contribution in prometheus has been merged or before, @javierron ?

@arejula27
Copy link
Contributor

Despite it not being merged yet, I guess it has been approved, so we can start working on it, right?

@algomaster99
Copy link
Collaborator

Hey! Please start working on it. I will wait for @javierron answer. 😅

@javierron
Copy link
Collaborator

@algomaster99 This PR is only for the proposal. When the group wants to submit the task, they should open another PR, which adds the links to the contributions to the README file.

@algomaster99 algomaster99 merged commit 3948b6b into KTH:2024 Sep 22, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants