question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

When i want to launch elastalert

See original GitHub issue

Hello,

It’s my first post here, for my work i must install elastalert with elasticsearch.

WHen i load my rule its works, but when i want to lauch elastalert i’ve this error:

elastalert --config ../config.yaml --rule test.yaml Traceback (most recent call last): File "/usr/local/bin/elastalert", line 9, in <module> load_entry_point('elastalert==0.0.75', 'console_scripts', 'elastalert')() File "/usr/local/lib/python2.7/dist-packages/elastalert-0.0.75-py2.7.egg/elastalert/elastalert.py", line 1332, in main client = ElastAlerter(args) File "/usr/local/lib/python2.7/dist-packages/elastalert-0.0.75-py2.7.egg/elastalert/elastalert.py", line 90, in __init__ self.conf = load_rules(self.args) File "/usr/local/lib/python2.7/dist-packages/elastalert-0.0.75-py2.7.egg/elastalert/config.py", line 362, in load_rules raise EAException('Invalid time format used: %s' % (e)) elastalert.util.EAException: Invalid time format used: type object argument after ** must be a mapping, not NoneType

If you have an idea to help me, thanks a lot !

Have a nice day !

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
Qmandocommented, Mar 22, 2016

timeframe must be of the format

timeframe:
  hours: 4

or

timeframe:
  days: 1

or similar. If you don’t include the spaces before days/minutes/hours/etc, it will not be parsed correctly.

0reactions
Qmandocommented, May 17, 2018

You get Invalid time format used: type object argument after ** must be a mapping, not NoneType from that config? That file looks correct as it’s posted here.

It’s possible that one of the other time options is messed up in the global config.yaml? Something like buffer_time or alert_time_limit?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Running ElastAlert for the First Time - Read the Docs
The default run_every is 5 minutes, meaning ElastAlert will sleep until 5 minutes have elapsed from the last cycle before running queries for...
Read more >
Powerful alerting with ElastAlert 2 - Documentation OVH
Launch ElastAlert ​​ If you send this event more than 3 times, the elastalert process will try to send an alert to the...
Read more >
ElastAlert Tips & Tricks - Auto1 Tech Blog
In this article I want to explain some of the common questions we have asked ourselves while rolling out elastalert: How do buffer_time,...
Read more >
Elastalert: How to run rule periodically - Stack Overflow
The above example to start elastalert use the timestamp of format ISO8601 and is in UTC. You can use your timezone like YYYY-MM-DDTHH:MM:SS-08: ......
Read more >
Yelp/elastalert - Gitter
Hey anyone here, i have few doubts for elast alert slack notification and need ... but it loads the rule and cca after...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found