This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About LLibarios
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About LLibarios
10-16-2019
2Posts
0Likes
0Solutions
Oct 16, 2019Last Visited
User
Activity
User
Profile
Latest posts by LLibarios
| Subject | Views | Posted |
|---|---|---|
| 6239 | 10-16-2019 05:43 AM | |
| 6292 | 10-15-2019 04:32 AM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 1 Like |
User Badges
Community Statistics
| Member Since | 09-30-2019 08:52 AM |
| Date Last Visited | 10-16-2019 09:09 AM |
| Posts | 2 |
10-16-2019
05:43 AM
Thanks on your response, I've solve it via removing " dismissalTimeRange " on parameter. i don't have any idea why it does not work having that on parameters. Thanks!
... View more
10-15-2019
04:32 AM
Anyone have experience using the Prisma Cloud API with dismissing alert, i've been testing the but always getting 404 or 400 response, check parameters below
url = "https://api.prismacloud.io/alert/dismiss"
payload = {
"alerts" : [param.get( "alert_id" )],
"dismissalTimeRange" : {
'type' : 'absolute' ,
'value' : {
'startTime' : 0 ,
'endTime' : end_time
}
},
"filter" : {
"timeRange" : {
'type' : 'absolute' ,
'value' : {
'startTime' : 0 ,
'endTime' : end_time
}
},
"limit" : "1" ,
"detailed" : "true"
}
}
been looking on the community but not found any good solutions.
... View more
- Tags:
- prisma cloud
Labels:
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
10-16-2019
09:09 AM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks