Main

processing priority

3

site type

5 (wiki-type site, growing by topic rather than chronologically)

review version

11

html import

20 (imported)

Events

first seen date

2023-11-29 13:15:27

expired found date

-

created at

2024-06-06 21:48:05

updated at

2026-02-18 00:12:31

Domain name statistics

length

19

crc

58682

tld

86

nm parts

0

nm random digits

0

nm rare letters

0

Connections

is subdomain of id

87719371 (github.io)

previous id

0

replaced with id

0

related id

-

dns primary id

0

dns alternative id

0

lifecycle status

0 (unclassified, or currently active)

Subdomains and pages

deleted subdomains

0

page imported products

0

page imported random

0

page imported parking

0

Error counters

count skipped due to recent timeouts on the same server IP

0

count content received but rejected due to 11-799

0

count dns errors

0

count cert errors

0

count timeouts

0

count http 429

0

count http 404

0

count http 403

0

count http 5xx

0

next operation date

-

Server

server bits

server ip

-

Mainpage statistics

mp import status

20

mp rejected date

-

mp saved date

-

mp size orig

40536

mp size raw text

23469

mp inner links count

9

mp inner links status

20 (imported)

Open Graph

title

description

In a previous post, I described how to run an ad-hoc analysis on the Telemetry data. There is often a need to re-run an analysis on an ongoing basis …

image

site name

author

Mark Reid

updated

2025-12-17 17:19:59

raw text

Mark @ Mozilla Mark @ Mozilla Performance team RSS Blog Archives Scheduling Telemetry Analysis Mar 14 th , 2014 In a previous post , I described how to run an ad-hoc analysis on the Telemetry data. There is often a need to re-run an analysis on an ongoing basis, whether it be for powering dashboards or just to see how the data changes over time . We’ve rolled out a new version of the Self-Serve Telemetry Data Analysis Dashboard with an improved interface and some new features. Now you can schedule analysis jobs to run on a daily, weekly, or monthly basis and publish results to a public-facing Amazon S3 bucket. Typical Scheduling Here’s how I expect that the analysis-scheduling capability will normally be used: Log in to telemetry-dash.mozilla.org Launch an analysis worker in the cloud Develop and test your analysis code Create a wrapper script to: Do any required setup (install python packages, etc) Run the analysis Put output files in a giv...

Text analysis

redirect type

0 (-)

block type

0 (no issues)

detected language

1 (English)

category id

Podróże (51)

index version

2025110801

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

18193

text words

3887

text unique words

1125

text lines

552

text sentences

174

text paragraphs

69

text words per sentence

22

text matched phrases

1

text matched dictionaries

1

RSS

rss status

32 (unknown)

rss found date

2023-12-30 10:04:10

rss size orig

36026

rss items

8

rss spam phrases

0

rss detected language

1 (English)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap status

40 (completed successful import of reports.txt file to table in_pages)

sitemap review version

2

sitemap urls count

12

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

0

sitemap found date

2023-12-24 20:48:55

sitemap process date

2025-05-12 17:23:02

sitemap first import date

-

sitemap last import date

2026-02-18 00:12:31