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

Automatically create signals based on API keys properties #2327

Open
DanAvni opened this issue Dec 1, 2024 · 2 comments
Open

Automatically create signals based on API keys properties #2327

DanAvni opened this issue Dec 1, 2024 · 2 comments

Comments

@DanAvni
Copy link

DanAvni commented Dec 1, 2024

I have many API keys and for each one I am adding two properties: Environment (describes which customer the server belongs to) and Source (describes which application component sent the event). After adding a new environment or source I need to create matching shared signals for all users to see and to be able to filter by these properties.

Please add an option to make the signals auto update when API keys are added/removed. The best thing I think would be to add an auto-group signal that I would specify the property name and it would list all values of API keys under it (not all values of events because there might not be any events yet and I need the user to understand that - and not seeing the signal is not as intuitive)

@nblumhardt
Copy link
Member

Thanks for the suggestion @DanAvni.

In case it helps while we look into this one - if you have properties like Environment and Source with a reasonably large number of values, property indexes can speed up searches significantly. These won't help with the discovery aspect though, unfortunately.

seqcli apikey create and seqcli signal create could be another option to check out (e.g. kicked off by a deployment script). HTH!

@DanAvni
Copy link
Author

DanAvni commented Dec 2, 2024

Hi @nblumhardt

I already have some utility I made that reads through API all the keys and the signals and creates what is needed. It works but I need to remember to run it after creating keys. I think an automated process would improve the quality of life for many users. Afterall, the properties added to API keys are usually there to be filtered by (at least in my view)

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

2 participants