Information about the Dashboard, Notifications, and how to get and track your usage data in Alooma.
How many events is Alooma loading into my data warehouse? Can you show me that by date? By table? What's the latency for getting my data into the warehouse?
To answer questions like these, Alooma provides two ways to track usage for your data warehouse: via the graphs on the Dashboard, and through the reports available via the Slack ReportBot.
Click on the Dashboard icon in Alooma to view the Dashboard graphs. Here you can see information about Throughput, Latency, Events over time, and the Incoming and Restream queues.
In general, the graphs are great for spotting trends and getting a good look at what's happening on your system. However, because of the real-time nature of the system, occasionally, a very small number of updates to the data may not be reflected in the graphs.
ReportBot allows you to get reports on your deployments directly from the meta tables if you have an Alooma Slack channel (Enterprise customers).
Currently, ReportBot can provide the following reports for each output:
Redshift and Snowflake:
Events Loaded by Date and Table
Events Loaded by Date
Events Loaded by Table
Reports 2 and 3 are just versions of report 1, aggregated by a specific date/table.
Last Batch Loaded at: When was the last time we loaded events for each table?
Events Loaded by Date
So, now you're probably wondering how to use ReportBot.
You use ReportBot in your Alooma Slack channel, so first you'll need to invite @ReportBot to your channel (yours looks something like this: #alooma-<CUSTOMERNAME>).
Once you've invited @ReportBot, you can request a report:
@ReportBot report x
Where x is the number of days you want the report to cover (maximum is 365). If x is not specified, the default is the last 7 days. Don't worry, if you get it wrong ReportBot will show you the correct usage:
After you request a report, you'll see a menu with the possible reports available to you. Make your selection and the report is uploaded in .csv format to the channel.
This only works on channels hosted in Alooma's workplace. ReportBot does not yet support Slack's shared-channel functionality.
Here's an example of the .csv file for events loaded over the last 7 days.
date,events_loaded 2017-11-27,3433524 2017-11-28,3665221 2017-11-29,4128162 2017-11-30,1199480 2017-12-01,3096248 2017-12-02,2228221 2017-12-03,2410643
If you have further questions about usage or if you can't find the data you're looking for, we're here to help.
Alooma's dashboard gives you insight into the Alooma platform's status in processing your data. It does so through a set of charts that indicate the state of different aspects of the system:
Throughput - This chart indicates the number of events per second flowing into the system across all of your inputs. Use this chart to get an general overview the data flowing into the system.
The data transferred is the amount of data in GB transferred since the last time your system was upgraded.
The average event size is the mean event size in bytes in the last 24 hours.
Latency - This chart shows the average, median, top 95%, and maximum latency of the events flowing through your system. The latency is measured as the time in seconds between when the event reached Alooma from the input to when it was loaded to your target data warehouse. Use this chart to understand the delay you should expect in seeing your events in your target data warehouse.
Events per minute - This chart shows the events per minute that Alooma received as well as the number of events that were restreamed, discarded, had an error, were unmapped, or were loaded to your target data warehouse. Use this chart to validate that your events are being loaded properly.
Incoming queue - Here you can see the number of events that Alooma received across all your inputs. Use this chart to identify spikes and input behavior.
Restream queue - This chart shows you how your restream is growing in terms of number of events. Use this chart to identify growth or attrition of errored events, and to strengthen the feedback of whether the restream queue is shrinking as you fix problematic events.
Use the time filter at the top of the page to indicate the timespan the charts should reflect: Last hour, 24 hours, 3 days, 7 days, or 30 days. Only the Throughput chart is not impacted by the time filter.
Hover over the charts to get additional breakdown information for the particular point in time.
Hover over a legend item to filter the view to only that category. Click a legend item to hide that particular category.
Alooma's notification pane, found on the Dashboard tab, gives you insight into the errors, warnings, and generally informative events that have happened in the platform. It shows notifications that have occurred in the last 24 hours.
Errors: These notifications show with a red indicator and require your attention for your data to be properly replicated to your target data warehouse. These notifications generally indicate an issue that has caused events to go to the Restream Queue. Read more about common event error reasons and solutions.
Warnings: These notifications indicate that there's a situation that requires your attention but isn't necessarily an error. An example is that events have been sent to the Restream Queue.
Informative: These are notifications that indicate interesting events that do not require action. For instance, events being loaded to your target data warehouse, mapping update success, and restream finishing.
You don't have to log in to Alooma to get these notifications - you can sign up for email digests and receive them straight in your inbox.