/sensu-go/6.12/api/core/ Recent content in Core API on Sensu Docs Hugo -- gohugo.io en-us /sensu-go/6.12/api/core/apikeys/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/apikeys/ NOTE: Requests to core/v2/apikeys endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all API keys The /apikeys GET endpoint retrieves all API keys. Example The following example demonstrates a GET request to the /apikeys API endpoint: curl -X GET \ http://127.0.0.1:8080/api/core/v2/apikeys \ -H "Authorization: Key $SENSU_API_KEY" The request will result in a successful HTTP/1. /sensu-go/6.12/api/core/assets/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/assets/ NOTE: Requests to core/v2/assets API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all assets The /assets API endpoint provides HTTP GET access to dynamic runtime asset data. Example The following example demonstrates a GET request to the /assets API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/checks/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/checks/ NOTE: Requests to core/v2/checks API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all checks The /checks API endpoint provides HTTP GET access to check data. Example The following example demonstrates a GET request to the /checks API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/cluster/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/cluster/ NOTE: Requests to core/v2/cluster API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all cluster data The /cluster/members API endpoint provides HTTP GET access to Sensu cluster data. Example The following example demonstrates a request to the /cluster/members API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/cluster-role-bindings/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/cluster-role-bindings/ NOTE: Requests to core/v2/clusterrolebindings API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all cluster role bindings The /clusterrolebindings API endpoint provides HTTP GET access to cluster role binding data. Example The following example demonstrates a GET request to the /clusterrolebindings API endpoint: /sensu-go/6.12/api/core/cluster-roles/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/cluster-roles/ NOTE: Requests to core/v2/clusterroles API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all cluster roles The /clusterroles API endpoint provides HTTP GET access to cluster role data. Example The following example demonstrates a GET request to the /clusterroles API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/entities/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/entities/ NOTE: Requests to core/v2/entities API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all entities The /entities API endpoint provides HTTP GET access to entity data. Example The following example demonstrates a GET request to the /entities API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/events/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/events/ PRO TIP: The core/v2/events API endpoints are primarily designed to provide HTTP access to event data created by agent-executed checks. To test your Sensu observability pipeline, use the agent API to create new ad hoc events or sensuctl or the web UI to execute existing checks on demand. NOTE: Requests to core/v2/events API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. /sensu-go/6.12/api/core/filters/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/filters/ NOTE: Requests to core/v2/filters API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all event filters The /filters API endpoint provides HTTP GET access to event filter data. Example The following example demonstrates a GET request to the /filters API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/handlers/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/handlers/ NOTE: Requests to core/v2/handlers API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all handlers The /handlers API endpoint provides HTTP GET access to handler data. Example The following example demonstrates a GET request to the /handlers API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/hooks/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/hooks/ NOTE: Requests to core/v2/hooks API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all hooks The /hooks API endpoint provides HTTP GET access to hook data. Example The following example demonstrates a GET request to the /hooks API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/mutators/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/mutators/ NOTE: Requests to core/v2/mutators API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all mutators The /mutators API endpoint provides HTTP GET access to mutator data. Example The following example demonstrates a GET request to the /mutators API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/namespaces/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/namespaces/ NOTE: Requests to core/v2/namespaces API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all namespaces The /namespaces API endpoint provides HTTP GET access to namespace data. Example The following example demonstrates a GET request to the /namespaces API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/pipelines/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/pipelines/ IMPORTANT: The pipelines you can create and manage with this core/v2/pipelines API are observation event processing workflows made up of filters, mutators, and handlers. Pipelines are different from the resources you can create and manage with the enterprise/pipeline/v1 API, which allows you to create and manage resources that can only be used in pipelines. NOTE: Requests to core/v2/pipelines API endpoints require you to authenticate with a Sensu API key or access token. /sensu-go/6.12/api/core/role-bindings/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/role-bindings/ NOTE: Requests to core/v2/rolebindings API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all role bindings The /rolebindings API endpoint provides HTTP GET access to role binding data. Example The following example demonstrates a GET request to the /rolebindings API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/roles/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/roles/ NOTE: Requests to core/v2/roles API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all roles The /roles API endpoint provides HTTP GET access to role data. Example The following example demonstrates a GET request to the /roles API endpoint: curl -X GET \ http://127. /sensu-go/6.12/api/core/silenced/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/silenced/ NOTE: Requests to core/v2/silenced API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. Get all silences The /silenced API endpoint provides HTTP GET access to silencing entry data. Example The following example demonstrates a GET request to the /silenced API endpoint: curl -X GET \ -H "Authorization: Key $SENSU_API_KEY" \ http://127. /sensu-go/6.12/api/core/tessen/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/tessen/ NOTE: Requests to core/v2/tessen API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests. The core/v2/tessen API endpoints provide HTTP access to manage Tessen configuration. Access to core/v2/tessen is restricted to the default admin user. Get the active Tessen configuration The /tessen API endpoint provides HTTP GET access to the active Tessen configuration. /sensu-go/6.12/api/core/users/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/api/core/users/ NOTE: The core/v2/users API endpoints allow you to create and manage user credentials with Sensu’s built-in basic authentication. To configure user credentials with an external provider like Lightweight Directory Access Protocol (LDAP), Active Directory (AD), or OpenID Connect 1.0 protocol (OIDC), use Sensu’s enterprise/authentication/v2 API endpoints. Requests to core/v2/users API endpoints require you to authenticate with a Sensu API key or access token. The code examples in this document use the environment variable $SENSU_API_KEY to represent a valid API key in API requests.