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
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions contributions/open-source/inigoaa-jmaragna/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Assignment Proposal

## Title

_--enable-feature: Consider removing no-default-scrape-port_

## Names and KTH ID

- Jacopo Maragna ([email protected])
- Íñigo Aréjula Aísa ([email protected])

## 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](https://github.com/prometheus/prometheus/issues/13959) 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.

Loading