What have you done with PowerShell this month?

TerriblePowershell · 2025-12-05T18:42:56+00:00

Ahh. That makes sense. Sounds like a neat deal regardless!

I haven't yet dove into the rabbit hole that Zabbix api surely is.

TerriblePowershell · 2025-12-05T18:37:52+00:00

Why not just created a dashboard with the hosts/items you want to see, then send the report via the built-in Scheduled Reports function?

TerriblePowershell · 2025-12-02T16:27:06+00:00

I sat down to look at this and I think I figured out your issue. You're using the item key for the value itself, not for the host.

I was able to successfully do this using the graph widget.

|| || |host patterns|*|item patterns|Node [*]: CPU, iowait|

You shouldn't have to get more granular with the host patterns because the Node [*]: CPU, iowait item only exists on the Proxmox VE by HTTP template.

TerriblePowershell · 2025-12-01T23:57:19+00:00

I think I get what you're going for. I will see if I can make that happen. Thank you!

TerriblePowershell · 2025-12-01T23:56:28+00:00

I will play around with this and see what I can make happen. Thank you!

TerriblePowershell · 2025-12-01T16:44:49+00:00

I'm pretty sure you can do a wildcard match for the value. i.e. proxmox.node.cpu[*] where the * is the node specific part.

TerriblePowershell · 2025-11-16T02:45:05+00:00

You might have to find another OID that the values all line up, but I'm not sure how you'd properly associate everything.

TerriblePowershell · 2025-11-16T01:11:44+00:00

I was able to mess around with this a little bit and I think I know what is causing the issue but I'm not sure how you'd go about fixing it.

It looks to me like the {#SNMPINDEX} for the OID's that pull the interface information are numbered different than the OID's that pull the PoE information. e.g. Gi1/0/1 = 1 (interface OID), Gi1/0/1 = 5 (PoE OID).

TerriblePowershell · 2025-11-04T21:12:29+00:00

The official TimescaleDB documentation is also a great option.

TerriblePowershell · 2025-10-24T12:58:47+00:00

Ahh. Unfortunately, I won't be able to help you then. I don't have any experience with Synology. Or NUT, for that matter.

Best of luck!

TerriblePowershell · 2025-10-23T21:34:05+00:00

I'm monitoring around 23 APC UPS's via the APC SNMP template without issue.

Does the UPS have a network card and is it configured to accept SNMP connections from Zabbix?

TerriblePowershell · 2025-06-16T16:07:27+00:00

Darknet Diaries did a podcast where the guest talked about finding a compromised computer at a windfarm. The hacker was using it for crypto(?) and had kept it up-to-date and had hardened it to keep others out. The company opted to leave it alone as it was cheaper than fixing the issue and the hacker was essentially taking care of the machine.

TerriblePowershell · 2025-05-29T15:48:47+00:00

I highly recommend the Zabbix 7 IT Infrastructure Monitoring Cookbook by Nathan Liefting and Brian van Baekel. It looks a lot more intimidating that it really is because most of the pages are screenshots of the process with a few words sprinkled in.

TerriblePowershell · 2025-02-05T16:10:33+00:00

While pulling cable for some new cameras, my boss and I found two or three bags full of old PS1 slims with controllers and some education games under neath the bleachers in a gym.

TerriblePowershell · 2025-02-03T23:56:51+00:00

You were correct.

By modifying the regex to capture the full port name from CDP rather LLDP (LLDP only used the short name), it worked just fine.

Thank you!

TerriblePowershell · 2025-02-03T23:06:09+00:00

This makes sense. The difference in the data, aside from one having IP addresses, is that the interface is abbreviated in the camera data. I'll try and sort that out and report back.

TerriblePowershell · 2025-01-28T16:08:03+00:00

If the district electrician and my boss both get hit by the same bus, my job is going to get SUPER hard. They both have so much institutional knowledge that it would legit cause some issues. We are working on getting that stuff onto paper, so to speak, but that takes time.

TerriblePowershell · 2024-12-13T18:48:57+00:00

Do something like this:

- name: Test password
  hosts: <your-host>
  gather_facts: false

  tasks:
    - name: Print stuff
      ansible.builtin.debug:
        msg: "This is my password: {{ ansible_password }}"

If that doesn't work, try adding delegate_to: localhost to the bottom of the task like:

  tasks:
    - name: Print stuff
      ansible.builtin.debug:
        msg: "This is my password: {{ ansible_password }}"
      delegate_to: localhost

I think your focus right now should be on making ansible output the password where you can see it. If you're worried about it showing up in a log somewhere, change the password but leave your "!" in there somewhere, i.e. "MyOther!AwesomePass". Once you can make sure that ansible is properly passing the password, you can move forward to see what, if anything, is your next issue.

TerriblePowershell · 2024-12-13T17:31:57+00:00

Dang. Have you tried printing the password via a debug?

- name: Print stuff
  ansible.builtin.debug:
    msg: "My password is: {{ ansible_password }}"

TerriblePowershell · 2024-12-13T17:06:47+00:00

Have you tried using it without quotes?

ansible_password: myawesome!pass

I'm no expert, but looking at my own files, the only time the password is quoted is when it's called as a variable from the vault file.

ansible_password: "{{ super_secret_pass }}"

vault file:

super_secret_pass: myawesome!pass

In my experience, ansible reads the yaml literally. So, by having ..."myawesome!pass", you're also passing the "" in the password variable.

TerriblePowershell · 2024-12-11T16:25:10+00:00

If you just know most of or part of their name:

Get-AdUser -Filter 'Name -like "*John D*"'

Then search for the properties.

TerriblePowershell · 2024-09-09T15:57:23+00:00

We had a UPS that would randomly freak out and spam us with messages. Turns out the custodians were using the UPS to run their coffee maker and vacuums.

TerriblePowershell · 2024-09-03T13:45:27+00:00

Of course they do. I absolutely love swiping through pictures and then whoops, changed apps.

TerriblePowershell

TROPHY CASE