Can we integrate multiple Zabbix Dashboards into a Single Dashboard for Monitoring?
Like i have an instance in X Location and other in Y Location. I need to show a dashboard to management with all the available triggers.
Thanks in advance.
I suggest a single Grafana with multiple Zabbix datasources.
You can set up a single dashboard or multiple dashboards with graphs and trigger from multiple sources, quick host/item/server selection with templating etc...
Below are the 2 solutions which i found to integrate different Zabbix environments.
Grafana tool need to be installed and all the Zabbix instances data need to be pushed to Grafana for visualization. In this method we are getting data from API.
For all the Zabbix database a web socket need to be built and push the data to a Redux store and built a React UI, so that only changed data will be available in the UI.
Related
Will you Please help me in one more important thing??? I need to store dashboard's data in a database.. according to my study thingsboard supports 3 database at the moment. NoSQL, Mysql and Hybrid (Psql+cassandra) so i have researched a lot but could not find any way to send my telemetry data to any database. I know it is possible because the thingsboard doc itself say so... but how do i do that?? I checked Psql database thingsboard that i created during installation but there are those relations are present that was made by default. i need to store my project's data in databases just like in AWS we store IoT core's data in Dynamo DB or in IoT analytics. Thingsboard do not provide any node related to DB in his rule engine?? so How do i make a rule chain to transfer my projects data in any Database server. i have installed pgadmin4 to Graphically see the database but nothing useful found. Documentation and stakoverflow geeks said that configuring Thingsboard.yml file located in monolithic installation on linux (/etc/thingsboard/conf/thingsboard.conf ) in this path it have cassandra,mysql,postgres configuration but how to properly configure it??? i tried to access the default database of postgres named thingsboard that i created on installing time but when i list the content of database it only shows the default things/relations of thingsboard if i create a device on thingsboard that is not showing in database why?? I really can use your help. Please enlighten me a way to connect my THINGSBOARD with a DATABASE.
see in my attached images there are everything default, nothing that i create on thingsboard.
enter image description here
That's wrong, ThingsBoard currently supports 3 database setups: Postgres only, Hybrid Postgres + Cassandra (only telemetries) & Postgres + Timescale. So there is no MySQL database used anywhere.
https://thingsboard.io/docs/user-guide/install/ubuntu/#step-3-configure-thingsboard-database
Find guides for connecting your devices to Thingsboard here, e.g. via MQTT:
https://thingsboard.io/docs/reference/mqtt-api/
If you would like to forward the stored telemetries of ThingsBoard to different databases, this is not possible directly with rulechains (there's only one node to store data in a cassandra table)
One way to achieve this, would be fetching the data with an external microservice/program via HTTP API and persisting the data in the database of your choice. You could use a python script for example.
https://thingsboard.io/docs/reference/rest-api/
Alternatively, you can send the data to a Message queue like Kafka instead of fetching via HTTP API. But still it would require additional tools for storing the data in external databases outside ThingsBoard.
Is it possible to have logical separation of Azure APIM service i.e one could work like Prod and Non-Prod at the same time?
If you check this Azure API Management DevOps Resource you would find that Microsoft recommends to use separate Azure API Management service instances for various environments, such as production, development, and QA. Where these environments are generally shared by multiple development teams, each responsible for a subset of APIs. It is the best practice for the enterprise setup.
But if you don't want to create multiple instances then, you could try using versions and revisions.
You can create revisions by right clicking API and click "Add Revision".
Similarly you can create versions by right clicking API and click "Add Version".
For more information check this answer by #DSpirit on the similar problem shared in Stack Overflow.
I have just created a Project in Google Cloud, and attached a Cloud SQL Database instance to that project. I was able to deploy a Django app that is connected to that DB just fine.
However, I would like to create a separate Django app/Project that is attached to the same Cloud SQL Database that my first Django app is attached to.
Is this possible?
One Django app is responsible for web scraping and supplying constant data to the database while my second Django app (the one I have already deployed) analyzes and returns json on that data. It would be advantageous to separate the two apps because if I ever needed to revise my web scraping algorithm, the whole app would not be down.
You can use cloudsql proxy for both apps. Also as long as you authorize both of your applications with service account that have access to the cloudsql it should be fine.
You can use database that you want, in your current project or in an external one. If you use Cloud SQL proxy, the service account of your app
Either Default AppENgine service account if on App Engine
Or Compute Engine default service account
except is you have defined a specific service account on your component (Cloud Run, Compute engine)
I recommend strongly to use a specific service account on the component if it's possible (not possible with App Engine)
The role to grant on the service account is the following: roles/cloudsql.client
However, I recommend you to smartly think to your design. The current trend is to lock 1 database to 1 service (or microservice).
Think about the schema update: a synchronous update will be required between to 2 services when you update the schema or one, or the other app will fail.
Same thing in case of rollback, both apps need to be rollbacked.
If there is 2 teams, one on each app, their release planning must be sync, and you will lost in velocity and agility.
Maybe, it fits your requirement, or you can duplicate the data, inside the database (other schema). As you wish.
I am trying to implement a device with a few sensors that will send their values in an Azure database using an WP8 app and Azure Mobile Services. While the hardware part will be done, I want to somehow simulate this whole process. Meaning that I want to have an app that will generate some random values at an interval of 1s and upload these values in the cloud.
So my question is: what would be the best approach to do this?
Best regards.
I think that you should create Sensors Reader abstraction layer. In the release version, you'll read the real data, but in the test version you can generate data or receive the data over the network (for example) from the generator app. Azure db have the local simulator too. So, I see no problem in your case.
We are using OpenMRS in Amazon EC2 .Can the Parse.com to make only notifications database or The Entire database to be build on Parse.com.
If it is So.We will be using the Google Messaging Cloud.
Parse's push offering can be augmented with other features (i.e. advanced targeting based on relationships with users or other data stored with Parse), but it is designed to work as a standalone feature.