[Bug]: Perfdata inconsistency

[martialblog]

Please try to fill out as much of the information below as you can. Thank you!

• Yes, I've searched similar issues on GitHub and didn't find any.

Which version contains the bug?

0.2.0

Describe the bug

The perfdata output is inconsistent:

go run main.go alert -T 2 --name foo
[UNKNOWN] - 0 Alerts: 0 Firing - 0 Pending - 0 Inactive

go run main.go alert -T 1 --name foo --name NodeHasMemoryPressure
[OK] - 1 Alerts: 0 Firing - 0 Pending - 1 Inactive
\_ [OK] [NodeHasMemoryPressure] is inactive
|total=1 firing=0 pending=0 inactive=1

When there are no alerts found, there is no output.

How to recreate the bug?

No response

[martialblog]

Now that I think of it, maybe it's fine because if nothing is found there maybe should not be perfdata 🤔

[martialblog]

I'll at least do a review and see if everything is consistent.

[martialblog]

Yeah, this won't do:

# With alerts defined:

$ go run main.go alert 

[OK] - 1 Alerts: 0 Firing - 0 Pending - 1 Inactive
\_ [OK] [NodeHasMemoryPressure] is inactive

$ go run main.go alert -P

[UNKNOWN] - 0 Alerts: 0 Firing - 0 Pending - 0 Inactive

exit status 3

# With nothing defined:

$ go run main.go alert
[OK] - No alerts defined

$ go run main.go alert -P
[OK] - No alerts defined

We should see perfdata when there are alerts defined.