You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have like 150+ API keys and are constantly adding more as we change our serilog sinks to Seq. The existing search box helps us by finding API Keys by name.
Additionaly, it would be great to have the following features:
Filter API Keys by "Applied properties". This would help us to identify all "production" or "qa" API Keys and see theri ingestion rates.
Filter by "Level" to quickly identify "incorrectly" set levels, e.g. "Debug" with a "production" property
Sort by "Events arrived", "Events accepted" and "Ingested data". We once had an incorrectly configured application which logged too many / large events and hence clogged our disks. With sorting by "Ingested data", it would be easier to identify the responsible app.
Maybe you could look into these features for one of the next releases.
The text was updated successfully, but these errors were encountered:
"Filter API Keys by Applied Properties" is already implemented, at least insofar as typing either the property name, or value, into the filter box will identify them.
We have like 150+ API keys and are constantly adding more as we change our serilog sinks to Seq. The existing search box helps us by finding API Keys by name.
Additionaly, it would be great to have the following features:
Filter API Keys by "Applied properties". This would help us to identify all "production" or "qa" API Keys and see theri ingestion rates.
Filter by "Level" to quickly identify "incorrectly" set levels, e.g. "Debug" with a "production" property
Sort by "Events arrived", "Events accepted" and "Ingested data". We once had an incorrectly configured application which logged too many / large events and hence clogged our disks. With sorting by "Ingested data", it would be easier to identify the responsible app.
Maybe you could look into these features for one of the next releases.
The text was updated successfully, but these errors were encountered: