Launching The Application; Integration External Ams Interface; Url Content - Bosch rexroth ActiveShuttle System Manual

5. Copy the webhook URL created in step 3 to the compose file for prometheus-msteams section.
Server alerts service under the environment variable - TEAMS_INCOMING_WEBHOOK_URL
6. Repeat steps 2, 3, and 4 for the
17 Prometheus2teams

4.4.3 Launching the application

→ After successful configuration of the server monitoring stack, restart the entire stack.
→ To start the stack use portainer.
→ Alternatively use the following command:
1. For swarm deployment (project name can be found using the command
• Docker service update projectname_prometheus_1 --force
• Docker service update projectname_alertmanager_1 --force
• Docker service update projectname_server-alerts_1 --force
• Docker service update projectname_ams-alerts_1 --force
2. For compose deployment
testüberschrift
docker restart ams_prometheus_1 ams_alertmanager_1 ams_cAdvisor_1 ams_Node-exporter_1
ams_server-alerts_1 ams_ams-alerts_1 -t 0
→ After successful restart, verify that the prometheus targets are up and running by visiting the URL
address:9090/targets.

4 URL content

4.5 Integration external AMS interface

The following information is necessary to use the REST-API or the Socket.IO interface:
• AMS-URL: URL of AMS server, including its port.
Example: https://127.0.0.1:8443
• API-Key: API-Key used to authenticate, provided by the AMS administrators.
Notice
• In this document, these variables appear as placeholders in the code examples.
• Examples for the REST-API will be put out as cURL commands.
◊ For more information on how to use the tool, see https://curl.haxx.se/
→ Always replace variables with the appropriate values before executing the commands.
RA91390962 AB-V1.3.3, en
as well.
ams-alerts
Server deployment | ILS, ActiveShuttle | 51
docker ps | grep prometheus
http://ip-