It’s been over half a decade since I wrote a blog entry here at Splunk about an astronomy related topic and that’s because I was just waiting for something interesting to talk about. In the past, I have spoken about star brightness, but recent news has taken this subject to another level.
For those, who may not be following, last fall, astronomers found an inexplicable property of a star almost 1500 light years away. Using Kepler spacecraft data, the star was shown to dim up to 22 percent of its original brightness at various times. To put this in perspective, the largest planets passing in front of a star only dim most stars less than one percent. So, it was obviously not a local planet causing the dimming. The real questions then become can this be a repeatable measurement, at what interval does this happen, and most importantly, what causes the dimming?
Measuring the brightness of one star at various intervals is one thing, but it would behoove the scientific community to do the same for millions of stars in the galaxy to figure out repeatable patterns or if this is an unique occurrence. Since the Milky Way has more than 100 billion stars (Ok, we can rule out the flaring M Class stars comprising 70 percent of all stars and short lived mega stars, but you are still left with 25 billion plus stars), taking historical measurements and analyzing them for patterns for an explanation makes this a big data problem. I had wrote a long time ago that all this data can be stored in Splunk and for any given star, we can conceptually create a timechart of its brightness using whatever units you like such as this example.
However, that is so 2010. There may be quite a few software packages out there to create this kind of chart (although you would still need a big data platform to store, retrieve, and analyze such a large growing data set). One could conceivably start collecting data for each star and use thresholds to create alerts when the brightness dims below a certain percentage. The percentage could be hard coded into rules (or Splunk searches) and adjusted as necessary. On the other hand, what if each star has its own peculiarity for the thresholds? Some stars may dim by 1 to 2 percent, which may make them rather uninteresting, but a dimming of 3 percent for the same star may mean a critical alert is needed. Similarly, the star in question for this blog, Tabby’s star, as it is now known as for the discoverer, has thresholds for dimming that are beyond anything ever seen. Automatic threshold adjustment is needed for what could be considered normal, high, and critical. Enter Splunk ITSI (IT Service Intelligence).
Splunk IT Service Intelligence is a monitoring solution that offers innovative, real-time insights into service health against defined key performance indicators (KPI) to drive operational and business decisions. Splunk ITSI can organize and correlate relevant metrics/events into ‘swim lanes’ to speed up investigations and diagnosis.
If we were to think of a star as a service, key performance indicators (or health scores) can be its brightness, temperature, UV light ouput, and IR light output among other things. Each KPI can have its own thresholds that can be computed dynamically over time to indicate what is normal, high, or critical. Now, instead of creating a plain timechart and using hard coded rules for thresholds, Splunk ITSI can use machine learning to auto-adjust the thresholds over time. The KPI for brightness (or dimming percentage depending on how you look at it) could end up looking something like this in Splunk ITSI.
In this hypothetical example, the star has dimmed over 20%, which is critical enough for someone to immediately investigate.
Moreover, since machine learning is used in Splunk ITSI, anomalies for the KPI could easily be detected and alerted upon.
One quick explanation that astronomers suggested for Tabby’s star dimming was a planetary collision at the time of measuring. I find this hard to believe because even the largest planet could only dim a star of this size by 1% and it would be incredibly strange for the fragments of a collision to line up in a blanket array to dim the star at such a large number. Scientifically, one could measure the IR light output increasing if a collision took place and correlate this with the dimming. This change in IR light measurement could also be a KPI for Splunk ITSI. In this case for Tabby’s star, no change in IR light was found.
Another explanation for the dimming that some scientist suggested was that a swarm of exo-comets just happened to be at the right place to dim the star. I find this equally as hard to believe as the number of comets needed (not to mention the enormous size of each comet) and the cooperative alignment of the comets to blanket the star makes it incredible. Scientifically, one could measure the UV light output around the star increasing as the comets swarm the star and this could be another KPI for Splunk ITSI.
Another KPI could be the star’s temperature meaning that perhaps, the temperature changes of the star has a direct relationship to its dimming percentage. Putting all these KPI together within swim lanes could create a visual correlation for the cause of the dimming. Fortunately, Splunk ITSI has this capability to stack any KPI’s from any service together to visually correlate the results. Here’s a hypothetical example of this using the KPI that are mentioned here.
The astute reader will point out that half the stars found are binary stars or greater meaning that they have one or more companions. In this case Splunk ITSI has a concept called entities for which each star could be an entity and the comprised stars of the system could make up the service.
What we have shown here is that by using a platform such as Splunk ITSI, we can treat each notable star in the galaxy as a service, keep track of its KPI within a big data platform, use dynamic thresholds to monitor the service, find anomalies in the KPI, and finally group KPIs from any service within swim lanes to visually correlate possible root causes.
If you’ve gotten this far reading this blog entry, you may want to ask what is causing this ordinary F class star to dim so much at various intervals. I will offer some more suggestions, for which I must admit, I am unqualified to backup, but it makes for interesting reading.
What is happening is a kick starter effort to take more measurements at frequent intervals around Tabby’s star. Sadly, history has shown how we find interesting things in the cosmos that cannot be found again. The WOW signal and the Mars onsite life detection experiments from the 1970s come to mind. A past world without universal internet and social media left those events as part of history, with discussion limited to few. It would be sad to discover if no more extreme dimming can be measured for Tabby’s star. This is why I advocate that the “health” of many stars be measured and treated as a service with multiple KPIs. Our current limitation is the ability to gather the measurements at mass scale, but I suspect instrument automation will be something that develops broadly over the years.
I have made the case that measuring the variable properties of stars is a big data problem. The use of Splunk ITSI to treat each star as a service with KPIs makes the journey to discovery easier than past static techniques.
In my past Splunk blog entries covering astronomy, I mentioned people, who inspired me to create the entry. Throughout history, we know the familiar names of those who have discovered and enhanced our understanding of the Cosmos. But, for each well known scientific star, there may be hundreds that go unnoticed. I would like to take this opportunity to mention my uncle, retired optical engineer, Dr Pravin Mehta, as one of those, who were among the thousands, that contributed to the field as he had small parts for Skylab, Hubble, Chandra, and the Einstein X-Ray telescopes. It is the endeavors of people such as him that help illuminate our understanding of the universe.
The Splunk platform removes the barriers between data and action, empowering observability, IT and security teams to ensure their organizations are secure, resilient and innovative.
Founded in 2003, Splunk is a global company — with over 7,500 employees, Splunkers have received over 1,020 patents to date and availability in 21 regions around the world — and offers an open, extensible data platform that supports shared data across any environment so that all teams in an organization can get end-to-end visibility, with context, for every interaction and business process. Build a strong data foundation with Splunk.