to easily distinguish multiple instances of this app to easily distinguish multiple instances of this appĪn informational message to put at the top of all pages, e.g. via a proxy which modifies the URL path) must start with '/'Īn HTML/CSS color value to set as the background color for all pages, e.g. The path under which the application is hosted externally (e.g.
The app can be configured with the configuration settings below (using environment variables). Note that this would work even if only the front-end is exposed externally, with the other tiers only accessible from within the cluster, because each call in the chain is done from the previous hop. If you set the requested Introspector "Group" to Environment and the "Key" to tier (or whatever environment variable you picked), then you can see the simple value returned by each hop to show which tier it represents. if you've deployed network policies or when you're using a service mesh), you can browse to the Inspector Gadget web page on the front-end, and from there perform an Introspector request by setting the "Call Chain" to (if those would be the URL's of the other pods of course). With that configuration in place, you can then perform a call chain to hop from the front-end to the api-gateway and from there to api-1.įor example, to validate that the tiers are able to reach each other (e.g. You can then add an info message or environment variable like tier to each pod indicating which tier they logically represent, e.g. Imagine for example that you deploy a Kubernetes cluster with 4 pods, each of these running the exact same Inspector Gadget container. on Kubernetes or other microservice platforms) and perform queries across multiple hops. This makes it easy to set up a multi-tier test environment (e.g. The main purpose for these API's is so that you can perform call chains of requests from one deployed instance of the application to one or more other instances. HealthCheckMode (can be AlwaysSucceed, AlwaysFail, FailNextNumberOfTimes), failNextNumberOfTimes WorkloadApiAddress, unixDomainSocketEndpoint, audience RequestHostName, requestPort, requestBody, readResponse RequestUrl, requestHostName, ignoreServerCertificateErrorsĭatabaseType (can be sqlserver, postgresql, mysql, cosmosdb), sqlConnectionString, sqlConnectionStringSuffix, sqlQuery, azureManagedIdentit圜lientId Introspector allows you to perform an inspector request from the web server, returning all information the inspector knows about or only a subset (group) or even single item (key).Įach gadget can also be accessed through a REST API: Method.for testing load balancers or container orchestrators. Health Check allows you to configure the health check endpoint, e.g.Huge thanks to xstof for contributing this feature! SPIFFE allows you to call the local SPIFFE Workload API.Process Run allows you to run a process on the host and capture the output.Socket Connection allows you to perform a raw TCP socket connection from the web server (optionally with a request body and reading back the response).Azure Managed Identity allows you to request an access token for the managed identity representing your application (when running on a supported Azure service).SQL Connection allows you to perform a (scalar) query on a SQL Connection from the web server to a database (optionally using an Azure Managed Identity where supported).HTTP Request allows you to perform an HTTP request lookup from the web server.DNS Lookup allows you to perform a DNS lookup from the web server.the it does not have all gadgets and no support for API and Call Chaining), but it can still be a useful drop-in page for basic tasks.
Jose caba inspector gaget windows#
Jelledruyts/inspectorgadget:latest-windowsĪlternatively, there's also a single default.aspx page that you can simply drop in any Windows and ASP.NET Framework based host (like IIS or Azure App Service). Jelledruyts/inspectorgadget:latest or simply jelledruyts/inspectorgadget Or even more easily, you can also find the latest published version of the Docker container publicly on Docker Hub at jelledruyts/inspectorgadget or on the GitHub packages container registry at ghcr.io/jelledruyts/inspectorgadget.
Jose caba inspector gaget code#
You can compile the source code and publish the app to your host of choice directly, or build and run it as a container. NET Core based web app can run on Linux or Windows. Inspector Gadget is a simple web app that you can use to get a lot of info on the web server where it's running (the inspector) and perform additional tasks (the gadgets) from there.
0 kommentar(er)
