automatic import of python-prom2teamsopeneuler20.03

3 files changed, 1019 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..2dfa602 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/prom2teams-4.2.0.tar.gz
diff --git a/python-prom2teams.spec b/python-prom2teams.spec
new file mode 100644
index 0000000..9fc17fc
--- /dev/null
+++ b/python-prom2teams.spec
@@ -0,0 +1,1017 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-prom2teams
+Version:	4.2.0
+Release:	1
+Summary:	Project that redirects Prometheus Alert Manager notifications to Microsoft Teams
+License:	Apache license 2.0
+URL:		https://github.com/idealista/prom2teams
+Source0:	https://mirrors.aliyun.com/pypi/web/packages/cb/1a/3aa84689f75019fca82f84618c3781bb487213a03f0afa6afab5227f3453/prom2teams-4.2.0.tar.gz
+BuildArch:	noarch
+
+
+%description
+<div align="center">
+  <img alt="logo" src="https://raw.githubusercontent.com/idealista/prom2teams/master/logo.gif">
+
+  [![Build Status](https://travis-ci.com/idealista/prom2teams.svg?branch=master)](https://travis-ci.com/idealista/prom2teams)
+  [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=idealista_prom2teams&metric=alert_status)](https://sonarcloud.io/dashboard?id=idealista_prom2teams)
+  [![Docker Build Status](https://img.shields.io/docker/build/idealista/prom2teams.svg)](https://hub.docker.com/r/idealista/prom2teams/) 
+  [![Docker Hub Pulls](https://img.shields.io/docker/pulls/idealista/prom2teams.svg)](https://hub.docker.com/r/idealista/prom2teams/)
+</div>
+
+# prom2teams: Prometheus Alertmanager/Microsoft Teams integration
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/idealista/prom2teams/master/assets/example.png" alt="Alert example" style="width: 600px;"/>
+</p>
+
+**prom2teams** is a service built with Python that receives alert notifications from a previously configured [Prometheus Alertmanager](https://github.com/prometheus/alertmanager) instance and forwards it to [Microsoft Teams](https://teams.microsoft.com/) using defined connectors.
+
+It presents grouping of alerts, labels/annotations exclusion and a Teams' alert retry policy among its key features.
+
+
+- [Getting Started](#getting-started)
+	- [Prerequisities](#prerequisites)
+	- [Installing](#installing)
+- [Usage](#usage)
+  - [Docker Image](#docker-image)
+  - [Helm Chart](#helm-chart)
+  - [Config file](#config-file)
+	- [Configuring Prometheus](#configuring-prometheus)
+	- [Templating](#templating)
+- [Documentation](#documentation)
+  - [Swagger UI](#swagger-ui)
+- [Testing](#testing)
+- [Built With](#built-with)
+- [Versioning](#versioning)
+- [Authors](#authors)
+- [License](#license)
+- [Contributing](#contributing)
+
+## Getting Started
+
+### Prerequisites
+
+The application has been tested with _Prometheus 2.2.1_, _Python 3.8.0_ and _pip 9.0.1_.
+
+Newer versions of _Prometheus/Python/pip_ should work but could also present issues.
+
+### Installing
+
+prom2teams is present on [PyPI](https://pypi.python.org/pypi/prom2teams), so could be installed using pip3:
+
+```bash
+$ pip3 install prom2teams
+```
+
+**Note:** Works since v1.1.1
+
+## Usage
+
+**Important:** Config path must be provided with at least one Microsoft Teams Connector. Check the options to know how you can supply it.
+
+```bash
+# To start the server (enable metrics, config file path , group alerts by, log file path, log level and Jinja2 template path are optional arguments):
+$ prom2teams [--enablemetrics] [--configpath <config file path>] [--groupalertsby ("name"|"description"|"instance"|"severity"|"summary")] [--logfilepath <log file path>] [--loglevel (DEBUG|INFO|WARNING|ERROR|CRITICAL)] [--templatepath <Jinja2 template file path>]
+
+# To show the help message:
+$ prom2teams --help
+```
+Other options to start the service are:
+
+```bash
+export APP_CONFIG_FILE=<config file path>
+$ prom2teams
+```
+**Note:** Grouping alerts works since v2.2.1
+
+### Docker image
+
+Every new Prom2teams release, a new Docker image is built in our [Dockerhub](https://hub.docker.com/r/idealista/prom2teams). We strongly recommend you to use the images with the version tag, though it will be possible to use them without it.
+
+There are two things you need to bear in mind when creating a Prom2teams container:
+
+- The connector URL must be passed as the environment variable `PROM2TEAMS_CONNECTOR`
+- In case you want to group alerts, you need to pass the field as the environment variable `PROM2TEAMS_GROUP_ALERTS_BY`
+- You need to map container's Prom2teams port to one on your host.
+
+So a sample Docker run command would be:
+
+```bash
+$ docker run -it -d -e PROM2TEAMS_GROUP_ALERTS_BY=FIELD_YOU_WANT_TO_GROUP_BY -e PROM2TEAMS_CONNECTOR="CONNECTOR_URL" -p 8089:8089 idealista/prom2teams:VERSION
+```
+
+#### Provide custom config file
+
+If you prefer to use your own config file, you just need to provide it as a Docker volume to the container and map it to `/opt/prom2teams/config.ini`. Sample:
+
+```bash
+$ docker run -it -d -v pathToTheLocalConfigFile:/opt/prom2teams/config.ini -p 8089:8089 idealista/prom2teams:VERSION
+```
+
+### Helm chart
+
+#### Installing the Chart
+
+To install the chart with the release name `my-release` run:
+
+```bash
+$ helm install --name my-release /location/of/prom2teams_ROOT/helm
+```
+
+After a few seconds, Prom2Teams should be running.
+
+> **Tip**: List all releases using `helm list`, a release is a name used to track a specific deployment
+
+#### Uninstalling the Chart
+
+To uninstall/delete the `my-release` deployment:
+
+##### Helm 2
+
+```bash
+$ helm delete my-release
+```
+> **Tip**: Use helm delete --purge my-release to completely remove the release from Helm internal storage
+
+The command removes all the Kubernetes components associated with the chart and deletes the release.
+
+##### Helm 3
+
+```bash
+$ helm uninstall my-release
+```
+
+The command removes all the Kubernetes components associated with the chart and deletes the release.
+
+#### Configuration
+
+The following table lists the configurable parameters of the Prom2teams chart and their default values.
+
+| Parameter                                       | Description                                                                                                        | Default
+| ---                                             | ---                                                                                                                | ---
+| `image.repository`                              | The image repository to pull from                                                                                  | `idealista/prom2teams`
+| `image.tag`                                     | The image tag to pull                                                                                              | `<empty>`
+| `image.pullPolicy`                              | The image pull policy                                                                                              | `IfNotPresent`
+| `resources.requests.cpu`                        | CPU requested for being run in a node                                                                              | `100m`
+| `resources.requests.memory`                     | Memory requested for being run in a node                                                                           | `128Mi`
+| `resources.limits.cpu`                          | CPU limit                                                                                                          | `200m`
+| `resources.limits.memory`                       | Memory limit                                                                                                       | `200Mi`
+| `service.type`                                  | Service Map (NodePort/ClusterIP)                                                                                   | `ClusterIP`
+| `service.port`                                  | Service Port                                                                                                       | `8089`
+| `prom2teams.host`                               | IP to bind to                                                                                                      | `0.0.0.0`
+| `prom2teams.port`                               | Port to bind to                                                                                                    | `8089`
+| `prom2teams.connector`                          | Connector URL                                                                                                      | `<empty>`
+| `prom2teams.connectors`                         | A map where the keys are the connector names and the values are the connector webhook urls                         | `{}`
+| `prom2teams.group_alerts_by`                    | Group_alerts_by field                                                                                              | `<empty>`
+| `prom2teams.loglevel`                           | Loglevel                                                                                                           | `INFO`
+| `prom2teams.templatepath`                       | Custom Template path (files/teams.j2)                                                                              | `/opt/prom2teams/helmconfig/teams.j2`
+| `prom2teams.config`                             | Config (specific to Helm)                                                                                          | `/opt/prom2teams/helmconfig/config.ini`
+| `prom2teams.extraEnv`                           | Dictionary of arbitrary additional environment variables for deployment (eg. `HTTP_PROXY`)                         | `<empty>`
+
+### Production
+
+For production environments you should prefer using a WSGI server. [uWSGI](https://uwsgi-docs.readthedocs.io/en/latest/)
+dependency is installed for an easy usage. Some considerations must be taken to use it:
+
+The binary `prom2teams_uwsgi` launches the app using the uwsgi server. Due to some incompatibilities with [wheel](https://github.com/pypa/wheel)
+you must install `prom2teams` using `sudo pip install --no-binary :all: prom2teams` (https://github.com/pypa/wheel/issues/92)
+
+```bash
+$ prom2teams_uwsgi <path to uwsgi ini config>
+```
+
+And `uwsgi` would look like:
+
+```
+[uwsgi]
+master = true
+processes = 5
+#socket = 0.0.0.0:8001
+#protocol = http
+socket = /tmp/prom2teams.sock
+chmod-socket = 777
+vacuum = true
+env = APP_ENVIRONMENT=pro
+env = APP_CONFIG_FILE=/etc/default/prom2teams.ini
+```
+
+Consider not provide `chdir` property neither `module` property.
+
+Also you can set the `module` file, by doing a symbolic link: `sudo mkdir -p /usr/local/etc/prom2teams/ && sudo ln -sf /usr/local/lib/python3.7/dist-packages/usr/local/etc/prom2teams/wsgi.py /usr/local/etc/prom2teams/wsgi.py` (check your dist-packages folder)
+
+Another approach is to provide yourself the `module` file [module example](bin/wsgi.py) and the `bin` uwsgi call [uwsgi example](bin/prom2teams_uwsgi)
+
+**Note:** default log level is DEBUG. Messages are redirected to stdout. To enable file log, set the env APP_ENVIRONMENT=(pro|pre)
+
+
+### Config file
+
+The config file is an [INI file](https://docs.python.org/3/library/configparser.html#supported-ini-file-structure) and should have the structure described below:
+
+```ini
+[Microsoft Teams]
+# At least one connector is required here
+Connector: <webhook url>
+AnotherConnector: <webhook url>   
+...
+
+[HTTP Server]
+Host: <host ip> # default: localhost
+Port: <host port> # default: 8089
+
+[Log]
+Level: <loglevel (DEBUG|INFO|WARNING|ERROR|CRITICAL)> # default: DEBUG
+Path: <log file path>  # default: /var/log/prom2teams/prom2teams.log
+
+[Template]
+Path: <Jinja2 template path> # default: app resources default template (./prom2teams/resources/templates/teams.j2)
+
+[Group Alerts]
+Field: <Field to group alerts by> # alerts won't be grouped by default
+
+[Labels]
+Excluded: <Comma separated list of labels to ignore>
+
+[Annotations]
+Excluded: <Comma separated list of annotations to ignore>
+
+[Teams Client]
+RequestTimeout: <Configures the request timeout> # defaults to 30 secs
+RetryEnable: <Enables teams client retry policy> # defaults to false
+RetryWaitTime: <Wait time between retries> # default: 60 secs
+MaxPayload: <Teams client payload limit in bytes> # default: 24KB
+```
+
+**Note:** Grouping alerts works since v2.2.0
+
+### Configuring Prometheus
+
+The [webhook receiver](https://prometheus.io/docs/alerting/configuration/#<webhook_config>) in Prometheus allows configuring a prom2teams server.
+
+The url is formed by the host and port defined in the previous step.
+
+**Note:** In order to keep compatibility with previous versions, v2.0 keep attending the default connector ("Connector") in the endpoint 0.0.0.0:8089. This will be removed in future versions.   
+
+```
+// The prom2teams endpoint to send HTTP POST requests to.
+url: 0.0.0.0:8089/v2/<Connector1>
+```
+
+### Prom2teams Prometheus metrics
+
+Prom2teams uses Flask and, to have the service monitored, we use @rycus66's [Prometheus Flask Exporter](https://github.com/rycus86/prometheus_flask_exporter). This will enable an endpoint in `/metrics` where you could find interesting metrics to monitor such as number of responses with a certain status. To enable this endpoint, just either:
+
+- Use the `--enablemetrics` or `-m` flag when launching prom2teams.
+- Set the environment variable `PROM2TEAMS_PROMETHEUS_METRICS=true`.
+
+### Templating
+
+prom2teams provides a [default template](prom2teams/resources/templates/teams.j2) built with [Jinja2](http://jinja.pocoo.org/docs/2.10/) to render messages in Microsoft Teams. This template could be overrided using the 'templatepath' argument ('--templatepath <Jinja2 template file path>') during the application start.
+
+Some fields are considered mandatory when received from Alert Manager.
+If such a field is not included a default value of 'unknown' is assigned.
+
+All non-mandatory labels not in excluded list are injected in `extra_labels` key. All non-mandatory annotations not in excluded list are injected in `extra_annotations` key.
+
+Alertmanager fingerprints are available in the `fingerprint` key.  Fingerprints
+are supported by Alertmanager 0.19.0 or greater.
+
+## Documentation
+### Swagger UI
+
+Accessing to `<Host>:<Port>` (e.g. `localhost:8089`) in a web browser shows the API v1 documentation.
+
+<img src="https://raw.githubusercontent.com/idealista/prom2teams/master/assets/swagger_v1.png" alt="Swagger UI" style="width: 600px;"/>
+
+Accessing to `<Host>:<Port>/v2` (e.g. `localhost:8089/v2`) in a web browser shows the API v2 documentation.
+
+<img src="https://raw.githubusercontent.com/idealista/prom2teams/master/assets/swagger_v2.png" alt="Swagger UI" style="width: 600px;"/>
+
+## Testing
+
+To run the test suite you should type the following:
+
+```bash
+// After cloning prom2teams :)
+$ pip install -r requirements.txt
+$ python3 -m unittest discover tests
+$ cd tests/e2e
+$ ./test.sh
+```
+
+## Built With
+![Python 3.8.0](https://img.shields.io/badge/Python-3.8.0-green.svg)
+![pip 9.0.1](https://img.shields.io/badge/pip-9.0.1-green.svg)
+
+## Versioning
+
+For the versions available, see the [tags on this repository](https://github.com/idealista/prom2teams/tags).
+
+Additionaly you can see what change in each version in the [CHANGELOG.md](CHANGELOG.md) file.
+
+## Authors
+
+* **Idealista** - *Work with* - [idealista](https://github.com/idealista)
+
+See also the list of [contributors](https://github.com/idealista/prom2teams/contributors) who participated in this project.
+
+## License
+
+![Apache 2.0 License](https://img.shields.io/hexpm/l/plug.svg)
+
+This project is licensed under the [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) license - see the [LICENSE](LICENSE) file for details.
+
+## Contributing
+
+Please read [CONTRIBUTING.md](.github/CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
+
+
+%package -n python3-prom2teams
+Summary:	Project that redirects Prometheus Alert Manager notifications to Microsoft Teams
+Provides:	python-prom2teams
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-prom2teams
+<div align="center">
+  <img alt="logo" src="https://raw.githubusercontent.com/idealista/prom2teams/master/logo.gif">
+
+  [![Build Status](https://travis-ci.com/idealista/prom2teams.svg?branch=master)](https://travis-ci.com/idealista/prom2teams)
+  [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=idealista_prom2teams&metric=alert_status)](https://sonarcloud.io/dashboard?id=idealista_prom2teams)
+  [![Docker Build Status](https://img.shields.io/docker/build/idealista/prom2teams.svg)](https://hub.docker.com/r/idealista/prom2teams/) 
+  [![Docker Hub Pulls](https://img.shields.io/docker/pulls/idealista/prom2teams.svg)](https://hub.docker.com/r/idealista/prom2teams/)
+</div>
+
+# prom2teams: Prometheus Alertmanager/Microsoft Teams integration
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/idealista/prom2teams/master/assets/example.png" alt="Alert example" style="width: 600px;"/>
+</p>
+
+**prom2teams** is a service built with Python that receives alert notifications from a previously configured [Prometheus Alertmanager](https://github.com/prometheus/alertmanager) instance and forwards it to [Microsoft Teams](https://teams.microsoft.com/) using defined connectors.
+
+It presents grouping of alerts, labels/annotations exclusion and a Teams' alert retry policy among its key features.
+
+
+- [Getting Started](#getting-started)
+	- [Prerequisities](#prerequisites)
+	- [Installing](#installing)
+- [Usage](#usage)
+  - [Docker Image](#docker-image)
+  - [Helm Chart](#helm-chart)
+  - [Config file](#config-file)
+	- [Configuring Prometheus](#configuring-prometheus)
+	- [Templating](#templating)
+- [Documentation](#documentation)
+  - [Swagger UI](#swagger-ui)
+- [Testing](#testing)
+- [Built With](#built-with)
+- [Versioning](#versioning)
+- [Authors](#authors)
+- [License](#license)
+- [Contributing](#contributing)
+
+## Getting Started
+
+### Prerequisites
+
+The application has been tested with _Prometheus 2.2.1_, _Python 3.8.0_ and _pip 9.0.1_.
+
+Newer versions of _Prometheus/Python/pip_ should work but could also present issues.
+
+### Installing
+
+prom2teams is present on [PyPI](https://pypi.python.org/pypi/prom2teams), so could be installed using pip3:
+
+```bash
+$ pip3 install prom2teams
+```
+
+**Note:** Works since v1.1.1
+
+## Usage
+
+**Important:** Config path must be provided with at least one Microsoft Teams Connector. Check the options to know how you can supply it.
+
+```bash
+# To start the server (enable metrics, config file path , group alerts by, log file path, log level and Jinja2 template path are optional arguments):
+$ prom2teams [--enablemetrics] [--configpath <config file path>] [--groupalertsby ("name"|"description"|"instance"|"severity"|"summary")] [--logfilepath <log file path>] [--loglevel (DEBUG|INFO|WARNING|ERROR|CRITICAL)] [--templatepath <Jinja2 template file path>]
+
+# To show the help message:
+$ prom2teams --help
+```
+Other options to start the service are:
+
+```bash
+export APP_CONFIG_FILE=<config file path>
+$ prom2teams
+```
+**Note:** Grouping alerts works since v2.2.1
+
+### Docker image
+
+Every new Prom2teams release, a new Docker image is built in our [Dockerhub](https://hub.docker.com/r/idealista/prom2teams). We strongly recommend you to use the images with the version tag, though it will be possible to use them without it.
+
+There are two things you need to bear in mind when creating a Prom2teams container:
+
+- The connector URL must be passed as the environment variable `PROM2TEAMS_CONNECTOR`
+- In case you want to group alerts, you need to pass the field as the environment variable `PROM2TEAMS_GROUP_ALERTS_BY`
+- You need to map container's Prom2teams port to one on your host.
+
+So a sample Docker run command would be:
+
+```bash
+$ docker run -it -d -e PROM2TEAMS_GROUP_ALERTS_BY=FIELD_YOU_WANT_TO_GROUP_BY -e PROM2TEAMS_CONNECTOR="CONNECTOR_URL" -p 8089:8089 idealista/prom2teams:VERSION
+```
+
+#### Provide custom config file
+
+If you prefer to use your own config file, you just need to provide it as a Docker volume to the container and map it to `/opt/prom2teams/config.ini`. Sample:
+
+```bash
+$ docker run -it -d -v pathToTheLocalConfigFile:/opt/prom2teams/config.ini -p 8089:8089 idealista/prom2teams:VERSION
+```
+
+### Helm chart
+
+#### Installing the Chart
+
+To install the chart with the release name `my-release` run:
+
+```bash
+$ helm install --name my-release /location/of/prom2teams_ROOT/helm
+```
+
+After a few seconds, Prom2Teams should be running.
+
+> **Tip**: List all releases using `helm list`, a release is a name used to track a specific deployment
+
+#### Uninstalling the Chart
+
+To uninstall/delete the `my-release` deployment:
+
+##### Helm 2
+
+```bash
+$ helm delete my-release
+```
+> **Tip**: Use helm delete --purge my-release to completely remove the release from Helm internal storage
+
+The command removes all the Kubernetes components associated with the chart and deletes the release.
+
+##### Helm 3
+
+```bash
+$ helm uninstall my-release
+```
+
+The command removes all the Kubernetes components associated with the chart and deletes the release.
+
+#### Configuration
+
+The following table lists the configurable parameters of the Prom2teams chart and their default values.
+
+| Parameter                                       | Description                                                                                                        | Default
+| ---                                             | ---                                                                                                                | ---
+| `image.repository`                              | The image repository to pull from                                                                                  | `idealista/prom2teams`
+| `image.tag`                                     | The image tag to pull                                                                                              | `<empty>`
+| `image.pullPolicy`                              | The image pull policy                                                                                              | `IfNotPresent`
+| `resources.requests.cpu`                        | CPU requested for being run in a node                                                                              | `100m`
+| `resources.requests.memory`                     | Memory requested for being run in a node                                                                           | `128Mi`
+| `resources.limits.cpu`                          | CPU limit                                                                                                          | `200m`
+| `resources.limits.memory`                       | Memory limit                                                                                                       | `200Mi`
+| `service.type`                                  | Service Map (NodePort/ClusterIP)                                                                                   | `ClusterIP`
+| `service.port`                                  | Service Port                                                                                                       | `8089`
+| `prom2teams.host`                               | IP to bind to                                                                                                      | `0.0.0.0`
+| `prom2teams.port`                               | Port to bind to                                                                                                    | `8089`
+| `prom2teams.connector`                          | Connector URL                                                                                                      | `<empty>`
+| `prom2teams.connectors`                         | A map where the keys are the connector names and the values are the connector webhook urls                         | `{}`
+| `prom2teams.group_alerts_by`                    | Group_alerts_by field                                                                                              | `<empty>`
+| `prom2teams.loglevel`                           | Loglevel                                                                                                           | `INFO`
+| `prom2teams.templatepath`                       | Custom Template path (files/teams.j2)                                                                              | `/opt/prom2teams/helmconfig/teams.j2`
+| `prom2teams.config`                             | Config (specific to Helm)                                                                                          | `/opt/prom2teams/helmconfig/config.ini`
+| `prom2teams.extraEnv`                           | Dictionary of arbitrary additional environment variables for deployment (eg. `HTTP_PROXY`)                         | `<empty>`
+
+### Production
+
+For production environments you should prefer using a WSGI server. [uWSGI](https://uwsgi-docs.readthedocs.io/en/latest/)
+dependency is installed for an easy usage. Some considerations must be taken to use it:
+
+The binary `prom2teams_uwsgi` launches the app using the uwsgi server. Due to some incompatibilities with [wheel](https://github.com/pypa/wheel)
+you must install `prom2teams` using `sudo pip install --no-binary :all: prom2teams` (https://github.com/pypa/wheel/issues/92)
+
+```bash
+$ prom2teams_uwsgi <path to uwsgi ini config>
+```
+
+And `uwsgi` would look like:
+
+```
+[uwsgi]
+master = true
+processes = 5
+#socket = 0.0.0.0:8001
+#protocol = http
+socket = /tmp/prom2teams.sock
+chmod-socket = 777
+vacuum = true
+env = APP_ENVIRONMENT=pro
+env = APP_CONFIG_FILE=/etc/default/prom2teams.ini
+```
+
+Consider not provide `chdir` property neither `module` property.
+
+Also you can set the `module` file, by doing a symbolic link: `sudo mkdir -p /usr/local/etc/prom2teams/ && sudo ln -sf /usr/local/lib/python3.7/dist-packages/usr/local/etc/prom2teams/wsgi.py /usr/local/etc/prom2teams/wsgi.py` (check your dist-packages folder)
+
+Another approach is to provide yourself the `module` file [module example](bin/wsgi.py) and the `bin` uwsgi call [uwsgi example](bin/prom2teams_uwsgi)
+
+**Note:** default log level is DEBUG. Messages are redirected to stdout. To enable file log, set the env APP_ENVIRONMENT=(pro|pre)
+
+
+### Config file
+
+The config file is an [INI file](https://docs.python.org/3/library/configparser.html#supported-ini-file-structure) and should have the structure described below:
+
+```ini
+[Microsoft Teams]
+# At least one connector is required here
+Connector: <webhook url>
+AnotherConnector: <webhook url>   
+...
+
+[HTTP Server]
+Host: <host ip> # default: localhost
+Port: <host port> # default: 8089
+
+[Log]
+Level: <loglevel (DEBUG|INFO|WARNING|ERROR|CRITICAL)> # default: DEBUG
+Path: <log file path>  # default: /var/log/prom2teams/prom2teams.log
+
+[Template]
+Path: <Jinja2 template path> # default: app resources default template (./prom2teams/resources/templates/teams.j2)
+
+[Group Alerts]
+Field: <Field to group alerts by> # alerts won't be grouped by default
+
+[Labels]
+Excluded: <Comma separated list of labels to ignore>
+
+[Annotations]
+Excluded: <Comma separated list of annotations to ignore>
+
+[Teams Client]
+RequestTimeout: <Configures the request timeout> # defaults to 30 secs
+RetryEnable: <Enables teams client retry policy> # defaults to false
+RetryWaitTime: <Wait time between retries> # default: 60 secs
+MaxPayload: <Teams client payload limit in bytes> # default: 24KB
+```
+
+**Note:** Grouping alerts works since v2.2.0
+
+### Configuring Prometheus
+
+The [webhook receiver](https://prometheus.io/docs/alerting/configuration/#<webhook_config>) in Prometheus allows configuring a prom2teams server.
+
+The url is formed by the host and port defined in the previous step.
+
+**Note:** In order to keep compatibility with previous versions, v2.0 keep attending the default connector ("Connector") in the endpoint 0.0.0.0:8089. This will be removed in future versions.   
+
+```
+// The prom2teams endpoint to send HTTP POST requests to.
+url: 0.0.0.0:8089/v2/<Connector1>
+```
+
+### Prom2teams Prometheus metrics
+
+Prom2teams uses Flask and, to have the service monitored, we use @rycus66's [Prometheus Flask Exporter](https://github.com/rycus86/prometheus_flask_exporter). This will enable an endpoint in `/metrics` where you could find interesting metrics to monitor such as number of responses with a certain status. To enable this endpoint, just either:
+
+- Use the `--enablemetrics` or `-m` flag when launching prom2teams.
+- Set the environment variable `PROM2TEAMS_PROMETHEUS_METRICS=true`.
+
+### Templating
+
+prom2teams provides a [default template](prom2teams/resources/templates/teams.j2) built with [Jinja2](http://jinja.pocoo.org/docs/2.10/) to render messages in Microsoft Teams. This template could be overrided using the 'templatepath' argument ('--templatepath <Jinja2 template file path>') during the application start.
+
+Some fields are considered mandatory when received from Alert Manager.
+If such a field is not included a default value of 'unknown' is assigned.
+
+All non-mandatory labels not in excluded list are injected in `extra_labels` key. All non-mandatory annotations not in excluded list are injected in `extra_annotations` key.
+
+Alertmanager fingerprints are available in the `fingerprint` key.  Fingerprints
+are supported by Alertmanager 0.19.0 or greater.
+
+## Documentation
+### Swagger UI
+
+Accessing to `<Host>:<Port>` (e.g. `localhost:8089`) in a web browser shows the API v1 documentation.
+
+<img src="https://raw.githubusercontent.com/idealista/prom2teams/master/assets/swagger_v1.png" alt="Swagger UI" style="width: 600px;"/>
+
+Accessing to `<Host>:<Port>/v2` (e.g. `localhost:8089/v2`) in a web browser shows the API v2 documentation.
+
+<img src="https://raw.githubusercontent.com/idealista/prom2teams/master/assets/swagger_v2.png" alt="Swagger UI" style="width: 600px;"/>
+
+## Testing
+
+To run the test suite you should type the following:
+
+```bash
+// After cloning prom2teams :)
+$ pip install -r requirements.txt
+$ python3 -m unittest discover tests
+$ cd tests/e2e
+$ ./test.sh
+```
+
+## Built With
+![Python 3.8.0](https://img.shields.io/badge/Python-3.8.0-green.svg)
+![pip 9.0.1](https://img.shields.io/badge/pip-9.0.1-green.svg)
+
+## Versioning
+
+For the versions available, see the [tags on this repository](https://github.com/idealista/prom2teams/tags).
+
+Additionaly you can see what change in each version in the [CHANGELOG.md](CHANGELOG.md) file.
+
+## Authors
+
+* **Idealista** - *Work with* - [idealista](https://github.com/idealista)
+
+See also the list of [contributors](https://github.com/idealista/prom2teams/contributors) who participated in this project.
+
+## License
+
+![Apache 2.0 License](https://img.shields.io/hexpm/l/plug.svg)
+
+This project is licensed under the [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) license - see the [LICENSE](LICENSE) file for details.
+
+## Contributing
+
+Please read [CONTRIBUTING.md](.github/CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
+
+
+%package help
+Summary:	Development documents and examples for prom2teams
+Provides:	python3-prom2teams-doc
+%description help
+<div align="center">
+  <img alt="logo" src="https://raw.githubusercontent.com/idealista/prom2teams/master/logo.gif">
+
+  [![Build Status](https://travis-ci.com/idealista/prom2teams.svg?branch=master)](https://travis-ci.com/idealista/prom2teams)
+  [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=idealista_prom2teams&metric=alert_status)](https://sonarcloud.io/dashboard?id=idealista_prom2teams)
+  [![Docker Build Status](https://img.shields.io/docker/build/idealista/prom2teams.svg)](https://hub.docker.com/r/idealista/prom2teams/) 
+  [![Docker Hub Pulls](https://img.shields.io/docker/pulls/idealista/prom2teams.svg)](https://hub.docker.com/r/idealista/prom2teams/)
+</div>
+
+# prom2teams: Prometheus Alertmanager/Microsoft Teams integration
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/idealista/prom2teams/master/assets/example.png" alt="Alert example" style="width: 600px;"/>
+</p>
+
+**prom2teams** is a service built with Python that receives alert notifications from a previously configured [Prometheus Alertmanager](https://github.com/prometheus/alertmanager) instance and forwards it to [Microsoft Teams](https://teams.microsoft.com/) using defined connectors.
+
+It presents grouping of alerts, labels/annotations exclusion and a Teams' alert retry policy among its key features.
+
+
+- [Getting Started](#getting-started)
+	- [Prerequisities](#prerequisites)
+	- [Installing](#installing)
+- [Usage](#usage)
+  - [Docker Image](#docker-image)
+  - [Helm Chart](#helm-chart)
+  - [Config file](#config-file)
+	- [Configuring Prometheus](#configuring-prometheus)
+	- [Templating](#templating)
+- [Documentation](#documentation)
+  - [Swagger UI](#swagger-ui)
+- [Testing](#testing)
+- [Built With](#built-with)
+- [Versioning](#versioning)
+- [Authors](#authors)
+- [License](#license)
+- [Contributing](#contributing)
+
+## Getting Started
+
+### Prerequisites
+
+The application has been tested with _Prometheus 2.2.1_, _Python 3.8.0_ and _pip 9.0.1_.
+
+Newer versions of _Prometheus/Python/pip_ should work but could also present issues.
+
+### Installing
+
+prom2teams is present on [PyPI](https://pypi.python.org/pypi/prom2teams), so could be installed using pip3:
+
+```bash
+$ pip3 install prom2teams
+```
+
+**Note:** Works since v1.1.1
+
+## Usage
+
+**Important:** Config path must be provided with at least one Microsoft Teams Connector. Check the options to know how you can supply it.
+
+```bash
+# To start the server (enable metrics, config file path , group alerts by, log file path, log level and Jinja2 template path are optional arguments):
+$ prom2teams [--enablemetrics] [--configpath <config file path>] [--groupalertsby ("name"|"description"|"instance"|"severity"|"summary")] [--logfilepath <log file path>] [--loglevel (DEBUG|INFO|WARNING|ERROR|CRITICAL)] [--templatepath <Jinja2 template file path>]
+
+# To show the help message:
+$ prom2teams --help
+```
+Other options to start the service are:
+
+```bash
+export APP_CONFIG_FILE=<config file path>
+$ prom2teams
+```
+**Note:** Grouping alerts works since v2.2.1
+
+### Docker image
+
+Every new Prom2teams release, a new Docker image is built in our [Dockerhub](https://hub.docker.com/r/idealista/prom2teams). We strongly recommend you to use the images with the version tag, though it will be possible to use them without it.
+
+There are two things you need to bear in mind when creating a Prom2teams container:
+
+- The connector URL must be passed as the environment variable `PROM2TEAMS_CONNECTOR`
+- In case you want to group alerts, you need to pass the field as the environment variable `PROM2TEAMS_GROUP_ALERTS_BY`
+- You need to map container's Prom2teams port to one on your host.
+
+So a sample Docker run command would be:
+
+```bash
+$ docker run -it -d -e PROM2TEAMS_GROUP_ALERTS_BY=FIELD_YOU_WANT_TO_GROUP_BY -e PROM2TEAMS_CONNECTOR="CONNECTOR_URL" -p 8089:8089 idealista/prom2teams:VERSION
+```
+
+#### Provide custom config file
+
+If you prefer to use your own config file, you just need to provide it as a Docker volume to the container and map it to `/opt/prom2teams/config.ini`. Sample:
+
+```bash
+$ docker run -it -d -v pathToTheLocalConfigFile:/opt/prom2teams/config.ini -p 8089:8089 idealista/prom2teams:VERSION
+```
+
+### Helm chart
+
+#### Installing the Chart
+
+To install the chart with the release name `my-release` run:
+
+```bash
+$ helm install --name my-release /location/of/prom2teams_ROOT/helm
+```
+
+After a few seconds, Prom2Teams should be running.
+
+> **Tip**: List all releases using `helm list`, a release is a name used to track a specific deployment
+
+#### Uninstalling the Chart
+
+To uninstall/delete the `my-release` deployment:
+
+##### Helm 2
+
+```bash
+$ helm delete my-release
+```
+> **Tip**: Use helm delete --purge my-release to completely remove the release from Helm internal storage
+
+The command removes all the Kubernetes components associated with the chart and deletes the release.
+
+##### Helm 3
+
+```bash
+$ helm uninstall my-release
+```
+
+The command removes all the Kubernetes components associated with the chart and deletes the release.
+
+#### Configuration
+
+The following table lists the configurable parameters of the Prom2teams chart and their default values.
+
+| Parameter                                       | Description                                                                                                        | Default
+| ---                                             | ---                                                                                                                | ---
+| `image.repository`                              | The image repository to pull from                                                                                  | `idealista/prom2teams`
+| `image.tag`                                     | The image tag to pull                                                                                              | `<empty>`
+| `image.pullPolicy`                              | The image pull policy                                                                                              | `IfNotPresent`
+| `resources.requests.cpu`                        | CPU requested for being run in a node                                                                              | `100m`
+| `resources.requests.memory`                     | Memory requested for being run in a node                                                                           | `128Mi`
+| `resources.limits.cpu`                          | CPU limit                                                                                                          | `200m`
+| `resources.limits.memory`                       | Memory limit                                                                                                       | `200Mi`
+| `service.type`                                  | Service Map (NodePort/ClusterIP)                                                                                   | `ClusterIP`
+| `service.port`                                  | Service Port                                                                                                       | `8089`
+| `prom2teams.host`                               | IP to bind to                                                                                                      | `0.0.0.0`
+| `prom2teams.port`                               | Port to bind to                                                                                                    | `8089`
+| `prom2teams.connector`                          | Connector URL                                                                                                      | `<empty>`
+| `prom2teams.connectors`                         | A map where the keys are the connector names and the values are the connector webhook urls                         | `{}`
+| `prom2teams.group_alerts_by`                    | Group_alerts_by field                                                                                              | `<empty>`
+| `prom2teams.loglevel`                           | Loglevel                                                                                                           | `INFO`
+| `prom2teams.templatepath`                       | Custom Template path (files/teams.j2)                                                                              | `/opt/prom2teams/helmconfig/teams.j2`
+| `prom2teams.config`                             | Config (specific to Helm)                                                                                          | `/opt/prom2teams/helmconfig/config.ini`
+| `prom2teams.extraEnv`                           | Dictionary of arbitrary additional environment variables for deployment (eg. `HTTP_PROXY`)                         | `<empty>`
+
+### Production
+
+For production environments you should prefer using a WSGI server. [uWSGI](https://uwsgi-docs.readthedocs.io/en/latest/)
+dependency is installed for an easy usage. Some considerations must be taken to use it:
+
+The binary `prom2teams_uwsgi` launches the app using the uwsgi server. Due to some incompatibilities with [wheel](https://github.com/pypa/wheel)
+you must install `prom2teams` using `sudo pip install --no-binary :all: prom2teams` (https://github.com/pypa/wheel/issues/92)
+
+```bash
+$ prom2teams_uwsgi <path to uwsgi ini config>
+```
+
+And `uwsgi` would look like:
+
+```
+[uwsgi]
+master = true
+processes = 5
+#socket = 0.0.0.0:8001
+#protocol = http
+socket = /tmp/prom2teams.sock
+chmod-socket = 777
+vacuum = true
+env = APP_ENVIRONMENT=pro
+env = APP_CONFIG_FILE=/etc/default/prom2teams.ini
+```
+
+Consider not provide `chdir` property neither `module` property.
+
+Also you can set the `module` file, by doing a symbolic link: `sudo mkdir -p /usr/local/etc/prom2teams/ && sudo ln -sf /usr/local/lib/python3.7/dist-packages/usr/local/etc/prom2teams/wsgi.py /usr/local/etc/prom2teams/wsgi.py` (check your dist-packages folder)
+
+Another approach is to provide yourself the `module` file [module example](bin/wsgi.py) and the `bin` uwsgi call [uwsgi example](bin/prom2teams_uwsgi)
+
+**Note:** default log level is DEBUG. Messages are redirected to stdout. To enable file log, set the env APP_ENVIRONMENT=(pro|pre)
+
+
+### Config file
+
+The config file is an [INI file](https://docs.python.org/3/library/configparser.html#supported-ini-file-structure) and should have the structure described below:
+
+```ini
+[Microsoft Teams]
+# At least one connector is required here
+Connector: <webhook url>
+AnotherConnector: <webhook url>   
+...
+
+[HTTP Server]
+Host: <host ip> # default: localhost
+Port: <host port> # default: 8089
+
+[Log]
+Level: <loglevel (DEBUG|INFO|WARNING|ERROR|CRITICAL)> # default: DEBUG
+Path: <log file path>  # default: /var/log/prom2teams/prom2teams.log
+
+[Template]
+Path: <Jinja2 template path> # default: app resources default template (./prom2teams/resources/templates/teams.j2)
+
+[Group Alerts]
+Field: <Field to group alerts by> # alerts won't be grouped by default
+
+[Labels]
+Excluded: <Comma separated list of labels to ignore>
+
+[Annotations]
+Excluded: <Comma separated list of annotations to ignore>
+
+[Teams Client]
+RequestTimeout: <Configures the request timeout> # defaults to 30 secs
+RetryEnable: <Enables teams client retry policy> # defaults to false
+RetryWaitTime: <Wait time between retries> # default: 60 secs
+MaxPayload: <Teams client payload limit in bytes> # default: 24KB
+```
+
+**Note:** Grouping alerts works since v2.2.0
+
+### Configuring Prometheus
+
+The [webhook receiver](https://prometheus.io/docs/alerting/configuration/#<webhook_config>) in Prometheus allows configuring a prom2teams server.
+
+The url is formed by the host and port defined in the previous step.
+
+**Note:** In order to keep compatibility with previous versions, v2.0 keep attending the default connector ("Connector") in the endpoint 0.0.0.0:8089. This will be removed in future versions.   
+
+```
+// The prom2teams endpoint to send HTTP POST requests to.
+url: 0.0.0.0:8089/v2/<Connector1>
+```
+
+### Prom2teams Prometheus metrics
+
+Prom2teams uses Flask and, to have the service monitored, we use @rycus66's [Prometheus Flask Exporter](https://github.com/rycus86/prometheus_flask_exporter). This will enable an endpoint in `/metrics` where you could find interesting metrics to monitor such as number of responses with a certain status. To enable this endpoint, just either:
+
+- Use the `--enablemetrics` or `-m` flag when launching prom2teams.
+- Set the environment variable `PROM2TEAMS_PROMETHEUS_METRICS=true`.
+
+### Templating
+
+prom2teams provides a [default template](prom2teams/resources/templates/teams.j2) built with [Jinja2](http://jinja.pocoo.org/docs/2.10/) to render messages in Microsoft Teams. This template could be overrided using the 'templatepath' argument ('--templatepath <Jinja2 template file path>') during the application start.
+
+Some fields are considered mandatory when received from Alert Manager.
+If such a field is not included a default value of 'unknown' is assigned.
+
+All non-mandatory labels not in excluded list are injected in `extra_labels` key. All non-mandatory annotations not in excluded list are injected in `extra_annotations` key.
+
+Alertmanager fingerprints are available in the `fingerprint` key.  Fingerprints
+are supported by Alertmanager 0.19.0 or greater.
+
+## Documentation
+### Swagger UI
+
+Accessing to `<Host>:<Port>` (e.g. `localhost:8089`) in a web browser shows the API v1 documentation.
+
+<img src="https://raw.githubusercontent.com/idealista/prom2teams/master/assets/swagger_v1.png" alt="Swagger UI" style="width: 600px;"/>
+
+Accessing to `<Host>:<Port>/v2` (e.g. `localhost:8089/v2`) in a web browser shows the API v2 documentation.
+
+<img src="https://raw.githubusercontent.com/idealista/prom2teams/master/assets/swagger_v2.png" alt="Swagger UI" style="width: 600px;"/>
+
+## Testing
+
+To run the test suite you should type the following:
+
+```bash
+// After cloning prom2teams :)
+$ pip install -r requirements.txt
+$ python3 -m unittest discover tests
+$ cd tests/e2e
+$ ./test.sh
+```
+
+## Built With
+![Python 3.8.0](https://img.shields.io/badge/Python-3.8.0-green.svg)
+![pip 9.0.1](https://img.shields.io/badge/pip-9.0.1-green.svg)
+
+## Versioning
+
+For the versions available, see the [tags on this repository](https://github.com/idealista/prom2teams/tags).
+
+Additionaly you can see what change in each version in the [CHANGELOG.md](CHANGELOG.md) file.
+
+## Authors
+
+* **Idealista** - *Work with* - [idealista](https://github.com/idealista)
+
+See also the list of [contributors](https://github.com/idealista/prom2teams/contributors) who participated in this project.
+
+## License
+
+![Apache 2.0 License](https://img.shields.io/hexpm/l/plug.svg)
+
+This project is licensed under the [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) license - see the [LICENSE](LICENSE) file for details.
+
+## Contributing
+
+Please read [CONTRIBUTING.md](.github/CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
+
+
+%prep
+%autosetup -n prom2teams-4.2.0
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+	find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+	find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+	find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+	find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+	find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-prom2teams -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 4.2.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..511341b
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+8cd0a989e376daf73b44ea51ddf8326a  prom2teams-4.2.0.tar.gz