Difference between Index ID in address bar vs index uuid

Version 2.9

I have url to my dashboard query

https://xxxxxxxx/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-5m,to:now))&_a=(columns:!(_source),filters:!(),index:‘0b70c730-1cc9-11f0-805a-1b4855d2643b’,interval:auto,query:(language:lucene,query:‘’),sort:!())

How different is this from index uuid. What I am trying to do is build a link to dashboards on the fly, where by clicking it will show the document found. I can get the document Id, but i don’t know how I can get this index identifier in the url

Hey @stecino

UUIDs are globally unique.

Not sure exactly what your trying to do.

I use OpenSearch API embedded in Python code to find documents in Index A where status field is ‘Failure’. I then loop through them and create opsgenie alert for each record found which then triggers corresponding JIRA incident ticket. What I want to be able to do is to build out a OpenSearch dashboards url directly pointing to that record. So when they click on it they will see that document.

If you’re referring to this ID, then this is index pattern ID and is not related to index ID.

@pablo thank you. would refreshing the index pattern change this ID? If not then pretty much unless I delete it and recreate, this ID will be static? If that’s the case I can hard code it?

@stecino Refreshing index pattern doesn’t recreate the object, therefore the index pattern ID remains the same.

You can test it on your side by refreshing the index pattern and opening a single document in the index pattern. You’ll notice in the URL the index pattern ID and that remains even when is refreshed.

1 Like

Perfect this will do. The only thing I will need to dynamically add is the document id and dates filters.

It worked, I am able to generate the url on the fly

2 Likes