views intergration with redirect module I've googled and nothing found about redirect module integration into views to add new filter criteria for a content type or taxonomy.

I need all redirects (FROM and To fields that showing in the image) path against specific nid (contextual filter) or content type (blog, event, article).

For more clarifications, see attached image
For your first question:

Redirect module integrated with views module, just navigate to admin/structure/views and you will see View called Redirects, enable it if it's not enabled, then pick the field you want, source field label is 'Source redirect' and from is redirect URL.



You can also create a new your view just be sure you using the base table or redirect





For the second question:

you need first to understand how redirect module structured.

Each redirect record you see is an entity, and it has the following fields:


rid: Primary Key: Unique redirect ID.
hash: A unique hash based on source, source_options, and language.
type: The redirect type; if the value is 'redirect' it is a normal redirect handled by the module.
uid: The {users}.uid of the user who created the redirect.
source: The source path to redirect from.
source_options: A serialized array of source options.
redirect: The destination path to redirect to.
redirect_options: A serialized array of redirect options.
language: The language this redirect is for; if blank, the alias will be used for unknown languages.
status_code: The HTTP status code to use for the redirect.
count: The number of times the redirect has been used.
access: The timestamp of when the redirect was last accessed.
status: Boolean indicating whether the redirect is enabled (visible to non-administrators).


As you see from the structure, there is no reference to the entity you added the redirect for; you have only a reference for the user who creates the redirect.

You can create a relation between the redirect and the user who creates the redirect, then get the nodes which authored by that user; Then you can adjust the views in the way you want.

Please notice this would work with nodes and with any entity store uid, but for example, in Taxonomy case it won't work because taxonomy entity doesn't store the uid.

another tip might help a bit is to add the redirect URL as a filter then make some string comparison.