-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
get-sensor error with filter on tag 'imap' #317
Comments
Can you please reproduce the issue and provide the output of |
PS> Get-Sensor -Type IMAP PS> $error[0].Exception.StackTrace |
Can you do Set-PrtgClient -LogLevel Response
Get-Sensor -Type IMAP |
PS /> Set-PrtgClient -LogLevel Response PS /> Get-Sensor -Type IMAP |
PS /> get-prtgclient Server : * |
Apologies, I wrote the command wrong, it should be Set-PrtgClient -LogLevel Response
Get-Sensor -Type IMAP -Verbose |
Here is a shortened answer:
|
The issue appears to be that the <intervalx>@32400</intervalx> What does the scanning interval show as in the PRTG UI? And does this scanning interval configured inherit from a parent object, or is it directly defined on these sensors? Do you have this issue retrieving other sensor types? |
The scanning interval is configured on the sensor with a specific format to plane a unique check based on an hour. ex: "@ UTC 09:00" And no, with other sensor type it works well. |
Are you able to show a screenshot of how you configured it to scan "@ UTC 09:00" in the user interface of PRTG? |
Thanks @senhub-io, I was not aware of this feature; I will have to look at how to deal with this; in the meantime, you can potentially still retrieve objects set to run at specific times by doing |
you're welcome! In the meantime we used the native APIs. Thank you! |
Describe the bug
Hello,
When I request my prtg core with this request I get an unexpected error.
Thank you for your help,
Matthieu
Steps to reproduce
What is the output of 'Get-PrtgClient -Diagnostic'?
Additional context
No response
The text was updated successfully, but these errors were encountered: