Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Improve functionality of sample detectors #366

Open
ohltyler opened this issue Jan 27, 2021 · 0 comments
Open

Improve functionality of sample detectors #366

ohltyler opened this issue Jan 27, 2021 · 0 comments
Labels
feature new feature

Comments

@ohltyler
Copy link
Contributor

Sample detectors were originally released when the plugin only had single entity, real-time detectors. With the addition of high-cardinality and historical detectors, the plugin should offer corresponding sample offerings of those to help users get familiar with the new features. This will require making the sample data more complex and stretch farther in the past.

A few options:

  1. Keep existing scenarios (HTTP responses, eCommerce, host health) and let user choose within those modules on what they want to create - (1) single-entity real-time, (2) high-cardinality real-time, (3) historical, or some combination of those.
  2. Provide separate scenarios to highlight the common use cases for the different types of detectors. Maybe only offer 1 example of each, and customize the data accordingly.
@ohltyler ohltyler added the feature new feature label Feb 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature new feature
Projects
None yet
Development

No branches or pull requests

1 participant