I installed Fastnetmon community edition using this guide: https://fastnetmon.com/install/
I then continued on to this guide to create a database and display them in a dashboard: https://fastnetmon.com/docs/influxdb_integration/
NOTE: I want to point out that Ionly used the first version of influxdb and not influxdb2 because influxdb2 doesn't seem to support graphite anymore. The guide in the second link that I sent will redirect you to install influxdb2.
Everything went well except for one thing. The networks that I put in graphite is not appearing for some reason.
Screenshot from the guide:
Screenshot from the guide
Screenshot of my results: Screenshot of my results
Networks is not appearing which means I cannot pull any data from it. Anyone has any idea why it is not showing?
Update: I had it working after enabling the network counters in fastnetmon.conf file.
Related
I have started using Apache Zookeeper and I want to know what kind of errors/problems could pop up
while using Zookeeper.
I've been looking online and couldn't find real common errors/problems.
For example, how should I handle high latency if I encounter this problem?
In addition, I found some metrics regarding Zookeeper such as:
open file descriptors, outstanding requests, pending syncs request and more,
But there is no info online on how to solve/handle these issues.
If someone has some experience I would be glad if you could share about your Zookeeper issues or any error-handling solutions.
I tried researching online with no luck.
I'm currently trying to make the Connector Device work with ROS. My first step was to just take one of the robots of the "connector.wbt" world and place it in a new world and switching the robots controller argument to "ros"as one can see below.
When I run the simulations all ROS services are advertised as expected. In the next step I enable the Connector using its corresponding service, where an integer needs to be specified (presence check Time Step) //presence_sensor/enable service as shown below:
Now the topic is enabled, however no messages are published, while I'm expecting to see messages of type "webots_ros/Int8Stamped", which should give me zeros for the absence of a suitable connector.
Is there any idea if the problems lies on my side? Is the Connector-Ros-Interface working properly for you if you recreate the above example?
You are completely right, there was indeed a problem with the ros-connector interface.
This has been fixed just now here:
https://github.com/omichel/webots/pull/672
This fix will be included in the nightly build of today (R2019b revision 1, available from tomorrow morning) that you can find here:
https://github.com/omichel/webots/releases
Let us know if there are still problems.
As the title says, whats the correct way to configure an IoTEdge Module to report data to Remote Monitoring?
Actually I have a custom module running on an IoTEdge device that is working correctly (I can check that is working properly by looking at the docker logs of the module) , but its not transmitting anything to the Remote monitoring dashboard, by the way the device is listed on the available devices on the Azure Remote Monitoring but it is offline. I suppose that it depends on the MessageSchema and MessageTemplate that are not configured. I can't find any specific documentation about this topic, can anyone point me in the right direction?
Are you asking about the original V1 version of the remote monitoring solution, or the newer V2 version? If it's the original version, you would need to, at least once, send a DeviceInfo structure (https://learn.microsoft.com/en-us/azure/iot-suite/iot-suite-v1-remote-monitoring-device-info#device-metadata) to the IoTHub associated with the solution. I haven't tried it yet, but it should work for the edge device (I don't think it would have an issue with the module concept). If it's the V2 version, I would need to investigate further.
Does anyone know of an elasticsearch client library for iOS? Would be a bonus if it was written in swift as well.
The elastic search 'clients' section shows multiple libraries for a number of platforms but nothing for iOS, I feel like someone must have done this?
Cheers
I doubt that anyone has - last time I checked there were none and for good reasons. Keep in mind that in order to allow an IOS client (or Android for that matter) to use a client library to connect to Elasticsearch you'd have to open up your cluster for either an http or node access - which would allow anyone to do anything to your cluster.
Maybe you could proxy it to prevent deletions and insertions but even so it would open up your cluster's data and open you up to DoS attacks.
Generally a better idea is to create your own REST API that incorporates some type of authentication and authorization and does not open up your cluster to the world.
If you still feel strongly about moving forward you can always just hit the http interface of the REST API for ES. Or take a look at this project someone was working on a few years ago at least to give you a head start:
https://github.com/tallpsmith/ElasticSearchIOSHead
Some recent discussions on this topic:
http://elasticsearch-users.115913.n3.nabble.com/Objective-C-client-for-ElasticSearch-iphone-ipad-etc-td3911216.html
Running Elasticsearch server on a mobile device (android / iphone / ios)
This may be what you're looking for. ElasticSwift. Seems to be in active development but haven't looked deep into how far they've gone.
This is another iOS Swift client that was made back in 2018: Appbase-Swift. It's a lightweight ElasticSearch/appbase.io client. Doesn't seem like it's been updated in awhile though.
We tried a lot for elastic and finally concluded that it on most of the challenging side. another thing is a bit bulky to use on mobile, as per my understanding no room for the optimization. We can only use HTTP Web Service call for the same service. Also, the flavor of the offline search can not be implemented in the mobile elastic till date...
We're using TFS Build Server to ensure that all files checked in by developers are going to compile to a working source tree, cuz there's nothing worse than a broken build!
Anyway we've having some problems with the drop location that Build Server wants to use, we keep getting this error:
TFS209011: Could not create drop location \build-server\drops\project\BuildNumber. No more connections can be mades to this remote computer at this time because there are already as many connections as the computer can accept
Since this is being used in a pilot program at the moment we only have 2 projects which are using the Build Server. I've checked the network share and the allowed number of connections is about 100 so I don't really get what the problem is.
Only occationally does the problem raise it's head, quite often we'll not have one for days, and then we'll have a bunch in a row.
I can't seem to find much info on this either.
I'm pretty good with TFS - but a dev not a network guy. I would GUESS that while the NETWORK SHARE itself allows 100 connections, is it possible the underlying server it is running on doesn't have some sort of limitation?
Have you checked event logs?
This problem seems specific enough I would encourage you to post to the official Microsoft forums.
It looks like the problem is to do with our install of Windows 2003, we have "Web Edition" installed and it is limited to just 10 connections.
I ended up with a post of the MSDN forums in which I got this answer: http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3967598&SiteID=1&mode=1