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

Prometheus retention customization #2968

Merged
merged 5 commits into from
Dec 16, 2020

Conversation

alexandre-allard
Copy link
Contributor

Component: salt, monitoring

Context: See #2953

Summary:

Acceptance criteria:


Closes: #2953

@alexandre-allard alexandre-allard requested a review from a team as a code owner December 9, 2020 12:02
@bert-e
Copy link
Contributor

bert-e commented Dec 9, 2020

Hello alexandre-allard-scality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Dec 9, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@@ -53429,7 +53429,7 @@ spec:
- --path.sysfs=/host/sys
- --path.rootfs=/host/root
- --web.listen-address=$(HOST_IP):9100
- --collector.diskstats.ignored-devices=^(ram|fd|(h|s|v)d[a-z]|nvme\\d+n\\d+p)\\d+$
- --collector.diskstats.ignored-devices=^(ram|fd)\\d+$
Copy link
Contributor Author

@alexandre-allard alexandre-allard Dec 9, 2020

Choose a reason for hiding this comment

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

Ignore this line as this comes from the Prometheus stack version bump (I forgot to re-render after having changed a parameter in charts/kube-prometheus-stack.yaml)

@alexandre-allard
Copy link
Contributor Author

Do we want a changelog entry for this kind of stuff ?

Copy link
Contributor

@gdemonet gdemonet left a comment

Choose a reason for hiding this comment

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

Mostly about user-facing information. This PR would also need a changelog entry, since we're adding a feature (didn't see your comment, sorry).

@bert-e
Copy link
Contributor

bert-e commented Dec 10, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

@alexandre-allard alexandre-allard force-pushed the improvement/2953-csc-prometheus-retention branch from 72bfc9b to 885cf28 Compare December 14, 2020 09:16
gdemonet
gdemonet previously approved these changes Dec 14, 2020
@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

We set these with special variables that will be
transformed into Jinja template by the chart
renderer script which will allow to customize
these fields at runtime through CSC mechanisms.

Refs: #2953
Since we changed retention time and size in the
charts, we need to regen it to apply changes.

```
./charts/render.py prometheus-operator \
  charts/kube-prometheus-stack.yaml \
  charts/kube-prometheus-stack/ \
  --namespace metalk8s-monitoring \
  --service-config grafana \
  metalk8s-grafana-config \
  metalk8s/addons/prometheus-operator/config/grafana.yaml \
  metalk8s-monitoring \
  --service-config prometheus \
  metalk8s-prometheus-config \
  metalk8s/addons/prometheus-operator/config/prometheus.yaml \
  metalk8s-monitoring \
  --service-config alertmanager \
  metalk8s-alertmanager-config \
  metalk8s/addons/prometheus-operator/config/alertmanager.yaml \
  metalk8s-monitoring \
  --service-config dex \
  metalk8s-dex-config \
  metalk8s/addons/dex/config/dex.yaml.j2 metalk8s-auth \
  --drop-prometheus-rules charts/drop-prometheus-rules.yaml \
  > salt/metalk8s/addons/prometheus-operator/deployed/chart.sls
```

Refs: #2953
Explain how to change retention time and activate
retention size using CSC ConfigMap.

Refs: #2953
@alexandre-allard alexandre-allard force-pushed the improvement/2953-csc-prometheus-retention branch from f7ab68b to 1675e58 Compare December 15, 2020 17:41
@alexandre-allard
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Dec 15, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Dec 16, 2020

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/2.7

The following branches will NOT be impacted:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Dec 16, 2020

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.7

The following branches have NOT changed:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6

Please check the status of the associated issue None.

Goodbye alexandre-allard-scality.

@bert-e bert-e merged commit 728094d into development/2.7 Dec 16, 2020
@bert-e bert-e deleted the improvement/2953-csc-prometheus-retention branch December 16, 2020 18:38
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.

Make Prometheus retention period configurable
3 participants