Отмена, возврат и повтор действий
Excel для Microsoft 365 Word для Microsoft 365 PowerPoint для Microsoft 365 Excel для Microsoft 365 для Mac Word для Microsoft 365 для Mac PowerPoint для Microsoft 365 для Mac Excel для Интернета Word для Интернета PowerPoint для Интернета Excel 2021 Word 2021 PowerPoint 2021 Excel 2021 для Mac Word 2021 для Mac PowerPoint 2021 для Mac Excel 2019 Word 2019 PowerPoint 2019 Excel 2019 для Mac Word 2019 для Mac PowerPoint 2019 для Mac Excel 2016 Word 2016 PowerPoint 2016 Еще. Меньше
В Microsoft Word, PowerPoint и Excel можно отменять и повторно выполнять множество действий. Вы можете отменять изменения даже после их сохранения, а затем сохранять снова, при условии что не превышено максимальное число операций отмены (по умолчанию в Office сохраняются последние 100 действий, которые можно отменить).
Отмена последнего действия
Чтобы отменить действие, нажмите клавиши CTRL+Z на клавиатуре или выберите Отменить на панели быстрого доступа. Чтобы отменить несколько шагов, можно нажать кнопку Отмена (или CTRL+Z).
Примечание: Дополнительные сведения см. в статье Настройка панели быстрого доступа.
Вы не можете отменить некоторые действия, такие как выбор команд на вкладке Файл или сохранение файла. Если вы не можете отменить действие, команда Отменить меняется на Нельзя отменить.
Чтобы отменить несколько действий одновременно, щелкните стрелку рядом с пунктом Отменить
, выберите действия в списке, которые нужно отменить, а затем выберите список.
Совет: Если вы не можете отменить изменения, которые вы хотите отменить изменения, возможно, вы сможете восстановить предыдущую версию файла. См. статью Восстановление предыдущей версии файла в OneDrive или OneDrive для бизнеса
Возврат действия
Чтобы повторить отмененное действие, нажмите клавиши CTRL+Y или F4. (Если F4 не работает, может потребоваться нажать клавишу F-Lock или клавишу Fn, а затем клавишу F4) на клавиатуре или нажать кнопку Повторить на панели быстрого доступа. (Кнопка Вернуть появляется только после отмены действия.)
Примечание: Дополнительные сведения см. в статье Настройка панели быстрого доступа.
Повтор действия
Чтобы повторить что-то простое, например операцию вставки, нажмите клавиши CTRL+Y или F4 (если F4 не работает, возможно, потребуется нажать клавишу F-Lock или клавишу Fn, а затем F4) или выбрать повторить на панели быстрого доступа.
-
По умолчанию кнопка Повторить
Дополнительно: настройка ограничения отмены
По умолчанию в Excel и других программах Office можно отменить и вернуть не более 100 действий. Однако это можно изменить, добавив запись в реестр Microsoft Windows.
Важно: Помните, что некоторые действия, такие как нажатие кнопок на вкладке Файл или сохранение файла, нельзя отменить, а выполнение макроса в Excel очищает стек отмены, из-за чего ее невозможно использовать.
Предупреждение: при увеличении числа уровней отмены следует соблюдать осторожность: чем больше уровней отмены, тем больше оперативной памяти (ОЗУ) требуется Excel для хранения журнала отмены, что влияет на производительность Excel.
Ниже описано, как изменить количество уровней отмены для Excel через редактор реестра. Для Word или PowerPoint нужно выполнить аналогичные действия.
- Закройте все запущенные программы Office.
- В Windows 10 или Windows 8 щелкните правой кнопкой мыши (или долго нажмите) кнопку Пуск, а затем выберите Выполнить. В Windows 7 или Windows Vista нажмите кнопку Пуск. В Windows XP нажмите кнопку Пуск , а затем выберите Выполнить.
- В поле поиска или поле Выполнить введите regedit и нажмите клавишу ВВОД. В зависимости от версии Windows может потребоваться подтвердить открытие редактора реестра.
- В редакторе реестра разверните подраздел реестра, соответствующий вашей версии Excel:
- Excel 2007: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\Options
- Excel 2010: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Excel\Options
- Excel 2013: HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Excel\Options
- Excel 2016: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\Options
- В меню Правка выберите пункт Создать, а затем — Параметр DWORD. Выберите Новое значение 1, укажите тип UndoHistory, а затем нажмите клавишу ВВОД.
- В меню Правка выберите Изменить.
- В диалоговом окне Изменение значения DWORD выберите Десятичный в разделе Базовый. Введите значение в поле Значение, нажмите кнопку ОК и выйдите из реестра Редактор.
- Запустите Excel. Excel будет хранить в журнале отмены количество действий, заданное в шаге 7.
См. также
Отмена последнего действия
+ Z или нажимайте кнопку Отменить в левом верхнем углу ленты, пока не устраните проблему.
Вы не можете отменить некоторые действия, такие как выбор команд в меню Файл или сохранение файла. Если вы не можете отменить действие, команда Отменить меняется на Нельзя отменить.
Чтобы отменить несколько действий одновременно, щелкните стрелку рядом с пунктом Отменить, выберите действия в списке, которые нужно отменить, а затем выберите список.
Совет: Если вы не можете отменить изменения, которые вы хотите отменить изменения, возможно, вы сможете восстановить предыдущую версию файла. См. статью Восстановление предыдущей версии файла в OneDrive или OneDrive для бизнеса
Возврат действия
Чтобы повторить отмену, нажмите
+ Y или выберите Повторить в левом верхнем углу ленты. (Кнопка Вернуть появляется только после отмены действия.)
Repeat an action
Чтобы повторить что-то простое, например операцию вставки, нажмите
+ Y или выберите Повторить в левом верхнем углу ленты.
В Word в Интернете,Веб-приложение PowerPoint и Excel в Интернете можно отменить или повторить основные действия. Дополнительные возможности доступны в классической версии Office.
Отмена последнего действия
Нажимайте клавиши CTRL+Z или выберите
(Отменить) на ленте, пока не устраните проблему.
Вы не можете отменить некоторые действия, такие как выбор команд на вкладке Файл или сохранение файла. Если вы не можете отменить действие, команда Отменить будет неактивна (затенена).
Совет: Если вы не можете отменить изменения, которые вы хотите отменить изменения, возможно, вы сможете восстановить предыдущую версию файла. См. статью Восстановление предыдущей версии файла в OneDrive или OneDrive для бизнеса
Возврат действия
Чтобы повторить отмену, нажмите клавиши CTRL+Y или выберите
(Повторить) на ленте.
Repeat an action
Чтобы повторить что-то простое, например операцию вставки, нажмите клавиши CTRL+Y на клавиатуре или выберите Повторить на вкладке Главная .
Understand Electronic Stability Control: Meaning, Causes, and Troubleshooting
Electronic Stability Control (ESC) is a vital safety feature in modern vehicles to improve stability and prevent accidents. It uses sensors to monitor the direction the driver intends to travel and the vehicle’s actual movement. Suppose the vehicle begins to deviate from its intended path. In that case, ESC intervenes by automatically applying individual brakes to wheels and adjusting engine power to help keep the vehicle on its intended course. Despite its effectiveness, ESC can malfunction due to various causes, such as faulty sensors, software issues, or damaged control modules.
Repair Time:
The typical time range in hours required to complete this repair.
Repair Cost:
The average repair cost range in USD to complete this repair by either an honest mechanic or as a DIY. Including the cost of parts but not tools.
Repair Difficulty:
This indicates how difficult it is for most DIYers and mechanics to perform this repair.
Troubleshooting ESC issues involves utilizing a YOUCANIC full system scanner and fixing the root cause, ranging from simple solutions, such as a software update, to more complex repairs, such as replacing a faulty component. Understanding ESC’s meaning, causes, and troubleshooting can help ensure that this important safety feature functions optimally, improving stability and reducing the risk of accidents.
ESC Meaning
ESC stands for Electronic Stability Control, a safety system that enhances a vehicle’s stability by detecting and reducing loss of traction (skidding). It works by applying individual brakes to wheels and adjusting engine power to help keep the vehicle on its intended course. ESC system enhances driving stability and helps prevent accidents by intervening when the vehicle loses control, thus helping the driver maintain control.
YOUCANIC Pro Manuals
Give you access to the original OEM Factory Repair Manuals. Each manual offers meticulously detailed steps and vivid illustrations, extensive wiring diagrams, precise torque specifications, and exclusive access to technical service bulletins and OEM service information—everything you need, just what the dealerships use.
- ESC – Electronic Stability Control
- ESP – Electronic Stability Program
- DSC – Dynamic Stability Control
ESC, ESP, and DSC are all acronyms that refer to the same technology in vehicles, known as Electronic Stability Control. These terms are often used interchangeably, but their exact definition may vary slightly depending on the automaker. The basic function of ESC, ESP, and DSC is to help improve the stability of a vehicle by detecting and reducing loss of traction (skidding) during sudden maneuvers or slippery road conditions. The system uses sensors to monitor the direction in which the driver intends to travel and the vehicle’s actual movement. Suppose the vehicle begins to deviate from its intended path. In that case, the system intervenes by automatically applying individual brakes to wheels and adjusting engine power to help keep the vehicle on its intended course. Regardless of the name, all of these systems serve the same purpose of improving vehicle handling, stability, and safety.
Common Problems
Several technical issues can cause problems with the Electronic Stability Control (ESC) system:
- Faulty sensors: ESC relies on sensors to monitor the vehicle’s movement and direction; any malfunction or damage to these sensors can cause the ESC not to work properly. The ABSwheel speed sensor is the most common problem that triggers stability control error messages.
- Software issues: ESC uses a control module that runs on software; any bugs or glitches in the software can cause the ESC to malfunction.
- Damaged control module: The control module, which is the brain of the ESC system, can get damaged for various reasons such as electrical issues, water damage, or physical damage, which can result in ESC problems.
- Wiring issues: ESC relies on a network of wires and connectors to communicate with other parts of the vehicle; any issues with the wiring or connectors can result in the ESC not functioning properly.
- Incorrect calibration: ESC requires proper calibration to work correctly; any calibration issues can result in the ESC not functioning properly.
- Failed components: The ESC system contains several components like actuators, valves, and solenoids that can fail over time, resulting in ESC problems.
- Brake light switch – A defective switch can trigger the ESC light. This is a common problem. Easy to replace and inexpensive.
- Steering angle sensor – The sensor may require calibration.
- Low battery – Low battery voltage.
It is important to diagnose and fix the root cause of any ESC problems to ensure that this important safety feature is functioning optimally and reducing the risk of accidents.
Troubleshooting
The stability control system, in most cases, comes on because of a faulty ABS wheel speed sensor. Other problems can trigger the stability control light to come on. If the stability control light is constantly on, the system is disabled or malfunctioning.
Below are a few simple things to check if your stability control light is on.
Check the Stability Control Button
On your dashboard, an ESC button may have been pressed accidentally. You can manually turn the ESC light off if that’s the case. Start the car. Find the switch that says ESC, ESP, or DSC on the dash and press it for three seconds. Look at your instrument cluster to see if the light is turned off.
Diagnose the stability system.
The fastest way to determine why your stability control light is on is to use a diagnostic scanner to read codes from the stability and ABS modules. You must have an ABS scanner to diagnose ESC and ABS problems. Basic OBD-II code readers are not able to communicate with the ABS module. Use a diagnostic scanner such as YOUCANIC Full System Scanner to scan your car’s multiple systems via the OBD-II port.
If your vehicle is still under warranty, take your car to the dealer to properly diagnose the ESC problem. There shouldn’t be a charge to fix stability problems if the vehicle has an existing warranty.
| Step 1: Plug in the scanner on the OBD-II port under the dashboard. |
| Step 2: Turn the ignition to the ON position. Do not start the car. |
| Step 3: Access the ESC and ABS menus and read fault codes. |
What causes the stability control light to come on?
8 out of 10 times, the stability control light comes on due to a faulty wheel speed sensor or an ABS sensor. These sensors can fail over time, get dirty, and damage the wires or connectors. It is a widespread problem and relatively easy to fix. A faulty steering angle sensor is the second most common problem that triggers the stability control light.
You may notice that both ABS and stability lights have turned on simultaneously. The stability system depends on the ABS module to function properly. Therefore, if there is a problem with the ABS module, the stability system will not function.
Why is my stability control light flashing?
Under normal operation, the ESC light should only be on when you start the car for a few seconds and then turn it off. If the ESC light is flashing when driving, the system is engaged and trying to keep the vehicle under control.
It doesn’t mean that there is something wrong with the ESC system. It means that you may be going too fast and should slow down. ESC will flash if you are going through a corner too fast. The light turns off under normal driving conditions.
How do I know if my car has stability control?
Most cars have stability control installed, but it may be called a different name. Electronic stability control (ESC) may also be referred to as an electronic stability program (ESP) or dynamic stability control (DSC).
Here is a list of what ESC is called on different makes.
| Acronym | Make |
|---|---|
| ESC | Hyundai, Kia, Chevrolet, Dodge, Chrysler, Audi, Saturn |
| ESP | Mercedes-Benz, VW, Sprinter, Suzuki, BMW, Renault, Jeep |
| DSC | Mazda, BMW, Jaguar |
| StabiliTrak | General Motors, Cadillac, Chevrolet, Buick, GMC, Holden, Opel, Vauxhall, GM |
My stability light came on after changing the battery.
If the ESC light stays on after you replace the battery, don’t panic. All you need to do is start the car and turn the steering wheel fully left and right several times. Then, drive for a minute, and the ABS and ESP lights should reset. Once the system does a self-check, it should reset the stability light.
Do different tires turn on the stability traction lights?
If you install different tire sizes on the front vs. the back, you may cause the ESC to malfunction.ESC may also come on when using a spare tire with a different diameter than the other tires on the car.
We hope you find the Electronic Stability Control (ESC) | Symptoms Problems guide helpful. Check these troubleshooting and repair guides for more help on your vehicle.
Written and fact-checked by:
YOUCANIC articles are written by authors who collectively have over 60 years of experience in the automotive field and years of hands-on experience on vehicles. These authors are certified ASE G1 Automotive Maintenance engine professionals (the highest level certification for vehicle maintenance and repair). They hold associate’s and bachelor’s degrees, as well as having gone on to further study to receive a master’s and doctorate degrees. These authors collaborate on research, writing, editing, and fact-checking every article to ensure that it is accurate and up to date and delivers the best counsel and information to YOUCANIC readers. View all posts
Для отмены сохранения документа нажмите esc что делать
Если вы запускаете действие, которое выполняется не сразу же, PowerPoint выводит окно сообщения с кнопкой «Отмена». В области состояния в нижней части окна PowerPoint также может появиться индикатор выполнения. Примерами таких продолжительных действий являются сохранение файла, вставка крупного звукового или видеофайла, сжатие все всех фотографий в большой презентации или замена шрифтов.
Если вы больше не хотите выполнять такое действие, нажмите клавишу ESC или кнопку «Отмена». Если действие выполняется слишком долго, вероятно, лучше отменить его и попробовать еще раз.
Управление файлами PDF и отсканированными документами с помощью приложения «Заметки» на Mac
В приложении «Заметки» на Mac можно добавлять файлы PDF или отсканированные документы, обрезать и поворачивать их, применять к ним фильтры и переименовывать их.
Просмотр файла PDF или отсканированного документа
- В приложении «Заметки» на Mac можно искать файлы PDF и отсканированные документы указанными способами.
- Посмотрите в заметке, в которую он был добавлен.
- Выполните поиск файла PDF или отсканированного документа по названию.
- Выберите «Вид» > «Показать браузер вложений», затем нажмите «Сканы» или «Документы». Чтобы просмотреть вложение внутри содержащей его заметки, выберите вложение, затем выберите «Вид» > «Показать в заметке».
Примечание. Если Вы используете macOS 10.14 или новее, а также iOS 12 или новее либо iPadOS 13 или новее, можно сканировать документы напрямую с камеры iPhone или iPad. Нажмите в начале строки в заметке, выберите «Файл» > «Вставить с iPhone или iPad», затем выберите «Отсканировать документы», чтобы отсканировать документ с помощью iPhone или iPad, а затем вставить его в заметку. См. раздел Вставка фотографий и отсканированных изображений при помощи Камеры Continuity.
Выполните любое из указанных действий.
-
Предварительный просмотр файла PDF или отсканированного документа. Нажмите стрелку вниз рядом с названием документа, затем выберите «Быстрый просмотр вложения».
Совет. При использовании трекпада можно изменять масштаб сведением и разведением пальцев в Быстром просмотре.
Обрезка файла PDF
Можно обрезать файл PDF, чтобы выделить определенный фрагмент или удалить лишние части документа.
- В Заметках на Mac нажмите стрелку вниз рядом с названием файла PDF, затем выберите вариант «Разметка». Если стрелка вниз не отображается, нажмите файл PDF, удерживая клавишу Control, затем нажмите «Режим просмотра» и выберите «Средний» или «Крупный».
- Удерживая клавишу Control, нажмите миниатюру, затем нажмите «Обрезать страницу» (или используйте панель Touch Bar).
- Нажмите кнопку «Обрезать»
, затем перетяните метки-манипуляторы выбора таким образом, чтобы охватить нужную область файла PDF. - Завершив внесение изменений, выполните одно из указанных действий.
- Сохранение изменений. Нажмите «Готово».
- Выход из режима обрезки без сохранения изменений. Нажмите клавишу Escape (Esc) или нажмите «Отменить».
Обрезка отсканированного документа
Можно обрезать отсканированный документ для выделения определенного фрагмента или устранения лишних частей документа.
- В приложении «Заметки» на Mac нажмите «Показать миниатюры» рядом с названием отсканированного документа. Если кнопка «Показать миниатюры» не отображается, нажмите файл PDF или отсканированный документ, удерживая клавишу Control, затем нажмите «Режим просмотра» и выберите «Средний» или «Крупный».
- Удерживая клавишу Control, нажмите миниатюру, затем нажмите «Обрезать страницу» (или используйте панель Touch Bar).
- Перетяните метки-манипуляторы выбора таким образом, чтобы охватить нужную область файла PDF или отсканированного документа.
- Завершив внесение изменений, выполните одно из указанных действий.
- Сохранение изменений. Нажмите «Готово».
- Выход из режима обрезки без сохранения изменений. Нажмите клавишу Escape (Esc) или нажмите «Отменить».
Применение фильтра к отсканированному документу
Вы можете придать отсканированному документу особый внешний вид, воспользовавшись одним из четырех фильтров.
- В приложении «Заметки» на Mac нажмите «Показать миниатюры» рядом с названием отсканированного документа.
- Удерживая клавишу Control, нажмите миниатюру, затем выберите «Фильтры».
- Нажмите нужный фильтр (или коснитесь его в панели Touch Bar).
Поворот файла PDF или отсканированного документа
Можно повернуть файл PDF или отсканированный документ вручную, изменив его ориентацию.
- В приложении «Заметки» на Mac нажмите «Показать миниатюры» рядом с названием файла PDF или отсканированного документа.
- Удерживая клавишу Control, нажмите миниатюру, затем нажмите «Повернуть влево» или «Повернуть вправо» (или используйте панель Touch Bar).
Для достижения нужной ориентации документ можно повернуть несколько раз.
Переименование файла PDF или отсканированного документа
По умолчанию отсканированный документ автоматически получает название, например Отсканированные документы, а файл PDF получает название оригинального файла. Можно переименовать любой из этих видов вложений.
- В приложении «Заметки» на Mac выберите файл PDF или отсканированный документ в заметке, затем выберите меню «Правка» > «Переименовать вложение».
- Введите новое имя, затем нажмите «Сохранить».
Проблемы с сохранением слайда в powerpoint 2007
День добрый!
Такой вопрос, при сохранение презентации стало появляться сообщение «Для отмены сохранения нажмите ESC». Как от этого избавиться, чтобы просто сохраняло и все?
94731 / 64177 / 26122
Регистрация: 12.04.2006
Сообщений: 116,782
Ответы с готовыми решениями:
Как спрятать дополнительный текст слайда (PowerPoint 2007)?
как спрятать дополнительный текст слайда, т.е. оставить только один заголовок слайда.
Powerpoint 2013 автоматическая смена слайда
Не могу добиться автоматической смена слайда. Вот такие настройки, галочку «по щелчку» что ставлю.
Применение дизайна слайда ко всем слайдам в презентации PowerPoint
Имею презентацию, вставляю в нее слайд с другим дизайном из другой презентации. Можно как-нибудь.
PowerPoint 2007 гиперссылка
Можно ли сделать чтобы при нажатии на гиперссылку на данном слайде происходила необходимая анимация.
Создание снимка экрана на компьютере Mac
Вы можете делать снимки всего экрана, его области или одного окна.
Как создать снимок экрана на компьютере Mac
- Чтобы создать снимок экрана, одновременно нажмите и удерживайте следующие три клавиши: Shift, Command и 3.
- Если в углу экрана появится миниатюра, щелкните ее, чтобы отредактировать снимок экрана. Или дождитесь сохранения снимка экрана на рабочем столе.
Как сделать снимок области экрана
- Одновременно нажмите и удерживайте следующие три клавиши: Shift, Command и 4.
- Перетащите перекрестие , чтобы выбрать область экрана для создания снимка. Чтобы переместить выбранную область, нажмите и удерживайте клавишу пробела при перетаскивании. Чтобы отменить создание снимка, нажмите клавишу Esc (Escape).
- Чтобы создать снимок, отпустите кнопку мыши или трекпада.
- Если в углу экрана появится миниатюра, щелкните ее, чтобы отредактировать снимок экрана. Или дождитесь сохранения снимка экрана на рабочем столе.
Как создать снимок окна или меню
- Откройте окно или меню, снимок которого требуется создать.
- Одновременно нажмите и удерживайте следующие четыре клавиши: Shift, Command, 4 и пробел. Указатель изменится на значок камеры . Чтобы отменить создание снимка, нажмите клавишу Esc (Escape).
- Щелкните окно или меню, чтобы создать его снимок. Чтобы снимок не содержал тени окна, при щелчке удерживайте нажатой клавишу Option.
- Если в углу экрана появится миниатюра, щелкните ее, чтобы отредактировать снимок экрана. Или дождитесь сохранения снимка экрана на рабочем столе.
Где найти снимки экрана
По умолчанию снимки экрана сохраняются на рабочем столе с именем «Снимок экрана [дата] ([время]).png».
В macOS Mojave и более поздних версий можно изменить расположение сохраненных снимков экрана по умолчанию в меню «Параметры» приложения «Снимок экрана». Миниатюру также можно перетащить в папку или документ.
Дополнительная информация
- В macOS Mojave и более поздних версий также можно установить таймер и выбрать расположение для сохранения снимков экрана в приложении «Снимок экрана». Чтобы открыть это приложение, одновременно нажмите и удерживайте следующие три клавиши: Shift, Command и 5. Узнайте больше о приложении «Снимок экрана».
- Некоторые приложения, например Apple TV, могут не позволять делать снимки экрана своих окон.
- Чтобы скопировать снимок экрана в буфер обмена, нажмите и удерживайте клавишу Control при создании снимка. Затем его можно вставить куда-нибудь еще. Или же можно воспользоваться универсальным буфером обмена, чтобы вставить этот снимок на другом устройстве Apple.
Дата публикации: 17 ноября 2023 г.
Zabbix + AWS ECS
Amazon Elastic Compute Cloud is a part of Amazon.com’s cloud-computing platform, Amazon Web Services, that allows users to rent virtual computers on which to run their own computer applications.
Available solutions
- AWS ECS Cluster by HTTP
- AWS ECS Serverless Cluster by HTTP
- 3rd party solutions
This template is for Zabbix version: 6.4
Also available for: 6.0
AWS ECS Cluster by HTTP
Overview
The template to monitor AWS ECS Cluster by HTTP via Zabbix that works without any external scripts. Most of the metrics are collected in one go, thanks to Zabbix bulk data collection. NOTE This template uses the GetMetricData CloudWatch API calls to list and retrieve metrics. For more information, please refer to the CloudWatch pricing page.
Additional information about the metrics and used API methods:
- Full metrics list related to ECS: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-ECS.html
Requirements
Zabbix version: 6.4 and higher.
Tested versions
This template has been tested on:
- AWS ECS Cluster by HTTP
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
The template gets AWS ECS metrics and uses the script item to make HTTP requests to the CloudWatch API.
Before using the template, you need to create an IAM policy for the Zabbix role in your AWS account with the necessary permissions.
Add the following required permissions to your Zabbix IAM policy in order to collect Amazon ECS metrics.
If you are using role-based authorization, set the appropriate permissions:
< "Version": "2012-10-17", "Statement": [ < "Effect": "Allow", "Action": "iam:PassRole", "Resource": "arn:aws:iam::>:role/>" >, < "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "cloudwatch:DescribeAlarms", "cloudwatch:GetMetricData", "ecs:ListServices", "esc:ListTasks", "ec2:AssociateIamInstanceProfile", "ec2:ReplaceIamInstanceProfileAssociation" ], "Resource": "*" >] > If you are using access key-based authorization, set the following macros «», «»
For more information about managing access keys, see official documentation
Refer to the Macros section for a list of macros used for LLD filters.
Additional information about the metrics and used API methods:
- Full metrics list related to ECS: https://docs.aws.amazon.com/AmazonECS/latest/userguide/metrics-dimensions.html
Macros used
Sets HTTP proxy value. If this macro is empty then no proxy is used.
Secret access key.
Amazon ECS Region code.
Authorization method. Possible values: role_base, access_key.
ECS cluster name.
Filter of discoverable alarms by name.
Filter to exclude discovered alarms by name.
Filter of discoverable alarms by namespace.
Filter to exclude discovered alarms by namespace.
Filter of discoverable services by name.
Filter to exclude discovered services by name.
The warning threshold of the cluster CPU utilization expressed in %.
The warning threshold of the cluster memory utilization expressed in %.
The warning threshold of the cluster service CPU utilization expressed in %.
The warning threshold of the cluster service memory utilization expressed in %.
Items
Get cluster metrics.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Get cluster services.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Get alarms data.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Data collection check.
Preprocessing
- JSON Path: $.error ⛔️Custom on fail: Set value to
- Discard unchanged with heartbeat: 3h
Data collection check.
Preprocessing
- JSON Path: $.error ⛔️Custom on fail: Set value to
- Discard unchanged with heartbeat: 3h
‘The number of EC2 instances running the Amazon ECS agent that are registered with a cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of tasks running in the cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of services in the cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘A number of CPU units reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.’
Preprocessing
- JSON Path: $.[?(@.Label == «CpuReserved»)].Values.first().first() ⛔️Custom on fail: Discard value
Cluster CPU utilization
Preprocessing
- JSON Path: $.CPUUtilization ⛔️Custom on fail: Discard value
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: $.MemoryUtilization ⛔️Custom on fail: Discard value
‘The number of bytes received by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes transmitted by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
Triggers
The CPU utilization is too high. The system might be slow to respond.
The system is running out of free memory.
LLD rule Cluster Alarms discovery
Discovery instance alarms.
Preprocessing
- JavaScript: The text is too long. Please see the template.
- Discard unchanged with heartbeat: 3h
Item prototypes for Cluster Alarms discovery
Get alarm metrics about the state and its reason.
Preprocessing
- JSON Path: $.[?(@.AlarmName == «»)].first() ⛔️Custom on fail: Discard value
An explanation for the alarm state, in text format.
Preprocessing
- JSON Path: $.StateReason ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The state value for the alarm. Possible values: 0 (OK), 1 (INSUFFICIENT_DATA), 2 (ALARM).
Preprocessing
- JSON Path: $.StateValue ⛔️Custom on fail: Set value to: 3
- JavaScript: The text is too long. Please see the template.
Trigger prototypes for Cluster Alarms discovery
Alarm «» has ‘Alarm’ state.
Reason:
LLD rule Cluster Services discovery
Preprocessing
- JSON Path: $.services
- Discard unchanged with heartbeat: 3h
Item prototypes for Cluster Services discovery
The number of tasks currently in the running state.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The number of tasks currently in the pending state.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The desired number of tasks for an service.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The number of task sets in the service.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
«A number of CPU units reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.»
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
«A number of CPU units used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.»
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1048576
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The memory that is reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1048576
‘The number of bytes received by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes transmitted by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
Get metrics of ESC services.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Trigger prototypes for Cluster Services discovery
The CPU utilization is too high. The system might be slow to respond.
The system is running out of free memory.
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide feedback, discuss the template, or ask for help at ZABBIX forums
This template is for Zabbix version: 6.0
Also available for: 6.4
AWS ECS Cluster by HTTP
Overview
The template to monitor AWS ECS Cluster by HTTP via Zabbix that works without any external scripts. Most of the metrics are collected in one go, thanks to Zabbix bulk data collection. NOTE This template uses the GetMetricData CloudWatch API calls to list and retrieve metrics. For more information, please refer to the CloudWatch pricing page.
Additional information about the metrics and used API methods:
- Full metrics list related to ECS: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-ECS.html
Requirements
Zabbix version: 6.0 and higher.
Tested versions
This template has been tested on:
- AWS ECS Cluster by HTTP
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
The template gets AWS ECS metrics and uses the script item to make HTTP requests to the CloudWatch API.
Before using the template, you need to create an IAM policy for the Zabbix role in your AWS account with the necessary permissions.
Add the following required permissions to your Zabbix IAM policy in order to collect Amazon ECS metrics.
If you are using role-based authorization, set the appropriate permissions:
< "Version": "2012-10-17", "Statement": [ < "Effect": "Allow", "Action": "iam:PassRole", "Resource": "arn:aws:iam::>:role/>" >, < "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "cloudwatch:DescribeAlarms", "cloudwatch:GetMetricData", "ecs:ListServices", "esc:ListTasks", "ec2:AssociateIamInstanceProfile", "ec2:ReplaceIamInstanceProfileAssociation" ], "Resource": "*" >] > If you are using access key-based authorization, set the following macros «», «»
For more information about managing access keys, see official documentation
Refer to the Macros section for a list of macros used for LLD filters.
Additional information about the metrics and used API methods:
- Full metrics list related to ECS: https://docs.aws.amazon.com/AmazonECS/latest/userguide/metrics-dimensions.html
Macros used
Sets HTTP proxy value. If this macro is empty then no proxy is used.
Secret access key.
Amazon ECS Region code.
Authorization method. Possible values: role_base, access_key.
ECS cluster name.
Filter of discoverable alarms by name.
Filter to exclude discovered alarms by name.
Filter of discoverable alarms by namespace.
Filter to exclude discovered alarms by namespace.
Filter of discoverable services by name.
Filter to exclude discovered services by name.
The warning threshold of the cluster CPU utilization expressed in %.
The warning threshold of the cluster memory utilization expressed in %.
The warning threshold of the cluster service CPU utilization expressed in %.
The warning threshold of the cluster service memory utilization expressed in %.
Items
Get cluster metrics.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Get cluster services.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Get alarms data.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Data collection check.
Preprocessing
- JSON Path: $.error ⛔️Custom on fail: Set value to
- Discard unchanged with heartbeat: 3h
Data collection check.
Preprocessing
- JSON Path: $.error ⛔️Custom on fail: Set value to
- Discard unchanged with heartbeat: 3h
‘The number of EC2 instances running the Amazon ECS agent that are registered with a cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of tasks running in the cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of services in the cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘A number of CPU units reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.’
Preprocessing
- JSON Path: $.[?(@.Label == «CpuReserved»)].Values.first().first() ⛔️Custom on fail: Discard value
Cluster CPU utilization
Preprocessing
- JSON Path: $.CPUUtilization ⛔️Custom on fail: Discard value
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: $.MemoryUtilization ⛔️Custom on fail: Discard value
‘The number of bytes received by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes transmitted by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
Triggers
The CPU utilization is too high. The system might be slow to respond.
The system is running out of free memory.
LLD rule Cluster Alarms discovery
Discovery instance alarms.
Preprocessing
- JavaScript: The text is too long. Please see the template.
- Discard unchanged with heartbeat: 3h
Item prototypes for Cluster Alarms discovery
Get alarm metrics about the state and its reason.
Preprocessing
- JSON Path: $.[?(@.AlarmName == «»)].first() ⛔️Custom on fail: Discard value
An explanation for the alarm state, in text format.
Preprocessing
- JSON Path: $.StateReason ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The state value for the alarm. Possible values: 0 (OK), 1 (INSUFFICIENT_DATA), 2 (ALARM).
Preprocessing
- JSON Path: $.StateValue ⛔️Custom on fail: Set value to: 3
- JavaScript: The text is too long. Please see the template.
Trigger prototypes for Cluster Alarms discovery
Alarm «» has ‘Alarm’ state.
Reason:
LLD rule Cluster Services discovery
Preprocessing
- JSON Path: $.services
- Discard unchanged with heartbeat: 3h
Item prototypes for Cluster Services discovery
The number of tasks currently in the running state.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The number of tasks currently in the pending state.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The desired number of tasks for an service.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The number of task sets in the service.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
«A number of CPU units reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.»
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
«A number of CPU units used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.»
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1048576
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The memory that is reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1048576
‘The number of bytes received by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes transmitted by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
Get metrics of ESC services.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Trigger prototypes for Cluster Services discovery
The CPU utilization is too high. The system might be slow to respond.
The system is running out of free memory.
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide feedback, discuss the template, or ask for help at ZABBIX forums
This template is for Zabbix version: 6.4
Also available for: 6.0
AWS ECS Serverless Cluster by HTTP
Overview
The template to monitor AWS ECS Serverless Cluster by HTTP via Zabbix that works without any external scripts. Most of the metrics are collected in one go, thanks to Zabbix bulk data collection. NOTE This template uses the GetMetricData CloudWatch API calls to list and retrieve metrics. For more information, please refer to the CloudWatch pricing page.
Additional information about the metrics and used API methods:
- Full metrics list related to ECS: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-ECS.html
Requirements
Zabbix version: 6.4 and higher.
Tested versions
This template has been tested on:
- AWS ECS Cluster by HTTP
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
The template gets AWS ECS metrics and uses the script item to make HTTP requests to the CloudWatch API.
Before using the template, you need to create an IAM policy for the Zabbix role in your AWS account with the necessary permissions.
Add the following required permissions to your Zabbix IAM policy in order to collect Amazon ECS metrics.
If you are using role-based authorization, set the appropriate permissions:
< "Version": "2012-10-17", "Statement": [ < "Effect": "Allow", "Action": "iam:PassRole", "Resource": "arn:aws:iam::>:role/>" >, < "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "cloudwatch:DescribeAlarms", "cloudwatch:GetMetricData", "ecs:ListServices", "esc:ListTasks", "ec2:AssociateIamInstanceProfile", "ec2:ReplaceIamInstanceProfileAssociation" ], "Resource": "*" >] > If you are using access key-based authorization, set the following macros «», «»
For more information about managing access keys, see official documentation
Refer to the Macros section for a list of macros used for LLD filters.
Additional information about the metrics and used API methods:
- Full metrics list related to ECS: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-ECS.html
Macros used
Sets HTTP proxy value. If this macro is empty then no proxy is used.
Secret access key.
Amazon ECS Region code.
Authorization method. Possible values: role_base, access_key.
ECS cluster name.
Filter of discoverable alarms by name.
Filter to exclude discovered alarms by name.
Filter of discoverable alarms by namespace.
Filter to exclude discovered alarms by namespace.
Filter of discoverable services by name.
Filter to exclude discovered services by name.
The warning threshold of the cluster CPU utilization expressed in %.
The warning threshold of the cluster memory utilization expressed in %.
The warning threshold of the cluster service CPU utilization expressed in %.
The warning threshold of the cluster service memory utilization expressed in %.
Items
Get cluster metrics.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Get cluster services.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Get alarms data.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Data collection check.
Preprocessing
- JSON Path: $.error ⛔️Custom on fail: Set value to
- Discard unchanged with heartbeat: 3h
Data collection check.
Preprocessing
- JSON Path: $.error ⛔️Custom on fail: Set value to
- Discard unchanged with heartbeat: 3h
‘The number of EC2 instances running the Amazon ECS agent that are registered with a cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of tasks running in the cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of services in the cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
Cluster CPU utilization
Preprocessing
- JSON Path: $.CPUUtilization ⛔️Custom on fail: Discard value
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: $.MemoryUtilization ⛔️Custom on fail: Discard value
‘The number of bytes received by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes transmitted by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes reserved from ephemeral storage in the resource that is specified by the dimensions that you’re using. Ephemeral storage is used for the container root filesystem and any bind mount host volumes defined in the container image and task definition. The amount of ephemeral storage can’t be changed in a running task.
This metric is only available for tasks that run on Fargate Linux platform version 1.4.0 or later.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1073741824
‘The number of bytes used from ephemeral storage in the resource that is specified by the dimensions that you’re using. Ephemeral storage is used for the container root filesystem and any bind mount host volumes defined in the container image and task definition. The amount of ephemeral storage can’t be changed in a running task.
This metric is only available for tasks that run on Fargate Linux platform version 1.4.0 or later.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1073741824
‘The calculated Disk Utilization’
Preprocessing
- JSON Path: $.DiskUtilization ⛔️Custom on fail: Discard value
Triggers
The CPU utilization is too high. The system might be slow to respond.
The system is running out of free memory.
LLD rule Cluster Alarms discovery
Discovery instance alarms.
Preprocessing
- JavaScript: The text is too long. Please see the template.
- Discard unchanged with heartbeat: 3h
Item prototypes for Cluster Alarms discovery
Get alarm metrics about the state and its reason.
Preprocessing
- JSON Path: $.[?(@.AlarmName == «»)].first() ⛔️Custom on fail: Discard value
An explanation for the alarm state, in text format.
Preprocessing
- JSON Path: $.StateReason ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The state value for the alarm. Possible values: 0 (OK), 1 (INSUFFICIENT_DATA), 2 (ALARM).
Preprocessing
- JSON Path: $.StateValue ⛔️Custom on fail: Set value to: 3
- JavaScript: The text is too long. Please see the template.
Trigger prototypes for Cluster Alarms discovery
Alarm «» has ‘Alarm’ state.
Reason:
LLD rule Cluster Services discovery
Preprocessing
- JSON Path: $.services
- Discard unchanged with heartbeat: 3h
Item prototypes for Cluster Services discovery
The number of tasks currently in the running state.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The number of tasks currently in the pending state.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The desired number of tasks for an service.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The number of task sets in the service.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
«A number of CPU units reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.»
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
«A number of CPU units used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.»
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1048576
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The memory that is reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1048576
‘The number of bytes received by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes transmitted by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes reserved from ephemeral storage in the resource that is specified by the dimensions that you’re using. Ephemeral storage is used for the container root filesystem and any bind mount host volumes defined in the container image and task definition. The amount of ephemeral storage can’t be changed in a running task.
This metric is only available for tasks that run on Fargate Linux platform version 1.4.0 or later.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1073741824
‘The number of bytes used from ephemeral storage in the resource that is specified by the dimensions that you’re using. Ephemeral storage is used for the container root filesystem and any bind mount host volumes defined in the container image and task definition. The amount of ephemeral storage can’t be changed in a running task.
This metric is only available for tasks that run on Fargate Linux platform version 1.4.0 or later.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1073741824
‘The number of bytes read from storage in the resource that is specified by the dimensions that you’re using.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes written to storage in the resource that is specified by the dimensions that you’re using.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
Get metrics of ESC services.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Trigger prototypes for Cluster Services discovery
The CPU utilization is too high. The system might be slow to respond.
The system is running out of free memory.
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide feedback, discuss the template, or ask for help at ZABBIX forums
This template is for Zabbix version: 6.0
Also available for: 6.4
AWS ECS Serverless Cluster by HTTP
Overview
The template to monitor AWS ECS Serverless Cluster by HTTP via Zabbix that works without any external scripts. Most of the metrics are collected in one go, thanks to Zabbix bulk data collection. NOTE This template uses the GetMetricData CloudWatch API calls to list and retrieve metrics. For more information, please refer to the CloudWatch pricing page.
Additional information about the metrics and used API methods:
- Full metrics list related to ECS: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-ECS.html
Requirements
Zabbix version: 6.0 and higher.
Tested versions
This template has been tested on:
- AWS ECS Cluster by HTTP
Configuration
Zabbix should be configured according to the instructions in the Templates out of the box section.
Setup
The template gets AWS ECS metrics and uses the script item to make HTTP requests to the CloudWatch API.
Before using the template, you need to create an IAM policy for the Zabbix role in your AWS account with the necessary permissions.
Add the following required permissions to your Zabbix IAM policy in order to collect Amazon ECS metrics.
If you are using role-based authorization, set the appropriate permissions:
< "Version": "2012-10-17", "Statement": [ < "Effect": "Allow", "Action": "iam:PassRole", "Resource": "arn:aws:iam::>:role/>" >, < "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "cloudwatch:DescribeAlarms", "cloudwatch:GetMetricData", "ecs:ListServices", "esc:ListTasks", "ec2:AssociateIamInstanceProfile", "ec2:ReplaceIamInstanceProfileAssociation" ], "Resource": "*" >] > If you are using access key-based authorization, set the following macros «», «»
For more information about managing access keys, see official documentation
Refer to the Macros section for a list of macros used for LLD filters.
Additional information about the metrics and used API methods:
- Full metrics list related to ECS: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-ECS.html
Macros used
Sets HTTP proxy value. If this macro is empty then no proxy is used.
Secret access key.
Amazon ECS Region code.
Authorization method. Possible values: role_base, access_key.
ECS cluster name.
Filter of discoverable alarms by name.
Filter to exclude discovered alarms by name.
Filter of discoverable alarms by namespace.
Filter to exclude discovered alarms by namespace.
Filter of discoverable services by name.
Filter to exclude discovered services by name.
The warning threshold of the cluster CPU utilization expressed in %.
The warning threshold of the cluster memory utilization expressed in %.
The warning threshold of the cluster service CPU utilization expressed in %.
The warning threshold of the cluster service memory utilization expressed in %.
Items
Get cluster metrics.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Get cluster services.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Get alarms data.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Data collection check.
Preprocessing
- JSON Path: $.error ⛔️Custom on fail: Set value to
- Discard unchanged with heartbeat: 3h
Data collection check.
Preprocessing
- JSON Path: $.error ⛔️Custom on fail: Set value to
- Discard unchanged with heartbeat: 3h
‘The number of EC2 instances running the Amazon ECS agent that are registered with a cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of tasks running in the cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of services in the cluster.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
Cluster CPU utilization
Preprocessing
- JSON Path: $.CPUUtilization ⛔️Custom on fail: Discard value
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: $.MemoryUtilization ⛔️Custom on fail: Discard value
‘The number of bytes received by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes transmitted by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes reserved from ephemeral storage in the resource that is specified by the dimensions that you’re using. Ephemeral storage is used for the container root filesystem and any bind mount host volumes defined in the container image and task definition. The amount of ephemeral storage can’t be changed in a running task.
This metric is only available for tasks that run on Fargate Linux platform version 1.4.0 or later.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1073741824
‘The number of bytes used from ephemeral storage in the resource that is specified by the dimensions that you’re using. Ephemeral storage is used for the container root filesystem and any bind mount host volumes defined in the container image and task definition. The amount of ephemeral storage can’t be changed in a running task.
This metric is only available for tasks that run on Fargate Linux platform version 1.4.0 or later.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1073741824
‘The calculated Disk Utilization’
Preprocessing
- JSON Path: $.DiskUtilization ⛔️Custom on fail: Discard value
Triggers
The CPU utilization is too high. The system might be slow to respond.
The system is running out of free memory.
LLD rule Cluster Alarms discovery
Discovery instance alarms.
Preprocessing
- JavaScript: The text is too long. Please see the template.
- Discard unchanged with heartbeat: 3h
Item prototypes for Cluster Alarms discovery
Get alarm metrics about the state and its reason.
Preprocessing
- JSON Path: $.[?(@.AlarmName == «»)].first() ⛔️Custom on fail: Discard value
An explanation for the alarm state, in text format.
Preprocessing
- JSON Path: $.StateReason ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The state value for the alarm. Possible values: 0 (OK), 1 (INSUFFICIENT_DATA), 2 (ALARM).
Preprocessing
- JSON Path: $.StateValue ⛔️Custom on fail: Set value to: 3
- JavaScript: The text is too long. Please see the template.
Trigger prototypes for Cluster Alarms discovery
Alarm «» has ‘Alarm’ state.
Reason:
LLD rule Cluster Services discovery
Preprocessing
- JSON Path: $.services
- Discard unchanged with heartbeat: 3h
Item prototypes for Cluster Services discovery
The number of tasks currently in the running state.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The number of tasks currently in the pending state.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The desired number of tasks for an service.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
The number of task sets in the service.
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Discard unchanged with heartbeat: 3h
«A number of CPU units reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.»
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
«A number of CPU units used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined CPU reservation in their task definition.»
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1048576
‘The memory being used by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The memory that is reserved by tasks in the resource that is specified by the dimension set that you’re using.
This metric is only collected for tasks that have a defined memory reservation in their task definition.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1048576
‘The number of bytes received by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes transmitted by the resource that is specified by the dimensions that you’re using.
This metric is only available for containers in tasks using the awsvpc or bridge network modes.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes reserved from ephemeral storage in the resource that is specified by the dimensions that you’re using. Ephemeral storage is used for the container root filesystem and any bind mount host volumes defined in the container image and task definition. The amount of ephemeral storage can’t be changed in a running task.
This metric is only available for tasks that run on Fargate Linux platform version 1.4.0 or later.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1073741824
‘The number of bytes used from ephemeral storage in the resource that is specified by the dimensions that you’re using. Ephemeral storage is used for the container root filesystem and any bind mount host volumes defined in the container image and task definition. The amount of ephemeral storage can’t be changed in a running task.
This metric is only available for tasks that run on Fargate Linux platform version 1.4.0 or later.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
- Custom multiplier: 1073741824
‘The number of bytes read from storage in the resource that is specified by the dimensions that you’re using.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
‘The number of bytes written to storage in the resource that is specified by the dimensions that you’re using.’
Preprocessing
- JSON Path: The text is too long. Please see the template. ⛔️Custom on fail: Discard value
Get metrics of ESC services.
Preprocessing
- Check for not supported value ⛔️Custom on fail: Discard value
Trigger prototypes for Cluster Services discovery
The CPU utilization is too high. The system might be slow to respond.
The system is running out of free memory.
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide feedback, discuss the template, or ask for help at ZABBIX forums