Difference between revisions of "ApiKey"
Jump to navigation
Jump to search
(→Errors) |
(→Errors) |
||
Line 9: | Line 9: | ||
a512267c-11111-4d6b-b913-b611111a495e | a512267c-11111-4d6b-b913-b611111a495e | ||
Error occurred with Status code: 422, Message: Key format is not valid!, Took: 0.001000, RequestId: a511167c-1693-4111b-b913-111111e | Error occurred with Status code: 422, Message: Key format is not valid!, Took: 0.001000, RequestId: a511167c-1693-4111b-b913-111111e | ||
+ | |||
+ | |||
+ | opsgenie-lamp listAlerts --config ~/.config/lamp.conf | ||
+ | INFO[202-10-11T18:35:30.033491+02:00] Client is configured with ApiUrl: api.opsgenie.com, RetryMaxCount: 4 | ||
+ | ERRO[202-10-11T18:35:30.344369+02:00] Error occurred with Status code: 422, Message: Key format is not valid!, Took: 0.000000, RequestId: | ||
+ | 7311bc6-111121-498d-b420-ce111111bc | ||
+ | Error occurred with Status code: 422, Message: Key format is not valid!, Took: 0.000000, RequestId: 73111c6-1321-411d-b110-ce1111bc | ||
== Related == | == Related == |
Revision as of 16:36, 11 October 2024
~/.config/lamp.conf
Errors
opsgenie-lamp listAlerts -apiKey=ATATT3xxxxxpjzmo ERRO[204-10-11T18:30:08.066948+02:00] Error occurred with Status code: 422, Message: Key format is not valid!, Took: 0.001000, RequestId: a512267c-11111-4d6b-b913-b611111a495e Error occurred with Status code: 422, Message: Key format is not valid!, Took: 0.001000, RequestId: a511167c-1693-4111b-b913-111111e
opsgenie-lamp listAlerts --config ~/.config/lamp.conf INFO[202-10-11T18:35:30.033491+02:00] Client is configured with ApiUrl: api.opsgenie.com, RetryMaxCount: 4 ERRO[202-10-11T18:35:30.344369+02:00] Error occurred with Status code: 422, Message: Key format is not valid!, Took: 0.000000, RequestId: 7311bc6-111121-498d-b420-ce111111bc Error occurred with Status code: 422, Message: Key format is not valid!, Took: 0.000000, RequestId: 73111c6-1321-411d-b110-ce1111bc
Related
See also
Advertising: