49 results found
-
Support for searchable snapshots
As an user of Opensearch
I want to be able to store large amounts of immutable logs for lengthy periods of time
so that I can support compliance and other regulatory requirements placed on me
In addition, I need this to be provided in a cost efficient manner, leveraging technologies such as object storage. Given queries against this data are infrequent price far outweighs performance.
2 votes -
PPL & Observability SIEM features in OpenSearch
As a Security Analyst,
I want to utilise the Observability plugin & PPL in an efficient manner. Features such as tooltips and autocomplete would help a lot, as well as bug fixes and regular updates.
The syntax is not well nor widely understood, and there are lingering bugs, which for a user are very hard to duplicate across the microcosm of repositories which bundle into the suite.
Observabilitiy & PPL feels like a very promising place for OpenSearch to become more useful to a security operations team, where currently the capabilities are extremely limiting.
While OpenSearch Dashboards, with tenancy and…
2 votes -
One-click visualisation creation from Discover in OpenSearch
As a security analyst,
I want to create a visualisation from a search, which can then be added to an existing or new dashboard, so that I can save time creating dashboard elements and create dashboard elements in a much easier manner than is currently possible.
2 votes -
Compliance dashboards for OpenSearch
As a security operator,
I want to have a view of our compliance status across various data sources, in a 'continual assurance' manner. e.g. PCI, SOC2, ISO27001, or frameworks such as NIST CSF. So that I can get a continual view of degredations as they occur.
so that I can [describe the benefit or a problem you want to solve]
In addition, [share any additional context or why this idea is important to you]2 votes -
API integration for cloud event sources
As a security analyst,
I want to collect events directly from cloud resources (XaaS, eg AWS, Azure, Okta, Github, GCP...) without having to run an intermediary host such as Logstash, so that I can lower my infrastructure cost, lower external hosting complexity and lower our maintenance overhead.
2 votes -
Correlation between indexes in OpenSearch Dashboards
As a security analyst,
I want to be able to search across more than one index within Discover (and Dashboards queries), so that I can enrich data between sources.
For example, Okta logs contain an organisations user logins, along with their IP addresses. We may also have SSHd logs, and between the two we could correlate IP address to provide user details into a search of SSH logs. Many examples could be found.
In addition, [share any additional context or why this idea is important to you]2 votes -
A unified search, alarm & dashboarding experience in OpenSearch
As a security analyst,
I want to have a unified alerting, dashboarding and search experience in my SIEM, so that our capabilities are not spread across multiple plugins with differing query languages.
Currently between Dashboards/Discover, Security Analytics, Observability there is not a unified experience, it is extremely confusing and difficult to use, and to make this harder each component has a different set of upstream repositories and seemingly little co-ordination between them in features, documentation and bug fixes, making the experience very confusing and difficult.
2 votes -
Search a string as another data type in OpenSearch
As a security or data analyst,
I want to be able to treat a string as another data type at search, for example searching the string "1" as an integer upon search, so that I can search data appropriately without having to update the mapping and reindex all data.
2 votes -
OpenSearch Dashboards range pickers in Visualisations
As a security analyst,
I want to utilise 'range' in visualisations without having to Edit Query as DSL,
so that I can save time and also have people without extensive DSL knowledge create visualisations.2 votes -
Keep OpenSearch Security Plugin SIGMA rules up to date.
As a security analyst and operator,
I want to utilise up-to-date SIGMA rules in the OpenSearch Security Plugin, so that I can utilise current contributions from the opensource community.
For example - at the time of writing this - the Okta rules in Security Plugin repo (main branch) have not been updated since February 2023 - with 13 rules available , while the SIGMA repo (master branch) Okta rules were last updated in December 2023 - with 21 rules available, notably including rules based on the high-profile Okta breach in 2023.
This can be observed across many rule categories, with…
2 votes -
View the underlying data of a visualisations in OpenSearch Dashboard
As an OpenSearch user
I want to view the data underneath the visualisation
so that I can quickly identify root cause of some abnormal behaviour of my system2 votes -
Allow customer to stick with one minor OpenSearch version for an extended period
As a DB admin
I want to stick w a minor OS version until I have done all my testing with the new minor versions to make sure it does not break anything
so that I can confidently upgrade my OS.1 vote -
Support and/or adopt PGSync to help users maintain real-time sync between Postgres and Opensearch
As an OpenSearch and Postgres user
I want to easily keep these databases in sync
so that I can provide low latency, high throughput full text search that doesn't impact my transactional database.Ever since search engines were invented, developers have struggled with keeping their system of records (typically relational databases like Oracle, Postgres, MySQL, etc) in sync with the search engine. Batch oriented processes are often not real-time enough resulting in poor user experiences where the search results don't return the same information as what's represented in the system of record. Event-oriented solutions such as writing updates from the…
1 vote -
Ability to change refresh interval for Index using Terraform
As a DBRE
I want to change the index refresh interval from a default value to some non-default value as a part of our latency optimization. With that, I would like this ability through IAC and control through our codebase.The idea here is to control this value from IAC and in more organized fashion.
1 vote -
Opensearch Large Shard Warning
As an operator of Opensearch,
I want to be alerted when my shards are outside of recommend best practices of 10-50GB / shard,
so that I can avoid having overly large shard size cause performance problems for ingestion and query.In addition, please tell me how within the alert to split my shards if they do get too large.
1 voteThanks Jason. We can roadmap this. WIll update the idea when we have more concrete timeline
-
Enable all cross cluster replication APIs
As an OpenSearch operator
I want to be able to pause, stop, and start cross cluster replication
so that I can use this feature to support failover in a disaster recovery scenario.Typically in Elasticsearch or Opensearch, CCR can be used to support a DR deployment by placing two clusters (a leader and follower) in separate regions. When the leader cluster becomes unavailable, applications/clients can failover to the follower cluster by stopping replication on the following cluster which makes it a regular index.
https://opensearch.org/docs/latest/tuning-your-cluster/replication-plugin/api/
1 voteCurrently we are controlling this process of start/pause etc so we can control replication process during the entire cluster's lifecycle (through all the node recycling, upgrading etc.) to ensure the stability of our services.
I put this to Gather interest, I am also aware of the failover capability mentioned in the ideas as well (we have different ideas ticket for that), this is something we can have a look and see if we need to expose all APIs if the main usecase is failover
-
OpenSearch compute-optimized and storage-optimized clusters
As an architect
I want to create right-sized clusters for my use case
so that I can get the most value.Currently, all the OpenSearch clusters have a 1:4 CPU:RAM ratio. High throughput application search use cases often have small data sets and can benefit from more relative CPU than RAM or disk (e.g. 1:2 CPU:RAM ratio). Logging use cases with large volumes of data may benefit from storage optimized instances with 1:8 CPU:RAM ratio with more disk.
1 vote -
Support two-zone OpenSearch clusters
As an OpenSearch architect
I want to provision the minimum amount of hardware I need to meet my requirements
so that I can optimize costs.Currently, OpenSearch on Aiven only supports 3 AZ deployments for production-grade plans. OpenSearch clusters with data nodes deployed across 2 AZs can be considered production-grade as long as you have master nodes across 3 AZs.
1 vote -
Set BASE_URL for Opensearch dashboards
As Opensearch Administrator
I want to be able to set custom Base_URLs for my OpenSearch clusters
so that I can simplify usage for my customers when they have multiple OS services per group/client/customer.1 vote -
The ability to Reduce logs in OpenSearch
As a security analyst,
I want to 'reduce' the logs searched to reduce the data to common patterns, allowing me to easily see meaningful events.
1 vote
- Don't see your idea?