Bosch rexroth ActiveShuttle System Manual page 50

50
$ nano docker-compose.yml
[...]
prometheus:
[...]
volumes:
- /path-within-server/prometheus/
prometheus.yml:/etc/prometheus/
prometheus.yml
- /path-within-server/prometheus/
server:/etc/prometheus
[...]
[...]
16 Prometheus configuration
Prometheus2teams
1. Copy the folder msteams and its content from the sample configuration folder to the deployment folder.
2. Make sure that the folder has read permissions for other users:
3. Create a notification channel.
◊ For further information, see Microsoft documentation
channel-in-teams-fda0b75e-5b90-4fb8-8857-7e102b014525)
4. Configure the incoming webhook in MS Teams.
◊ For further information, see Microsoft documentation
platform/webhooks-and-connectors/how-to/add-incoming-webhook)
RA91390962 AB-V1.3.3, en
ILS, ActiveShuttle | Server deployment
8. Create a folder called ams-instance within the
prometheus/server/ path
9. Copy the content of the sample configuration to the
folder ams-instance-compose.
10. Open the ams.rules file from the directory
prometheus/server/ams-instance/
11. Edit
container_label_com_docker_compose_
based on the deployment configuration.
project
Notice!
To find the respective names run the command
docker ps | grep etcd
In this case xyz is the name of the project).
12. Replace all project names for all the microservices
within the file as described in step 11.
13. Change the deployment path in the
file.
compose.yml
The content of this folder is volume-mounted
within the alert manager Docker-Container.
sudo chmod -R 777 msteams.
(https://support.microsoft.com/en-us/office/create-a-
(https://docs.microsoft.com/en-us/microsoftteams/
/
gives xyz_etcd_1).
docker-