Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom types #13

Open
aolko opened this issue Jan 17, 2018 · 5 comments
Open

custom types #13

aolko opened this issue Jan 17, 2018 · 5 comments

Comments

@aolko
Copy link

aolko commented Jan 17, 2018

How about custom incident types and styles for each one?

@Pryx
Copy link
Collaborator

Pryx commented Jan 17, 2018

Sounds like a nice feature, but not sure how useful it would be. What kind of types that would require different styles would you use? From the top of my head I can't think of any.

@aolko
Copy link
Author

aolko commented Jan 17, 2018

like allowing user to change the color or change entire css class (or id) per type (for gradients, custom icon, etc)

@Pryx
Copy link
Collaborator

Pryx commented Jan 17, 2018

I understand what you mean, it's hard for me to see what it would be used for. I'm trying to see whether this is a commonly needed and should be prioritized or not. Basically what I'm saying is that I would like a specific example of how it would be used.

@Pryx
Copy link
Collaborator

Pryx commented Jan 17, 2018

That being said I'm open to implement it, it's just about priority. If a PR with this happened to be opened I'd gladly merge it, but it's not vital for my operations atm so I feel like doing other things first.

@Pryx Pryx added this to the 1.2.0 milestone Jan 17, 2018
@jhuesser
Copy link
Contributor

jhuesser commented Jun 7, 2018

I would love it if there are "Investigating", "Identified" and "Monitoring". We could use minor for that, but in case of "Monitoring" (after deploying a fix) the system should be operational again. But if there is still an error, it would be better if the user knows, that there recently was an incident.

@Pryx Pryx removed this from the 1.2.0 milestone May 22, 2020
@Pryx Pryx added the pinned label Sep 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants