Skip to content
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

Unnecessary cron jobs started when Monitoring is set on #3730

Open
matleppa opened this issue Mar 22, 2019 · 1 comment
Open

Unnecessary cron jobs started when Monitoring is set on #3730

matleppa opened this issue Mar 22, 2019 · 1 comment

Comments

@matleppa
Copy link
Member

General

After an API is connected to a Proxy, it is possible to set on Monitoring, which indicates, if API is responding to a GET method.

When the Monitoring is started, also a cron job for recurring sending of GET request is started.

Problem

Within starting cron job for Monitoring, also cron jobs related to collection of traffic data from Proxy via ElasticSearch are started.

In case ElasticSearch connection is not working properly, it leads UI freezing. In any case it is unnecessary functionality.

@matleppa
Copy link
Member Author

It seems, that autorun in apinf_packages\dashboard\client\analytic\body\body.js is triggered, when url is changed. Thus causing the requests to be sent to ElasticSearch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant