Відео

Sorry about that, thank you for the feedback I'll certainly keep it in mind for future videos, genuinely appreciated. 👍

Thank you! Certainly...at some point I'll try and get a video tutorial for this as I'm using a few plugins on Netbox Docker.

@@seesteps Please make this video for us. Your videos are of great quality.

Hi Francisco, thank you! appreciate the comment...I'll certainly try and get a video up as soon as possible...

You can leave the argument blank if you wish to use the default setup, however if you want to set where you want your Prometheus data or retention period then you need to put in the flags within the argument section. I've put the below within the description of the video but for reference these are the flags I used. NSSM Prometheus Data Location Flag: --storage.tsdb.path="Location" NSSM Prometheus Data 90 days Retention Flag: --storage.tsdb.retention.time=90d NSSM Prometheus - Enable Time Series Deletion (you don't need this, I needed to delete some data so I enabled it): --web.enable-admin-api

Hi Ryan I have not come across this issue or had it come to my knowledge, looked through Paxton Net2 knowledge base and I could not find anything specific to an unzip error. There shouldn't be a DB compatibility issue. * I'm assuming the Net2 app is not being installed on a domain controller? The only reason, this is not supported. * If you're installing it on Windows Server 2022 or Windows 11, then version v6.6 SR1 should be installed (minimum recommended version). * I would have said is Net2 lite installed prior to DB restore but if the video was followed then that is ruled out. * Is there any further information being shown on event logs? I would recommend to review the database on the old server if possible and see if there are any issues or contact Paxton Support (in my personal experience they are good at responding) as I have a feeling the database is not zipping correctly. Feel free to update as it would be good to know for future knowledge.

@@seesteps Big thanks sir. . i think you're right something's wrong with the old backup, I'll create a new backup and follow again the steps, regarding the door license since its a new server will it ask for an update as well? by d way, may i know what's the default sa password of the SQL server 2012 express sp4? many thanks..

No worries, hopefully you get it sorted. Do reach out to Paxton Support they are generally good in giving back a response. In regard to the SA account, last time I checked Paxton by design does not provide this information.

Thank you so much. It certainly gives me motivation, appreciated.

Hi, There is a chance that docker was already pre-installed on your Ubuntu OS (correct me if I'm wrong). I would uninstall/purge docker completely and then reinstall docker (as per the video). Let me know how you get on..

Hey, Thank you for the comment... regarding the error, if I recall it's usually related to your network. Where the scraping is taking too long and is timing out before it completes. You could troubleshoot and eliminate this possibly being the issue by testing the following, on the Prometheus configuration yaml file, amend it by adding the below, scrape interval and timeout (increase the time, if needed): scrape_configs: - job_name: 'Windows Exporter' scrape_interval: 3m scrape_timeout: 1m Let me know how you get on...

Local Firewall allow application policy had to be enabled.

Good to read you resolved the issue.

Hi Praveen, The Prometheus version within the video was: 2.51.1 Personally I haven't had any issues in the past requiring the Prometheus application to be at a certain version for windows exporter collector to work, but let me know if this is the case for you, I doubt it will be down to the version.

Hi Mike, Alert Manager should appear as a data source within Grafana as it's built into the Grafana Application. Here is a reference guide to the Grafana KB, it will even allow you to configure it via the config file if needed: grafana.com/docs/grafana/latest/datasources/alertmanager/ If it's still failing to appear, I would suggest reinstalling (if not done already). If I've misunderstood, do let me know.

Hi Amit, Appreciate the comment, certainly will take your feedback on board, I usually try by pinning or place config files for apps via GitHub. Commands I usually place for my Linux videos but I understand in hindsight it is probably equally as important to place cmds and URLs for these videos, irrespective. At some point I'll update these videos...Thanks again...

Glad I could help! 👍

Hi, You can certainly download Grafana "offline", I've left a link of my first video I created for Grafana - ua-cam.com/video/4-YZajsXukI/v-deo.html You can either host it on the same server as where your Prometheus application is or you can install it on a dedicated server. The choice is yours....hope this helps. Please do like or subscribe, it helps and keeps me motivated to carry on making future videos, appreciated.

@@seestepsthanks of quickly responce, but i mean i want to download grafana to pc,can’t access to internet

Grafana & Prometheus can operate offline and continue to scrape and collect data, provided that you can communicate within your local network between the Grafana/Prometheus server and the Prometheus Windows Exporter Agent. With the above in mind, you will need to download the MSI/EXE and then transfer it to the necessary machines/VMs e.g. using a USB. If I've misunderstood, do let me know.

@@seestepsi got it ,thank you so much 🤍🤍

Glad to hear that it was of help!

Hi! I'm assuming devices like UDM Pro and UDM SE? If so, I'm not sure if this would work...well I've never tried it to be honest. I remember coming across a thread once on Reddit and someone managed to get it working using "Glens" script (same as the video), but the method was not the same.

Merci, apprécié

I'll give this solution a go since my own paid certificate is no longer accepted and even breaks the controller

@@diederikmaes2367 Je l'ai installé sur mon vps unifi déja existant depuis longtemps et ça a fonctionné du premier coup !

Hi, thank you for watching the video :) appreciated. I've never had the need to change the timezone (would be something new to me), however I've found a discussion thread on netbox-docker GitHub, which looks to be straight forward, you would need to edit the docker.compose.override.yml file github.com/netbox-community/netbox-docker/discussions/760 If you're still unable to change the timezone, let me know and when I get a chance I'll create a short video, assuming I'm also successful :D

Hi, In order to create cable and interface connections via the GUI, you need to create the devices first and then the interfaces for those devices and then link them with all the relevant devices, at which point netbox should populate this for you, netbox will not allow you create an individual cable using a "+" sign or on network interface. You can use the import function for cables but it will require various information within the .CSV e.g. device name, termination type, termination name etc. you can view this by clicking the import button and then scrolling down where it says field options and it will show you the "required" info the .CSV file must have.... Hope the above helps.

I thought I would update this reply, Netbox since version 3.7.8, has enabled the ability to add new cables directly from the navigation menu.

No additional steps are required, KVM does not need to be enabled. Though the video has been speeded up to shorten the video, the video shows all the steps, start-to-finish on a "fresh/out-of-the-box" Ubuntu VM.

Perfect, nice to read you resolved the issue and also that the video has been of some help in your implementation as a guide. Appreciate the view.

Is it normal for the output of "docker compose up" to take over an hour?

If the output is the same as the video, then the container is already up and attached, if you leave it up for an hour it's essentially just showing you the current logs. It's not normal for it to take an hour. You need to exit out to the shell. To do this, without shutting down the container is to either close your terminal session as I did, as the shortcut keys was not working for me when using "Putty" or if it works for you, the shortcut is "Ctrl + P then Ctrl + Q". Hope the above helps.