- Added some higher numbers to the "by number of days since the" selector. Unfortunately it is sometimes useful to normalize the x-axis to these much higher numbers now.
- Moved the layer of reset links into its own Pattern file.
- Added a new prototype that allows the same sort of interactivity but specifically for the counties within one particular US State. For all non-US users out there, unfortunately the JHU dataset recently started providing this County-level detail only for US States. For what it's worth when similar granularity is available for other countries I will certainly try and expose that as additional functionality, as I've done here for the US.)
- (New data for 3/29 loaded from JHU CSSE)
- Added a disclaimer to both "cases over time by country or state" and "recovery by country" to call out that the "Recovered" numbers in the dataset are not broken out by US State. Without this disclaimer it seemed potentially quite alarming. Hopefully the JHU CSSE folks are able to soon break this down by state and I can change this disclaimer or remove it later.
- (New data for 3/28 loaded from JHU CSSE)
(New data for 3/27 loaded from JHU CSSE)
- Fixed a misconfiguration of the main view, where the main Country/Province/State pulldown would reset to the default every time you reloaded the page (rather than using the selection preserved in the url)
- minor fix so the chart doesn't redispatch when you just change the y-axis type.
- Expanded the 'reset to default' link to also allow you to reset to selecting all the provinces within the few countries that have that level of granularity. This is only a convenience but it saves a lot of time selecting/deselecting provinces and states.
- Also I have added another static lookup to handle normalization of various Province_State names that have typos or inconsistencies.
- (data for 3/26 loaded from JHU CSSE)
- Fixed a minor bug where the explanatory note above the main chart always said the xaxis showed days since the Nth "confirmed case", even when that option was set to 'deaths' instead.
- (New data for the past day loaded from JHU CSSE)
quick fix for a regression in the 0.7 build just posted, where 'recovery-over-time' tab didn't load.
Splunkbase restricts release notes to only 1000 characters and the notes for this release exceed that number.
However for complete release notes for this and all releases, you can always refer to our website.
- Improved the `get_count_of_days_since_nth_case` further, so now it can take three optional args. See comments in macros.conf
- Added the ability to explode out the countries/provinces and treat them as separate countries. This allows a much more flexible analysis - notably you can compare individual US states or Australian or Canadian provinces to entire countries. The previous tab doing per-state analysis has been deleted.
- Added controls to allow the user to change from the x-axis being "days since the 100th confirmed case" from 100 to any N, and from "confirmed case" to "death".
- Fixed a bug where clicking 'see raw search syntax' on a tabular output would dump you out into a column chart
- Pulled out the primer on logarithmic y-axes into its own page under 'notes'
- Upped the required version of Canary to 1.2.3, and added a little message that appears in the top of the analysis view, if the version is too low
Fixed a problem in the "COVID-19 dataset" tab where the covidtracking.com data rows were appearing there, but with most columns blank. As this was confusing and served no purpose I filtered them out
Fixed a regression in the "COVID-19 dataset" tab where the selection of the province/state element had no effect on the results.
Added some text underneath the main tab giving users a primer on exponential curves and how to interpret charts with logarithmic y-axes
Since the JHU CSSE data suddenly has a whole other field for US County, but the field name strangely is "Admin2", I've renamed the field to "County" and made it visible in the Covid19 tab.
Fixed an unfortunately bug that only happened on 7.3, but that prevented users from being redirected into the app correctly. Instead they were stranded on a page telling them that "TopNav" and "AppNav" modules didnt exist.
Reviewed and made improvements to how we handle days with missing data at the country and province level. Previously the SPL screened out the duplicate records where the "Last Update" referred to a day before the day-based filename the record was in. Now we let those records get indexed and returned at search time but at search time we override the _time value from the filename. Normally this is a bad practice in Splunk and it's better to set it from the filename at index time with INGEST_EVAL. However here it's quick, its effective and we pull the entire set off disk anyway with each search so there's not much of a downside. Also INGEST_EVAL would force reindexing for all upgrades to this release.
Removing the warning message added in 0.4.2 and the app now simply dedups the data explicitly on search.
There is a new health checks page, whereby the app ships stanzas in checklist.conf that get run explicitly on this page. Note the checklist.conf stanzas will also run in the Splunk Monitoring Console if any splunk admins are looking there
(New data loaded from JHU CSSE dataset)
JHU recently went back and changed something in the daily data from 2 days ago, which is great. However this comes before I had completed the health check to automatically detect this and bubble up a warning to the user
So this release just has a hardcoded warning at the top to always reindex the data after updating to a new version.
Redoing the default country selection. The short version is "I added Switzerland".
The Long version - Previously it was the top 10 total confirmed cases, plus an extra 2 - Hong Kong and Singapore which are low but have extremely interesting curves. New it is the top 10, plus an extra 3 - Japan, Hong Kong and Singapore.
the app now ships a snapshot of the per-day testing data for US States from https://covidtracking.com/api/
some key numbers from the us testing data can now be chosen as y-axis values on the per-province/state chart, although of course they only work for US states at the moment.
In the "by province/state" tab I have marked the "Recovered" yaxis option as "(doesn't work with recent US data)", The reason is that since the "Recovered" numbers in the US are no longer associated with individual states, this means we can't really graph that number in the US split by state. While you might think we can create a fake state called 'unknown', we'd ahve to also determine "on what day the unknown state passed 30th confirmed cases" and that's nonsensical.
Altered the app so that even if the user fails to install the Sideview Utils app or the Canary app (or both) this app itself will explain that problem to them on the landing page and give them instructions for how to install the missing apps. (Before this version the app would just load a blank page and leave the user stranded.)
Tested on Splunk 7.3 and since everything seems fine, I am marking it compatible with 7.3 (prior to this it was marked in SB as Splunk 8.X only)
gave the navigation bar a link to the release notes file.
- (New data loaded from JHU CSSE dataset. I try to push a new build asap when there's new data on github)
unfortunately Splunkbase truncates release notes at only 1000 characters so our notes for this release do not fit in this field.
However you can read the release notes for this release as well as all others over on our website - https://sideviewapps.com/apps/covid19-reporting/release-notes/
(i need to backfill release notes but right now since it's still been languishing many days in the SB manual review queue, it's not a pressing task)
Development of this app began on March 14th and is proceeding quite rapidly. I plan on posting daily updates, as this app actually has a current snapshot of the CSSE COVID19 dataset contained inside it.
Once you install the app and restart Splunk, the app will create a new index called "covid19" and index the daily_report data (a copy of which ships within the app itself) into that index.
Check back soon for updates. Email firstname.lastname@example.org with any questions/comments.
Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.