Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PreviousLevel in a Lambda #2751

Open
izenn opened this issue Mar 24, 2023 · 0 comments
Open

PreviousLevel in a Lambda #2751

izenn opened this issue Mar 24, 2023 · 0 comments

Comments

@izenn
Copy link

izenn commented Mar 24, 2023

I'm trying to write an alert where there is Critical, Warning, Info and OK. I'm running into an issue where the cpu usage will occasionally go between ok and info and i do not want to be alerted if that happens, but i do if it goes from warning down to info. It looks like there might be a way to get PreviousLevel (i've seen it here: #2668 and #2715 (where there looks to be "previousLevel" available.

I'm not seeing that in my data:
{"Name":"","TaskName":"test-task","Group":"host=xxxxxx","Tags":{"host":"xxxxxx"},"ServerInfo":{"Hostname":"localhost","ClusterID":"xxxxxx","ServerID":"xxxxxx"},"ID":":host=xxxxxx","Fields":{"cpulist":"cpu0","status":"CHECK","timeframe":"30 minutes","used":0.16255418860727153},"Level":"INFO","Time":"2023-03-24T17:30:59.663545193-05:00","Duration":10797827655742,"Message":":host=xxxxxx is INFO"}

is there a way to get previous level when using a batch query so i can put some extra logic in my info alert?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant