This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

Is there something more than editing of the agent's default.yaml that's necessary to get spikearrest working?

Posted on 10-05-2015 11:36 PM
Not applicable
Reply posted on --/--/---- --:-- AM

I'm trying to get version 1.0.0 to work but am not seeing spikearrest fire. I've tried both minute and second and am blasting the endpoint with loads of hits.

0 1 119
Topic Labels
0 Likes
1 REPLY 1

Posted on --/--/---- --:-- AM
Not applicable
Reply posted on --/--/---- --:-- AM

Spikearrest is configured by setting these properties (for example) -

spikearrest:
  timeUnit: minute
  allow: 10

The agent has to be restarted to pickup changes to config/default.yaml. After restarting the agent, ensure the changes are picked up by examining the cached config in /var/tmp/edgemicro-config-<org>-<env>.yaml.

After restarting the agent, spikearrest should work. If still not working, try restarting Edge Micro with DEBUG enabled -

$ edgemicro agent proc -c ls

[{"pid":8092,"uid":"MTQ0NDE2NTU5MDkwNQ","running":true,"restarts":0,"since":"2015-10-06T21:06:30.913Z"}]

$ edgemicro agent proc -c stop -u MTQ0NDE2NTU5MDkwNQ

{ uid: 'MTQ0NDE2NTU5MDkwNQ',
  running: false,
  since: '2015-10-06T21:06:30.913Z' }

$ edgemicro agent proc -c start -k <key> -s <secret> -e DEBUG='*'

Note the extra -e (env) option. This will print a lot of debug output to the console which will help us identify the problem.

0 Likes