You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional Info
Instead of making different api calls depending on the type of object requested it may be simpler to have the UI remain the same but store host and serviceElement Type's as filters.
eg: Select Element TypeHost and select my_server.example.com from the list.
This is stored and executed as a host filterhost.name=="my_server.example.com"
Meerkat Version = 3.1.0
The text was updated successfully, but these errors were encountered:
Fix: #219 Call correct parameter's for host requests
Fix: #220 Make dashboard elements for host based objects return correct mapping for Up/Down based on check state.
Fix: Fix problem with frontends where loss of connect to Meerkat caused the frontend to spam requests at a unreasonable rate.
Fix: version flag (really build string) in Meerkat to report correct build string
---------
Co-authored-by: 63 <55000067+63@users.noreply.github.com>
Describe the bug
Elements that use
Element Type = Host
make malformed api calls.To Reproduce
Steps to reproduce the behavior:
Element Type
ofHost
if you look in the logs the api call for this element is
Expected behavior
The api call to get a host are
https://icinga:5665/v1/objects/hosts/my_server.example.com
https://icinga:5665/v1/objects/hosts?hosts=my_server.example.com
Additional Info
Instead of making different api calls depending on the type of object requested it may be simpler to have the UI remain the same but store
host
andservice
Element Type
's as filters.eg: Select
Element Type
Host
and selectmy_server.example.com
from the list.This is stored and executed as a
host filter
host.name=="my_server.example.com"
The text was updated successfully, but these errors were encountered: