This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
mission:log:2014:11:24:using-python-lxml-request-as-simple-scrape-robot-for-metrics-from-webpages [2015/01/09 09:42] – [The python solution] chrono | mission:log:2014:11:24:using-python-lxml-request-as-simple-scrape-robot-for-metrics-from-webpages [2015/07/08 08:07] – [In the beginning there was the copy] chrono | ||
---|---|---|---|
Line 22: | Line 22: | ||
===== In the beginning there was the copy ===== | ===== In the beginning there was the copy ===== | ||
- | Even if it appears unique and original to us, there always was some other inspiration/ | + | Even if it appears unique and original to us, there always was some other inspiration/ |
===== The Problem ===== | ===== The Problem ===== | ||
Line 97: | Line 97: | ||
Infrequently upstream data changed and introduced some incomprehensible white space changes as a consequence and sometimes just delivered 999.9 values. Pain to maintain. And since most relevant values came as floats there was no other solution than to use bc for floating point math & comparisons, | Infrequently upstream data changed and introduced some incomprehensible white space changes as a consequence and sometimes just delivered 999.9 values. Pain to maintain. And since most relevant values came as floats there was no other solution than to use bc for floating point math & comparisons, | ||
- | And finally, the data structure and shipping method to influxdb is more than questionable, | + | And finally, the data structure and shipping method to influxdb is more than questionable, |
===== The python solution ===== | ===== The python solution ===== |