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.

Sign up for GitHub

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

Jump to bottom

wso2 analytics 3.2.0 alert issue #1476

Closed
kalevivek11 opened this issue Nov 23, 2020 · 2 comments
Closed

wso2 analytics 3.2.0 alert issue #1476

kalevivek11 opened this issue Nov 23, 2020 · 2 comments

Comments

@kalevivek11
Copy link

we are using wso2 analytics 3.0.0, we are testing functionality analytics alerts, all the alerts are generating except
"backend response time and abnormal response time" we have done all the configurations as per documentation
Also, mails from analytics worker are not generating other than Gmail domain
Please provide your inputs.
@kalevivek11
Copy link
Author

Analytics worker logs

04:10:39
[2020-12-02 04:10:39,110] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_ACCESS_SUMMARY deployed successfully
[2020-12-02 04:10:39,110] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_ACCESS_SUMMARY deployed successfully

04:10:39
[2020-12-02 04:10:39,238] INFO {io.siddhi.core.aggregation.IncrementalDataPurger} - Data purging has enabled for tables: SECONDS,MINUTES,HOURS,DAYS,MONTHS, with an interval of 3600 seconds in ApiThrottledOutAgg aggregation
[2020-12-02 04:10:39,238] INFO {io.siddhi.core.aggregation.IncrementalDataPurger} - Data purging has enabled for tables: SECONDS,MINUTES,HOURS,DAYS,MONTHS, with an interval of 3600 seconds in ApiThrottledOutAgg aggregation

04:10:39
[2020-12-02 04:10:39,242] INFO {io.siddhi.core.aggregation.IncrementalDataPurger} - Data purging has enabled for tables: SECONDS,MINUTES,HOURS,DAYS,MONTHS, with an interval of 3600 seconds in APIM_ReqCountAgg aggregation
[2020-12-02 04:10:39,242] INFO {io.siddhi.core.aggregation.IncrementalDataPurger} - Data purging has enabled for tables: SECONDS,MINUTES,HOURS,DAYS,MONTHS, with an interval of 3600 seconds in APIM_ReqCountAgg aggregation

04:10:39
[2020-12-02 04:10:39,243] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_THROTTLED_OUT_SUMMARY deployed successfully
[2020-12-02 04:10:39,243] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_THROTTLED_OUT_SUMMARY deployed successfully

04:10:41
[2020-12-02 04:10:41,229] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_EVENT_RECEIVER deployed successfully
[2020-12-02 04:10:41,229] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_EVENT_RECEIVER deployed successfully

04:10:41
[2020-12-02 04:10:41,354] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_unusual_ip_access_0 deployed successfully
[2020-12-02 04:10:41,354] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_unusual_ip_access_0 deployed successfully

04:10:41
[2020-12-02 04:10:41,452] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_abnormal_request_pattern_0 deployed successfully
[2020-12-02 04:10:41,452] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_abnormal_request_pattern_0 deployed successfully

04:10:41
[2020-12-02 04:10:41,513] INFO {io.siddhi.core.aggregation.IncrementalDataPurger} - Data purging has enabled for tables: SECONDS,MINUTES,HOURS,DAYS,MONTHS, with an interval of 3600 seconds in ApiFaultyInvocationAgg aggregation
[2020-12-02 04:10:41,513] INFO {io.siddhi.core.aggregation.IncrementalDataPurger} - Data purging has enabled for tables: SECONDS,MINUTES,HOURS,DAYS,MONTHS, with an interval of 3600 seconds in ApiFaultyInvocationAgg aggregation

04:10:41
[2020-12-02 04:10:41,513] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_FAULT_SUMMARY deployed successfully
[2020-12-02 04:10:41,513] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_FAULT_SUMMARY deployed successfully

04:10:41
[2020-12-02 04:10:41,540] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_API_AVAILABILITY deployed successfully
[2020-12-02 04:10:41,540] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_API_AVAILABILITY deployed successfully

04:10:41
[2020-12-02 04:10:41,543] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_STAKEHOLDER_ALERT deployed successfully
[2020-12-02 04:10:41,543] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_STAKEHOLDER_ALERT deployed successfully

04:10:41
[2020-12-02 04:10:41,620] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_abnormal_response_time_0 deployed successfully
[2020-12-02 04:10:41,620] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_abnormal_response_time_0 deployed successfully

04:10:41
[2020-12-02 04:10:41,626] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_CONFIGURATION_ALERT deployed successfully
[2020-12-02 04:10:41,626] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_CONFIGURATION_ALERT deployed successfully

04:10:41
[2020-12-02 04:10:41,651] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_frequent_tier_limit_hitting_0 deployed successfully
[2020-12-02 04:10:41,651] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_frequent_tier_limit_hitting_0 deployed successfully

04:10:41
[2020-12-02 04:10:41,817] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_PERSIST_ALERTS deployed successfully
[2020-12-02 04:10:41,817] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_PERSIST_ALERTS deployed successfully

04:10:41
[2020-12-02 04:10:41,907] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_abnormal_backend_time_0 deployed successfully
[2020-12-02 04:10:41,907] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_abnormal_backend_time_0 deployed successfully

04:10:41
[2020-12-02 04:10:41,953] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_abnormal_request_count_0 deployed successfully
[2020-12-02 04:10:41,953] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App apim_alert_abnormal_request_count_0 deployed successfully

04:10:42
[2020-12-02 04:10:42,213] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_ALERT_EMAIL_NOTIFICATION deployed successfully
[2020-12-02 04:10:42,213] INFO {org.wso2.carbon.streaming.integrator.core.internal.StreamProcessorService} - Siddhi App APIM_ALERT_EMAIL_NOTIFICATION deployed successfully

04:10:42
[2020-12-02 04:10:42,222] INFO {org.wso2.carbon.kernel.internal.CarbonStartupHandler} - WSO2 API Manager Analytics Server started in 20.495 sec
[2020-12-02 04:10:42,222] INFO {org.wso2.carbon.kernel.internal.CarbonStartupHandler} - WSO2 API Manager Analytics Server started in 20.495 sec

@kalevivek11 kalevivek11 changed the title wso2 analytics 3.0.0 alert issue wso2 analytics 3.2.0 alert issue Dec 2, 2020
@RAVEENSR RAVEENSR mentioned this issue Dec 7, 2020
Open
@RAVEENSR
Copy link
Member

RAVEENSR commented Dec 7, 2020

Duplicate issue. Hence closing. Track the progress of this issue in 1479 and 1480.

@RAVEENSR RAVEENSR closed this as completed Dec 7, 2020
@RAVEENSR RAVEENSR mentioned this issue Dec 7, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kalevivek11 @RAVEENSR