[go: up one dir, main page]

Page MenuHomePhabricator

Create panel on citoid dashboard to identify domains which may block us
Closed, DeclinedPublic

Description

We need a panel on the citoid dashboard that either shows:

by domain, top errors, with a percentage of how many errors are there relative to 200 (so like, percentage !200)

by domain, only domains which have no 200s in the sampled time period.

Unfortunately after poking around I couldn't figure out how to do something this complicated in the openSearch dashboard.

The idea is to identify domains that may be IP blocking us permanently so we can contact them and maybe get unblocked.

Currently we have a top requested domains and top requested errors, but if you want to see if a website is entirely failing you gave to do some post processing comparing them.

Tagging observability, which may knows how to do this? If not I could download raw data and python it but a live dashboard would definitely be better.

Event Timeline

Mvolz renamed this task from Create panel on citoid dashboard to identify domains which block us to Create panel on citoid dashboard to identify domains which may block us.Tue, Oct 22, 11:35 AM

"Count Percentage" isn't a calculation that OpenSearch returns in its response. It's not even a percent of all hits returned by the query. Count percentage is calculated client-side by dividing each leaf aggregation doc_count by the sum of all branch root aggregations doc_count. This makes it heavily influenced by the size parameter.

I don't think it's possible in the current implementation. OpenSearch Dashboards would need a new feature to do it.

"Count Percentage" isn't a calculation that OpenSearch returns in its response. It's not even a percent of all hits returned by the query. Count percentage is calculated client-side by dividing each leaf aggregation doc_count by the sum of all branch root aggregations doc_count. This makes it heavily influenced by the size parameter.

I don't think it's possible in the current implementation. OpenSearch Dashboards would need a new feature to do it.

Ok, good to know then. I wasn't sure if it was just that I couldn't figure out or if it really wasn't possible!