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
My idea simple in many cases you want see what happened on remote location while the dashboard in local or someware else it bit poinless the dashboard if you can setup remote monitor but love the idea
The text was updated successfully, but these errors were encountered:
glady just state i hope my english be good please tell if something you will not understood.
the idea is simple on paper.
it means you have dashboard that will act both as monitor system and as well collector that will collect all data from register agents.
the agent is what need be install in the actual project that will send the process both cli, job, what not.
why this impotent let say i have a project and it is on production and have more then 1 server or even worse it mircoservice system.
what this means that this package may not usable meaning if i dont have a unit that just do collecting of the raw data such as job , cli and more that means i may have security risk for the monitoring tool must be in secure site and not production what more this may create unneeded prefume on the server means once more unusable tool that can be kick ass.
that why i saying here agent that will package the data and send at (may save in s3, tcp,http, whatever) but he dont collect or process at just send
collector - can be within dashboard but may need support to detach at so can switch location and scale up / down he what do due process if needed and sync db
and dashboard (monitor / controller)
even later can add security thingy
My idea simple in many cases you want see what happened on remote location while the dashboard in local or someware else it bit poinless the dashboard if you can setup remote monitor but love the idea
The text was updated successfully, but these errors were encountered: