Add HTTP header authentication method for monitors

[marcleblanc2]

📑 I have found these related issues/pull requests

I haven't found any related issues or PRs

🔖 Feature description

I'm monitoring a GraphQL API endpoint with an HTTP request, and it uses a token value in an Authorization header for authentication. It'd be great if this could be configured under Authentication methods. It'd also be ideal if authentication methods could be reused across multiple monitors, so when I have to rotate this token, I can do it in one place instead of many.

✔️ Solution

Add authentication method: HTTP header token

❓ Alternatives

Currently saving the token header in the headers field, but then the token is readable in plain text

📝 Additional Context

No response

[madelyngamble2]

@marcleblanc2 May I resolve this issue?

[marcleblanc2]

Hey @madelyngamble2, I'm not sure I understand the question, could I ask for further clarification?

[CommanderStorm]

I would like to see this done via a graphql specific monitor instead.
If graphql requires custom headers there that are a bit uncommon maybe, that would be a better product, right?

The reasoning is simply that hacking around a problem is not something that makes the product better in the longer run.
A proper fix though is much better.

[dougle03]

graphql specific monitor

If monitoring graphql is always based on http, perhaps a subset option config under the http main monitor option?
Might help to keep the root list of monitor types from growing too large over time, especially where the monitor is really just a variation of the http monitor type?

[CommanderStorm]

You technically could also change the steam monitor this way.
If UX can be better by differentiating to different moniors (same as GRPC, I think we can do this here) we should